create the release files trough maven (or by hand) and follow standard release protocol from sourceforge. You need some "admin" permissions at the sourceforge wicket-stuff project to do that though. If you have enough permissions it is located under admin>file releases.
Maurice On Jan 13, 2008 3:11 AM, Maris Orbidans <[EMAIL PROTECTED]> wrote: > thank you > > I have committed fixed POM file so wicket-javaee can be compiled with > wicket 1.3. > > How can I build a release jar that would appear on SF download page ? > > > Maris > > > > You're set to go. > > > > Martijn > > > > On Jan 10, 2008 10:59 PM, Maris Orbidans <[EMAIL PROTECTED]> wrote: > > > >> it's marisorb > >> > >> Maris > >> > >> > >>> Can't do anything without your sf.net id > >>> > >>> Martijn > >>> > >>> On Jan 10, 2008 6:51 AM, Maris Orbidans <[EMAIL PROTECTED]> wrote: > >>> > >>> > >>>> hi > >>>> > >>>> can I have commit access on wicket-contrib-javaee ? > >>>> > >>>> https://wicket-stuff.svn.sourceforge.net/svnroot/wicket-stuff/trunk/wicket-contrib-javaee > >>>> > >>>> Original author doesn't have time to work on it but there are some > >>>> important things that should be done like: > >>>> + POM cleanup > >>>> + it needs recompilation to work with wicket 1.3 > >>>> > >>>> I am interested to do it because I am using this library. > >>>> > >>>> Maris > >>>> > >>>> -------------------- > >>>> > >>>> Hi Maris, > >>>> sorry for my late answer... I'm busy, indeed, and unfortunately I'm > >>>> not working with Wicket at all in the last months. > >>>> Feel free to contribute... as far as I know, there's no strict policy > >>>> for wicket-stuff committer, so you should just ask for the developer > >>>> rights on the mailing list and commit your stuff. Just to be sure to > >>>> add some documentation and your name, so people will be able to > >>>> contact you for any questions. > >>>> > >>>> Thanks for your help! > >>>> -- > >>>> Filippo Diotalevi > >>>> http://www.diotalevi.com > >>>> > >>>> > >>>> > >>> > >>> > >>> > > > > > > > > >
