You need some extra configuration in your Maven settings.xml:
<servers>
<!-- To publish a snapshot of some part of Maven -->
<server>
<id>apache.snapshots.https</id>
<username>jgallimore</username>
<password>XXXXXXXXXX</password>
</server>
<!-- To publish a website using Maven -->
<server>
<!--Note: This should match the id in your distributionManagement entry
used-->
<!--to upload your site. This is the suggested standard id-->
<id>apache.website</id>
<username>jgallimore</username>
<privateKey><!--OPTIONAL: path to your ssh key ie
~/.ssh/identify--></privateKey>
<filePermissions>664</filePermissions>
<directoryPermissions>775</directoryPermissions>
</server>
<!-- To stage a release of some part of Maven -->
<server>
<id>apache.releases.https</id>
<username>jgallimore</username>
<password>XXXXXXXXXX</password>
</server>
</servers>
(use your Apache username and password obviously ;-))
And then I think you can just do 'mvn -Dassemble deploy'. I like to do a
full build first, and run the itests. If something fails to build during
the deploy things can be left in a funny state if I remember correctly.
Jon
On 10/01/2011 09:43, Jean-Louis MONTEIRO wrote:
Sorry, the spam ;-)
A new OWB snapshot is available.
djencks already did related change to make OEJB work with the new OWB
snapshot.
So, how can i deploy a new OEJB snapshot so end users can still work with
our snapshot?
For the moment, our snapshot does not work because djenck's commit is not
in.
Thanks
Jean-Louis
