« Return to Thread: Spring
Re: Spring
by Tom Nichols
::
Rate this Message:
Ok, say 2.5.5 is the last community maintenance release before Spring
v3. Now assume there is some code in Spring's trunk or 2.5.x branch
that Grails needs. They will just bundle a non-official build of
Spring.
Here's what they (or someone) can do --
After the 3 month window, just do "unofficial builds" every x months
or whenever certain bugs are fixed. Then release them to Maven as a
sort of "unofficial official" community build. Someone could easily
provide maintenance builds without forking the code. Would they be
able to support it? Not really -- at least I wouldn't want to. But
at least when the community is discussing issues with Spring they can
say "I'm running community build 2.5.17" and everyone will be on the
same page. Doesn't that make sense? No forking, just a semi-official,
non-SpringSource community build repository. Done.
On Fri, Sep 26, 2008 at 1:21 PM, tomasz brymora <tomekpilot@...> wrote:
> ... DZone had this piece just recently as a response to the situation:
> http://java.dzone.com/news/qa-with-rod-johnson-over-sprin
> It seems to make a bit more sense now imho.
>
> --- On Fri, 9/26/08, Erik Pragt <erik@...> wrote:
>
>> From: Erik Pragt <erik@...>
>> Subject: Re: [grails-user] Spring
>> To: user@...
>> Date: Friday, September 26, 2008, 8:43 AM
>> Graeme Rocher-2 wrote:
>> >
>> > We have a good relationship with the guys at
>> SpringSource and don't
>> > have any immediate concerns no. I think there is a
>> slight overreaction
>> > to the policy in that thread
>> >
>>
>> Sorry Graeme, but I think your taking things a bit to
>> lightly here.
>>
>> This change in policy is a huge risk for any Spring related
>> project, but
>> also for any project which relies on Spring. I don't
>> think that having 'a
>> good relationship' will result in: Instead of charging
>> $25.000 for it, we
>> give it for free. If that was the case, people would just
>> download Grails to
>> get the latest Spring version from it.
>>
>> Since I think the future of Spring as a framework
>> (especially with the new
>> money focusses approach) is a bit uncertain, I also fear a
>> little bit for
>> Grails, since it so strongly depends on Spring. I'm not
>> about to start a
>> panic here, but I think I need to be a little be more
>> convinced about the
>> future of Grails + Spring before I'm at not concerned
>> about the future of
>> Grails anymore.
>>
>> So: any idea on how this relationship could help Grails?
>>
>> Erik
>>
>> PS: This is not theoretical at all: Grails Remoting needs
>> Spring 2.5.5.
>> Whith this policy in effect, Spring 2.5.5 would never have
>> been released to
>> the public, I wouldn't have been able to use Grails in
>> combination with
>> Grails Remoting, and I would have to find a different
>> solution. Just some
>> context for my worries.
>> --
>> View this message in context:
>> http://www.nabble.com/Spring-tp19609427p19687736.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
>
> ---------------------------------------------------------------------
> 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
v3. Now assume there is some code in Spring's trunk or 2.5.x branch
that Grails needs. They will just bundle a non-official build of
Spring.
Here's what they (or someone) can do --
After the 3 month window, just do "unofficial builds" every x months
or whenever certain bugs are fixed. Then release them to Maven as a
sort of "unofficial official" community build. Someone could easily
provide maintenance builds without forking the code. Would they be
able to support it? Not really -- at least I wouldn't want to. But
at least when the community is discussing issues with Spring they can
say "I'm running community build 2.5.17" and everyone will be on the
same page. Doesn't that make sense? No forking, just a semi-official,
non-SpringSource community build repository. Done.
On Fri, Sep 26, 2008 at 1:21 PM, tomasz brymora <tomekpilot@...> wrote:
> ... DZone had this piece just recently as a response to the situation:
> http://java.dzone.com/news/qa-with-rod-johnson-over-sprin
> It seems to make a bit more sense now imho.
>
> --- On Fri, 9/26/08, Erik Pragt <erik@...> wrote:
>
>> From: Erik Pragt <erik@...>
>> Subject: Re: [grails-user] Spring
>> To: user@...
>> Date: Friday, September 26, 2008, 8:43 AM
>> Graeme Rocher-2 wrote:
>> >
>> > We have a good relationship with the guys at
>> SpringSource and don't
>> > have any immediate concerns no. I think there is a
>> slight overreaction
>> > to the policy in that thread
>> >
>>
>> Sorry Graeme, but I think your taking things a bit to
>> lightly here.
>>
>> This change in policy is a huge risk for any Spring related
>> project, but
>> also for any project which relies on Spring. I don't
>> think that having 'a
>> good relationship' will result in: Instead of charging
>> $25.000 for it, we
>> give it for free. If that was the case, people would just
>> download Grails to
>> get the latest Spring version from it.
>>
>> Since I think the future of Spring as a framework
>> (especially with the new
>> money focusses approach) is a bit uncertain, I also fear a
>> little bit for
>> Grails, since it so strongly depends on Spring. I'm not
>> about to start a
>> panic here, but I think I need to be a little be more
>> convinced about the
>> future of Grails + Spring before I'm at not concerned
>> about the future of
>> Grails anymore.
>>
>> So: any idea on how this relationship could help Grails?
>>
>> Erik
>>
>> PS: This is not theoretical at all: Grails Remoting needs
>> Spring 2.5.5.
>> Whith this policy in effect, Spring 2.5.5 would never have
>> been released to
>> the public, I wouldn't have been able to use Grails in
>> combination with
>> Grails Remoting, and I would have to find a different
>> solution. Just some
>> context for my worries.
>> --
>> View this message in context:
>> http://www.nabble.com/Spring-tp19609427p19687736.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
>
> ---------------------------------------------------------------------
> 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
« Return to Thread: Spring
| Free embeddable forum powered by Nabble | Forum Help |
