I didn't test it, but you could try something like this:
- change your patterns in the settings and publish task to:
"[organisation]/[module]/[artifact]/[revision]/[artifact]-[revision](-[classifier]).[ext]"
- add classifier attribute on the artifacts element:
<artifact name="${artifact.name}" type="source" ext="jar" classifier="sources"
/>
<artifact name="${artifact.name}" type="javadoc" ext="jar" classifier="javadoc"
/>
Don't declare this classifier attribute for the main artifact
Maarten
----- Original Message ----
From: Stefan Bodewig <bode...@apache.org>
To: dev@ant.apache.org
Sent: Tue, June 15, 2010 11:56:30 AM
Subject: -source.jar and -javadoc.jar in ivy.xml
Hi,
I've added the creation of -sources.jar and -javadoc.jar to the common
build file used by all Antlibs so these jars can get uploaded to the mvn
repo when we perform a release.
Unfortunately it is not clear to me how to declare them as artifacts as
child of publications that Ivy is supposed to upload. Something like
this?
<artifact name="${artifact.name}" type="source" ext="-sources.jar"/>
I'm afraid this won't resolve to the correct name for the artifact.
Would I need to provide an explicit url? What is the recommended way?
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org
