1.3.1-SNAPSHOT is an older version it has been renamed to follow wicket naming conventions to 1.3-SNAPSHOT. That is the major and minor versions will always be used to indicate the latest snapshot, this prevents users needing to change there pom whenever a new patch version has been released.
I originally kept the old jars because someone might still depend on them, like you do. but lately it has become clear to me that they are causing a lot of confusion so i removed them last night. The 1.3.1-SNAPSHOT was actually a lot closer to the 1.3.0 jar then the current 1.3-SNAPSHOT is. So you would not be reverting back but actually take advantage of the latest changes :) For a list of changes see http://wicketstuff.org/confluence/display/STUFFWIKI/Wicket-Security+1.3.1#Wicket-Security1.3.1-migrateto1.3.1 Maurice On Wed, May 14, 2008 at 8:04 AM, RUMikeP <[EMAIL PROTECTED]> wrote: > > Why would you want to delete those jars? I am busy using them and the appear > to be working fine (for what I am using). Please can you explain what is > broken/why it would be better to use 1.3-SNAPSHOT? What do I lose by > reverting back to 1.3-SNAPSHOT? What is the latest version of Wicket that I > can use with SWARM 1.3-SNAPSHOT? > > Thanks > Mike > > > > Mr Mean wrote: > > > > ... > > > > > Argh, i am only just reading you are using 1.3.1-SNAPSHOT. You should > > be using 1.3-SNAPSHOT. That does it i am deleting those jars. > > > > Maurice > > > > > > -- > View this message in context: > http://www.nabble.com/Swarm%3A-Authorization--for-WebMarkupContainer-tp17206272p17223972.html > Sent from the Wicket - User mailing list archive at Nabble.com. > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
