Rod Johnson wrote:
However, some in the community expressed concern about the fact that after 3 months tags would not be available in the repository. They worried about the risk of an extended window between binary releases available to the community, when the absence of tags might make it hard to access bug fixes.
[...]
We are amending our maintenance policy in the light of community feedback. We will make regular binary releases from the Spring trunk available to the community, with no 3 month window. For each version of Spring, community releases will be available while it remains the trunk or until the next version is stable.
[...]
As an example, Spring 2.5.x remains the trunk, so under this policy amendment we will be releasing Spring 2.5.6 to the community very shortly. Spring 3.0M1 will be released shortly afterward and the trunk will be for 3.0 development. Once we release Spring 3.0 RC1 we will no longer provide tags or releases for the 2.5.x branch. We will focus on 3.0 development so that we can release 3.0 as soon as possible after the first milestone.

Jair Rillo Junior wrote:Mas então, pelo que eu vi no seu exemplo, você ainda precisa usar duas annotations para isso funcionar, correto? (Não conheço Spring MVC)

Jair Rillo Junior wrote:Faz tempo que não vejo o VRaptor, mas no Rails é assim: Se você chama a seguinte URL: http://suaaplicacao/clientes/cadastro, o Rails irá chamar a Action ClientesAction e o método cadastro, sem XML ou Annotation para mapear essa Action/método. Bem mais simples né?

ricardo.ekm wrote:Se encontrar um bug fora dos 3 meses, a correção sairá na próxima versão grande que sempre é disponibilizada para a comunidade.
Ex. Bug na 2.5.1, corrigido 2.5.2 (só enterprise) e também liberada na 3.0 (comunidade).

First, I've seen several people refer to this as a change in Spring's licensing. That's simply not true. Spring will continue to be available under the same licenses as before (Apache License 2.0 for most of the Spring portfolio and GPL for SpringSource dm Server). This change only refers to the maintenance policy, and specifically to binary builds.

My understanding of the new policy (confirmed with SpringSource) is that it means no more binary downloads of maintenance releases of Spring projects after 3 months following a major release, unless you're a SpringSource Enterprise customer. That's it.

Spring has been, still is, and shall continue to be open-source--with emphasis on "source". The license did not change. SpringSource will continue to resolve bugs and place those fixes in the public source code repositories. And, as a member of open-source society, you'll still be able to check that code out and build it yourself.

SpringSource, however, will no longer be obligated to provide binary builds or any other form of support after 3 months following the major release that those changes were applied to. Come to think of it, I'm not sure that they ever really were obligated to do so--but they did so anyway because they're nice folks and that's what seems to be expected of them.

Luiz Aguiar wrote:option+c = ç

Bani wrote:- Leopard: vem com Java 5 por default, não sei se alguém aqui tem experiência de tentar colocar Java 6 nele

davidpadilha wrote:tenho duvidas se vou ter que fazer malabarismos pra instalar o jboss, eclipse e tal