But how do we propagate the releases to the central repository? The maven guys want to use a rsync thing to get them if you let them.
Martijn On 9/11/07, Johan Compagner <[EMAIL PROTECTED]> wrote: > i don't see the jquery projects in bamboo > so then that distributionManagement doesn't do much. > > Why having 2 dirs? Maven already creates there own dirs for the specific > projects > also we don't do rsync to something. This repository is just for the wicket > snapshots and wicketstuff snapshots/releases > > johan > > > On 9/10/07, David Bernard <[EMAIL PROTECTED]> wrote: > > > > Hi, > > > > I've added (as suggested) : > > > > <distributionManagement> > > <snapshotRepository> > > <id>repo</id> > > <name>Local Bamboo/Tomcat repository</name> > > > > <url>file:/home/wicket/tomcat/webapps/maven/repository/</url> > > <uniqueVersion>false</uniqueVersion> > > </snapshotRepository> > > <repository> > > <id>repo</id> > > <name>Local Bamboo/Tomcat repository</name> > > > > <url>file:/home/wicket/tomcat/webapps/maven/repository/</url> > > </repository> > > </distributionManagement> > > > > into the wicketstuff-parent's pom.xml (the shared pom for > > wicketstuff-jquery* projects). > > > > IMO, it's better to have 2 directories one for release and one for > > snapshots. > > * /home/wicket/tomcat/webapps/maven/repository/release > > * /home/wicket/tomcat/webapps/maven/repository/snapshots > > > > With 2 directories, it's possible to enable rsync/push of releases into > > central repository (snaphots aren't allowed). > > See "Sync'ing your own repository to the central repository automatically" > > at > > http://maven.apache.org/guides/mini/guide-central-repository-upload.html > > (I did it for my sourceforge project and for inria forge). > > > > /david > > > -- Buy Wicket in Action: http://manning.com/dashorst Apache Wicket 1.3.0-beta3 is released Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.0-beta3/
