Hi all, On a wicketstuff related note, do you think there is any benefit of trying to keep the release cycles of the wicketstuff inline with the core wicket projects?
I do understand that there is a wide variety of modules under the wicketstuff banner, and ensuring it is all compatible is not really a single persons task, but given the 1.4.7 naming it does sort of seem that an attempt to keep the modules inline is being aimed at. The counterpoint to keeping up to date is that its potentially misleading that a module looks to be mature (1.4.7 looks mature to me) when it might have only been in existence for a few weeks. This question is not really aimed at anyone, and it may have already been discussed in other posts, if so please set me straight. In any case its just a thought.. Steve On Tue, May 25, 2010 at 1:48 AM, Michael O'Cleirigh < [email protected]> wrote: > Hello, > > Based on the positive reception for a 1.4.7 wicketstuff-core release, 4 > positive votes (3 + mine) and no negative, I promoted the staged release > into the sonatype repository and filed the ticket for central sync up. > > The sync up has now occurred and the 1.4.7 artifacts are available through > maven central (http://repo2.maven.org/maven2/org/wicketstuff). > > Tag: > https://wicket-stuff.svn.sourceforge.net/svnroot/wicket-stuff/tags/wicketstuff-core-1.4.7 > > To use in Maven: > > <dependency> > <groupId>org.wicketstuff</groupId> > <artifactId>${module}</artifactId> > <version>1.4.7</version> > </dependency> > > The module names come from what is defined in each module's POM (so each > module directory/pom.xml that produces a jar artifact). > > Regards, > > Mike > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
