SpringWs plugin - dead in the water?

[Luis Muniz-2]

Hi,

We are currenly using the spring WS plugin and a very happy with it. The only issue is that there does not seem to be an evolution of this plugin.

SpringWS has hit 2.0 and I can't see any activity on the JIRA site on this plugin.

Moreover, can anyone point me to the source repository of this plugin, I haven't been able to find a link to that either.

Thanks.

[Graeme Rocher-4]

The source appears to be here:

http://svn.codehaus.org/grails-plugins/grails-springws/trunk/

You will need to contact the original author to find the status on the plugin

Cheers

On Mon, May 30, 2011 at 10:52 AM, Luis Muniz <[hidden email]> wrote:

> Hi,
>
> We are currenly using the spring WS plugin and a very happy with it. The
> only issue is that there does not seem to be an evolution of this plugin.
>
> SpringWS has hit 2.0 and I can't see any activity on the JIRA site on this
> plugin.
>
> Moreover, can anyone point me to the source repository of this plugin, I
> haven't been able to find a link to that either.
>
> Thanks.
>

--
Graeme Rocher
Grails Project Lead
SpringSource - A Division of VMware
http://www.springsource.com

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[Luis Muniz-2]

Thanks

On Mon, May 30, 2011 at 11:12 AM, Graeme Rocher <[hidden email]> wrote:

The source appears to be here:

http://svn.codehaus.org/grails-plugins/grails-springws/trunk/

You will need to contact the original author to find the status on the plugin

Cheers

On Mon, May 30, 2011 at 10:52 AM, Luis Muniz <[hidden email]> wrote:
> Hi,
>
> We are currenly using the spring WS plugin and a very happy with it. The
> only issue is that there does not seem to be an evolution of this plugin.
>
> SpringWS has hit 2.0 and I can't see any activity on the JIRA site on this
> plugin.
>
> Moreover, can anyone point me to the source repository of this plugin, I
> haven't been able to find a link to that either.
>
> Thanks.
>

--
Graeme Rocher
Grails Project Lead
SpringSource - A Division of VMware
http://www.springsource.com

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

   http://xircles.codehaus.org/manage_email

[houbie]

Russ Miles is the original author of the plugin, but I wrote part of the functionality and did a major refactoring.

After my last commit about a year ago, I asked Russ to release the plugin, but did not get an answer.

Personally, I wouldn't mind if someone else would take over (the plugin collective?). At the moment I don't have any spare time to work on this plugin.

Grtz,

Ivo

On 31 May 2011, at 15:13, Luis Muniz wrote:

Thanks

On Mon, May 30, 2011 at 11:12 AM, Graeme Rocher <[hidden email]> wrote:

The source appears to be here:

http://svn.codehaus.org/grails-plugins/grails-springws/trunk/

You will need to contact the original author to find the status on the plugin

Cheers

On Mon, May 30, 2011 at 10:52 AM, Luis Muniz <[hidden email]> wrote:
> Hi,
>
> We are currenly using the spring WS plugin and a very happy with it. The
> only issue is that there does not seem to be an evolution of this plugin.
>
> SpringWS has hit 2.0 and I can't see any activity on the JIRA site on this
> plugin.
>
> Moreover, can anyone point me to the source repository of this plugin, I
> haven't been able to find a link to that either.
>
> Thanks.
>

--
Graeme Rocher
Grails Project Lead
SpringSource - A Division of VMware
http://www.springsource.com

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

   http://xircles.codehaus.org/manage_email

[Radim Kolar]

Russ do not cares about this plugin any more i asked him to fix bugs
several and provided patches and got no reply at all.

I believe that code ownership as practised with grails plugins is simply
wrong. Take a look at freebsd project - anybody can submit patch and if
code owner does not respond in reasonable time(2-4w) then patch is
committed. Bugs in springws plugin annoyed me for almost 2 years now.

in trunk is already one bug fixed - incorrect web.xml generation.
serializer-2.7.1.jar is still missing from lib/ in trunk.

Pass springws to more active maintainer or make it - anybody can submit
patch until new maintainer is found.
We waited about 2 years for simple bug fixes already, how many years you
want to wait?

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[hanswesterbeek]

Russ has made it clear to me that he will be happy to hand over
maintainership to any volunteer. Maybe it was your confrontational
language that made him a bit apprehensive.

So I'm sure you can become the maintainer, eg just take the current
code, put it in a github repo and apply your changes.

Cheers,
Hans

On Sat, Aug 27, 2011 at 9:31 PM, Radim Kolar <[hidden email]> wrote:

> Russ do not cares about this plugin any more i asked him to fix bugs several
> and provided patches and got no reply at all.
>
> I believe that code ownership as practised with grails plugins is simply
> wrong. Take a look at freebsd project - anybody can submit patch and if code
> owner does not respond in reasonable time(2-4w) then patch is committed.
> Bugs in springws plugin annoyed me for almost 2 years now.
>
> in trunk is already one bug fixed - incorrect web.xml generation.
> serializer-2.7.1.jar is still missing from lib/ in trunk.
>
> Pass springws to more active maintainer or make it - anybody can submit
> patch until new maintainer is found.
> We waited about 2 years for simple bug fixes already, how many years you
> want to wait?
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>   http://xircles.codehaus.org/manage_email
>
>
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[Radim Kolar]

So I'm sure you can become the maintainer, eg just take the current
code, put it in a github repo and apply your changes.

I would prefer to stay away from github. i have no experience with this
+ git and i am not willing to waste my time on learning that. I can
provide fixed version of that plugin to anybody who is willing to
maintain that or i am willing to correct that in SVN. No git. I have no
interested in maintaining that plugin in long time (i am busy with other
projects), i am interested only in getting it fixed in svn.

https://rapidshare.com/files/3143139014/grails-springws-0.5.1.zip

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[Brad Whitaker]

Has anyone put any effort into this plugin? I'd really like to get it updated to be compatible with Grails 2.x.

[Graeme Rocher-4]

Not that I'm aware of. Contributions welcome

On Thu, Mar 22, 2012 at 7:01 PM, Brad Whitaker <[hidden email]> wrote:

> Has anyone put any effort into this plugin? I'd really like to get it updated
> to be compatible with Grails 2.x.
>
> --
> View this message in context: http://grails.1312388.n4.nabble.com/SpringWs-plugin-dead-in-the-water-tp3560213p4496373.html
> Sent from the Grails - user mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>    http://xircles.codehaus.org/manage_email
>
>

--
Graeme Rocher
Grails Project Lead
SpringSource - A Division of VMware
http://www.springsource.com

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[pledbrook]

> Has anyone put any effort into this plugin? I'd really like to get it updated
> to be compatible with Grails 2.x.

I recommend we import the code into the gpc GitHub account. Anyone who
is actively using it and willing to test changes can be added as
committers.

The real issue as I see it is the ability to verify fixes. As long as
someone is in a position to do this, then we're good to go. It doesn't
necessarily need "ownership".

Thoughts?

Peter

--
Peter Ledbrook
Grails Advocate
SpringSource - A Division of VMware

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[Brad Whitaker]

The gpc GitHub account sounds like a good idea to me. I'm willing to put some effort into maintenance and testing. (I have three separate apps in production that use this plugin.) I have some minor enhancements to the current plugin. I looked into upgrading the plugin myself but found a lot of code that took me into unfamiliar territory, mainly related to Grails and Acegi rather than Spring-WS. (Based on the Spring-WS documentation it does not appear that there have been significant API changes going from 1.5.x to 2.0.x.)

Thanks,

Brad

[pledbrook]

> The gpc GitHub account sounds like a good idea to me. I'm willing to put some
> effort into maintenance and testing. (I have three separate apps in
> production that use this plugin.) I have some minor enhancements to the
> current plugin. I looked into upgrading the plugin myself but found a lot of
> code that took me into unfamiliar territory, mainly related to Grails and
> Acegi rather than Spring-WS. (Based on the Spring-WS documentation it does
> not appear that there have been significant API changes going from 1.5.x to
> 2.0.x.)

Brad (and everyone else),

The plugin is now available on GitHub:

     https://github.com/gpc/grails-springws

You can either fork it or we can give you direct commit access to the
repo. You may also want to check out the changes made in this repo:

    https://github.com/euvitudo/grails-springws-plugin

If you have any questions about Grails and plugins, feel free to ask.
One of the first things to do is sort out the dependencies. The above
repository seems to have added them to BuildConfig.groovy, but it
doesn't seem to rely on transitive dependencies. I'm also not sure
about the Spring WS plugin requiring Spring Security - is there really
a hard dependency between the two? Or does Spring WS simply support
Spring Security?

Cheers,

Peter

--
Peter Ledbrook
Grails Advocate
SpringSource - A Division of VMware

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email