« Return to Thread: Spring
Re: Spring
by mingfai
::
Rate this Message:
to my understanding Spring may still do bug fixing and put into svn. Given Grails will not use very old version of Spring, the worst case is just to build Spring by ourselves. Maybe we could make a nightly build of Spring+Groovy+Grails.
i wonder if we have concern over Spring's new policy, what could we do? drop Spring from Grails? Ask G2One to pay for subscription? there are any sensible options to consider, so i would not concern about it personally.
>Firstly, many people who adopt Grails don't even know they have
>Spring. Grails is an abstraction layer over Spring. In other words
I'm not one of those people. I use Spring and Hibernate directly and keep my Spring library up-to-date all the time. It's not too good to do in this way, but it's not good to make too many request to update library either. Anyway, it would be great if there is a clear policy and mechanism of updating Grails dependency libraries. two suggestions are as follows:
regards,
mingfai
i wonder if we have concern over Spring's new policy, what could we do? drop Spring from Grails? Ask G2One to pay for subscription? there are any sensible options to consider, so i would not concern about it personally.
>Firstly, many people who adopt Grails don't even know they have
>Spring. Grails is an abstraction layer over Spring. In other words
I'm not one of those people. I use Spring and Hibernate directly and keep my Spring library up-to-date all the time. It's not too good to do in this way, but it's not good to make too many request to update library either. Anyway, it would be great if there is a clear policy and mechanism of updating Grails dependency libraries. two suggestions are as follows:
- for every major release, Grails will update all it's core depending libraries, that incl. Spring, Hibernate, Jetty, Groovy etc.
- make dependency library wiki page, whoever want a library be updated could add an entry to the page, and indicate if it's unofficially tested or not. And whenever there are Grails release, dev just check the list and make sure all requested libraries are up to date
regards,
mingfai
On Fri, Sep 26, 2008 at 11:50 PM, Graeme Rocher <graeme@...> wrote:
Firstly, many people who adopt Grails don't even know they have
Spring. Grails is an abstraction layer over Spring. In other words
people, in my experience, don't consider upgrading the Spring jar
distributed with Grails, they think in terms of upgrading Grails not
upgrading Spring.
Its more an issue for us, the Grails developers, to make sure that we
are prompt with upgrading to the latest version of Spring after a
release. And to ensure any issues are reported. It may also be that
Grails releases become more aligned with Spring releases. And during
development we can always build a distribution of Spring from the
sources
The code in the Spring repo will be the latest code. Obviously some
feel its an issue, I personally think that it will be less of an
issue than is made out to be.
Cheers
On Fri, Sep 26, 2008 at 4:34 PM, Marcel Overdijk
<marceloverdijk@...> wrote:
>
> I agree with Erik that this policy change should not be underestimated.
>
> I think a lot of people (including myself) are trying to bring Grails under
> the attention of their managers and/or are starting their first commercial
> projects with Grails.
>
> But now with Spring's change in policy people will be more careful and think
> twice. Also for management the risk to need expensive subscriptions could be
> a blocker in this. Especially for small to medium (startup) projects.
>
>
> Cheers,
> Marcel
>
>
>
>
>
> Erik Pragt wrote:
>>
>>
>>
>> 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-tp19609427p19690873.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
>
>
>
--http://www.g2one.com
Graeme Rocher
Grails Project Lead
G2One, Inc. Chief Technology Officer
---------------------------------------------------------------------
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 |
