Hi folks,
I am currently deploying certain dev.java.net projects under our
corporate Hudson - to ensure quality of builds.
This concerns annox, hyperjaxb3, jaxb2-commons and maven-jaxb2-plugin projects.
All these projects are maven2 projects. For the artifact deployment to
work correctly from within Hudson, I need to reconfigure the
distribution management. This change only affects developers who
operate/build on SVN/CVS checked-out projects listed above.
Old distribution management configuration was as follows:
<distributionManagement>
<repository>
<id>local-repository</id>
<url>file:${m2-repo.java.net.url}</url>
</repository>
</distributionManagement>
New configuration is as follows:
<distributionManagement>
<repository>
<id>dev.java.net-releases</id>
<url>${dev.java.net-releases.deploy.url}</url>
</repository>
<snapshotRepository>
<id>dev.java.net-snapshots</id>
<url>${dev.java.net-snapshots.deploy.url}</url>
</snapshotRepository>
</distributionManagement>
Developers will need to add the appropriate properties to your
dev.java.net profile in maven2 settings.xml. If you previously had:
<m2-repo.java.net.url>C:\Projects\maven2-repository\www\repository</m2-repo.java.net.url>
Add these two properties:
<dev.java.net-releases.deploy.url>file:C:\Projects\maven2-repository\www\repository</dev.java.net-releases.deploy.url>
<dev.java.net-snapshots.deploy.url>file:C:\Projects\aven2-repository\www\snapshots</dev.java.net-snapshots.deploy.url>
It's almost the same, but "file:" scheme is included into URL - this
means we can freely use something like sftp deployment in Hudson.
The changes will be effective in a couple of hours.
Bye.
/lexi