On 5/17/07, Torsten Curdt <[EMAIL PROTECTED]> wrote:
So it should be
<id>rc</id>
<repositories>
<repository>
<id>rc</id>
<url>http://people.apache.org/builds/commons/$
{project.name}/${project.version}/m2-staging-repository</url>
<snapshots><enabled>false</enabled></snapshots>
<releases><enabled>true</enabled></releases>
</repository>
</repositories>
${project.name} is likely to be something like "Commons Math" not the
"commons-math" that would be more appropriate in a directory name. If
you can't find something suitable in the pom, you may want to
introduce an arbitrary property in each project's pom and use that in
the url. (I think $artifactId would only work for single-module
projects.)
mvn stage:copy \
-Dsource="http://people.apache.org/builds/commons/$
{project.name}/${project.version}/m2-staging-repositoryg" \
-Dtarget="scp://people.apache.org/www/people.apache.org/repo/
m2-ibiblio-rsync-repository" \
-Dversion=${project.version}
Any chance to have the project name and version injected
automatically there?
Not afaik. You should know what you're promoting. :)
> The latest release of the gpg plugin will prompt for a passphrase if
> one is not supplied.
Great ...last time I tried it did not work for me (although it was
supposed to according to the docs)
Specify a version in the pom to make sure you're really using the
latest. Open a bug if it's not working... I gave up and just put the
passphrase in settings.xml. (You may not like being prompted-- I have
a feeling it's going to prompt more than once!)
> Signing the release distributions... The gpg plugin will sign them if
> you deploy them to the repository (attached assemblies). There's a
> bit of renaming and copying to do that I haven't figured out how to
> automate yet.
WDYM? ...seems like the signing worked just fine for the jci RC1.
> Then you have to decide if you want the distributions
> in the Maven repo.
WDYM? The usual artifacts? Sure!
No, the .zip and .tar.gz release distributions, the assemblies.
Not so sure what to do with the bin/src dists from the assembly though.
Right. :)
Take a look at the last section of my Archiva release page, under
'Release Distribution':
http://wiki.wsmoak.net/cgi-bin/wiki.pl?Archiva09Alpha2Release
The assemblies get deployed under their artifactIds, not the "final
name" that we want for the public distribution. Plus Maven's checksum
files aren't formatted correctly for md5sum -c.
--
Wendy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]