Well, one could see that in version x.x.x of wicketstuff core project x was excluded.. It was just a proposition. As with everything else it has pro's and con's.
2010/4/1 Jeremy Thomerson <jer...@wickettraining.com>: > there's already an attic - why create a new one? it will just generate more > emails to the list whining about "i can't find such and such" - by those who > can't use the search function well. there's nothing special about an > ex-core project that means it needs its own attic > > -- > Jeremy Thomerson > http://www.wickettraining.com > > > > On Wed, Mar 31, 2010 at 11:57 AM, nino martinez wael < > nino.martinez.w...@gmail.com> wrote: > >> I guess we could start a branch, called wicketstuff-core-attic. Then >> upgrade them to latest wicket version and see if they work and if not, >> then remove them. Unless someone wants to fix the errors. >> >> 2010/3/28 Major Péter <majorpe...@sch.bme.hu>: >> > JavaEE-Inject is tested, and OK. >> > >> > It looks like there are projects, which are depending to a specific >> > wicket version (1.4-rc*, 1.4.5): >> > * multi-text-input-parent >> > * flot-parent/flot >> > * flot-parent/flot-examples >> > * wicket-html5-parent >> > * ddcalendar-parent/ddcalendar >> > * ddcalendar-parent/ddcalendar-examples >> > >> > What's going to happen with them? >> > >> > Regards, >> > Peter >> > >> > 2010-03-24 22:14 keltezéssel, Boris Goldowsky írta: >> >> As discussed, and not hearing any objections, I've updated the >> >> wicketstuff-core project to depend on Wicket 1.4.7. wicketstuff-core's >> >> version number is now 1.4.7-SNAPSHOT, and the idea is that people can >> >> test it, and barring any major problems it can be released as a stable >> >> version 1.4.7 . >> >> >> >> Now, before people can easily test this, the artifacts need to get into >> >> the wicket snapshots maven repository, right? Can someone with the >> >> requisite permissions make this happen? In the meantime of course >> >> people are encouraged to download the projects and build and test them >> >> locally. >> >> >> >> In addition to wicket, the following dependencies were also updated to >> >> the latest stable version within the same major version of the project. >> >> I did not attempt to move Lucene from version 2.4.1 to 3.0.1, for >> >> instance, since more significant changes might be required for this (if >> >> any subproject is actually using it). >> >> >> >> Jetty: 6.1.22 >> >> Lucene: 2.4.1 >> >> slf4j: 1.5.11 >> >> JUnit: 4.8.1 >> >> >> >> I had to make a couple of changes to get everything to build with the >> >> new dependencies (commented out wagon-ssh-external extension from >> >> inmethod-grid; added new required constructor argument to two instances >> >> of SpringComponentInjector). People should test the build and make sure >> >> these changes are ok. But at least for me, I can do a "mvn install" at >> >> the top level and it works. >> >> >> >> Bng >> > >> > --------------------------------------------------------------------- >> > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >> > For additional commands, e-mail: users-h...@wicket.apache.org >> > >> > >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >> For additional commands, e-mail: users-h...@wicket.apache.org >> >> > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
