please release about soap4r

[tjarratt]

@grosser you probably noticed that I was commenting on a few "we should release" issues for soap4r in the past year. The issue is kind of complicated.

The original maintainers (that also own the rubygems soap4r account) haven't responded to any requests to update soap4r on rubygems. I'd like to do that to better support ruby 2.0, but at this point, short of creating a new gem on rubygems.org, that isn't going to happen.

Typically I recommend people refer to this gem directly in their Gemfile eg:

gem :soap4r, :git => 'git://github.com/grosser/soap4r'

Or even use a gem with better community support (eg: Savon).

Is there a particular reason why you'd like this fork of this gem to be on rubygems.org? Maybe I'm overlooking something obvious...

[grosser]

Just trying to clean out github dependencies / having a real version in gem
specs, maybe just releasing soap5r :)
On Sep 16, 2013 11:44 AM, "Tim Jarratt" [email protected] wrote:

@grosser https://github.com/grosser you probably noticed that I was
commenting on a few "we should release" issues for soap4r in the past year.
The issue is kind of complicated.

The original maintainers (that also own the rubygems soap4r account)
haven't responded to any requests to update soap4r on rubygems. I'd like to
do that to better support ruby 2.0, but at this point, short of creating a
new gem on rubygems.org, that isn't going to happen.

Typically I recommend people refer to this gem directly in their Gemfile
eg:

gem :soap4r, :git => 'git://github.com/grosser/soap4r'

Or even use a gem with better community support (eg: Savon).

Is there a particular reason why you'd like this fork of this gem to be on
rubygems.org? Maybe I'm overlooking something obvious...

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/13#issuecomment-24533885
.

[tjarratt]

+1

I could get behind a "soap5r". That's just crazy enough to work.

Sent From A Very Small Keyboard

On Sep 16, 2013, at 12:13, Michael Grosser [email protected] wrote:

Just trying to clean out github dependencies / having a real version in gem
specs, maybe just releasing soap5r :)
On Sep 16, 2013 11:44 AM, "Tim Jarratt" [email protected] wrote:

@grosser https://github.com/grosser you probably noticed that I was
commenting on a few "we should release" issues for soap4r in the past year.
The issue is kind of complicated.

The original maintainers (that also own the rubygems soap4r account)
haven't responded to any requests to update soap4r on rubygems. I'd like to
do that to better support ruby 2.0, but at this point, short of creating a
new gem on rubygems.org, that isn't going to happen.

Typically I recommend people refer to this gem directly in their Gemfile
eg:

gem :soap4r, :git => 'git://github.com/grosser/soap4r'

Or even use a gem with better community support (eg: Savon).

Is there a particular reason why you'd like this fork of this gem to be on
rubygems.org? Maybe I'm overlooking something obvious...

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/13#issuecomment-24533885
.

—
Reply to this email directly or view it on GitHub.

[grosser]

I'd just love to have a real gem I can add to my gems as dependency and not having to tell people to install some custom github foo :)

@felipec thoughts ?

[tjarratt]

Hmmm, well I was about to push to rubygems.org this morning and noticed that soap5r is already taken.

I'm going to release it at soap2r since I had originally worked on this branch to provide support for ruby v2.0

[tjarratt]

Released as soap2r http://rubygems.org/gems/soap2r.

[grosser]

@aforward what do you think about getting everything back into 1 repo/gem ?

[aforward]

Sounds good @grosser -- my work was mostly on the gemspec stuff that I could wrap into a pull a new pull request. Send me the appropriate repo/gem name and I can review my stuff

[grosser]

I'd think making a pull to https://github.com/felipec/soap4r with everything except the gemspec changes would be best and then you and @felipec can figure out what to name this beat + share ownership (so this abandomed gem thing does not repeat itself) :)

[tjarratt]

Agreed on both counts. I'm more than willing to share the account on rubygems.org for the gem, so that it doesn't become abandoned as the community continues to fix bugs.

[grosser]

@aforward can you make a pull against this repo so we get all the features/fixes together ?

[aforward]

It will probably be easier to re-apply my changes off a new fork as the
commit histories are quite different. I'll get it in the next few days.

On Wed, Sep 25, 2013 at 12:04 AM, Michael Grosser
[email protected]:

@aforward https://github.com/aforward can you make a pull against this
repo so we get all the features/fixes together ?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/13#issuecomment-25060884
.

aforward

[grosser]

@aforward gogogo :D