All you need is an account for SourceForge. Then you could commit in wicketstuff's SVN
El jue, 09-07-2009 a las 13:38 +0200, Olger Warnier escribió: > Hi Luca, > > Maybe it is possible to commit the whole into an existing / new branch > of the wicket-security project. > Is there someone who could arrange that ? > > Kind Regards, > > Olger > > > On 9 jul 2009, at 11:00, Luca Provenzani wrote: > > > Hi all, > > i'm interested too. Probably my company have to realize a new > > project in the > > near future and we think to use wicket 1.4, but we need something like > > swarm. > > I started to see in svn but if it is possible to have your updated > > code it > > would be fantastic. > > > > thank you > > Luca > > > > 2009/7/9 Olger Warnier <[email protected]> > > > >> Hi Joshua / List, > >> > >> For our project, I have ported wicket-security to 1.4 based on the > >> code of > >> Maurice found at: > >> > >> http://wicket-stuff.svn.sourceforge.net/viewvc/wicket-stuff/branches/wicket-security-1.4-earlyaccess/ > >> And > >> > >> https://wicket-stuff.svn.sourceforge.net/svnroot/wicket-stuff/trunk/wicket-security/ > >> Most of the tests work fine, a few of them are disabled (I is not > >> quite > >> clear to me what the expected behaviour is yet) and I removed the > >> ACEGI > >> example as it was too outdated. (I have a spring-security sample > >> available > >> to add) > >> The current state is more of less a first 'seems to work' version > >> based on > >> RC5 that needs more attention while being used and extended. > >> Please let me know if you are intrested, I could provide the code and > >> further suport to get it released along with the wicket 1.4 release. > >> Kind Regards, > >> Olger > >> > >> On 8 jul 2009, at 18:42, Joshua Martin wrote: > >> > >> When will Wicket 1.4 be compatible with Swarm/Wasp? > >>> > >>> -- > >>> _________________________________ > >>> > >>> Joshua S. Martin > >>> > >>> --------------------------------------------------------------------- > >>> 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] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
