Johan Compagner wrote:
i don't see the jquery projects in bamboo
so then that distributionManagement doesn't do much.
How to regsister projects on bamboo ?
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
It's possible to upload releases on central repository automaticaly without
doing a JIRA request,
* only for repository's root directory without snapshots.
* only for one groupId (and children) (by request) (eg: org.wicketstuff)
from the maven site :
.....................................................................................................................................
Sync'ing your own repository to the central repository automatically
--------------------------------------------------------------------
This is the preferred process. You first have to setup your project to deploy
to a remote repository .
You must make sure the remote repository server has rsync or rsync over ssh,
there are free services like Sourceforge that provide you ssh server access .
After you are able to deploy to your remote repository make sure you only deploy releases . Then you can provide a script like the current scripts , open an issue under MAVENUPLOAD and attach the
script, and we'll add it to the automatically synced repos.
Make sure you provide proof of owning the domain that matches the groupId (see groupId considerations above). Proof means either the server to sync from has a name under that domain, your name shows
up in a prominent place in the domain, or you provide a link to a whois database where your name shows up as the domain owner.
If you are using ssh in your own server you need to add the maven public key to
the authorized ones to allow us to log in the machine.
Remember to subscribe to repository mailing list .
Important : nothing is deleted or changed in the Central Repository after it is
synced (except maven-metadata.xml files)
.....................................................................................................................................
Upload jar to central repo:
* avoid user to declare wicketstuff's repository in every pom.
* increase visibility
* do automatique registration into mvnrepository.com and maven IDE plugin
/david
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
