i did find a hack to accomplish this ... which was to create a new build file
that just had the ant code to publish the second artifact. note from my
previous email that i had to set ivy.dep.file in the seconard build file.
i needed to publish the secondary artifact in a separate ant file, i am
guessing because once the primary ivy.xml is loaded, i could not overwrite the
variables setup by it to point to the primary artifact.
is there some better way to accomplish this?
jeff <[EMAIL PROTECTED]> wrote: i have one project (one build.xml), that
generates multiple JARs that i wish to publish. i can't find the right approach
to this.
i've tried too many permutations to list here, but this is the latest i have
tried ...
my two artifacts ...
and ...
organisation="com.sun.portal"
module="admin"
revision="${PS.product.version}"
pubdate="${pubdate}"
status="integration"
overwrite="true"
>
thus publishes both of the JARs, but both as the same name, admin-7.2.jar, so
one overwrites the other.
any ideas?
---------------------------------
Ahhh...imagining that irresistible "new car" smell?
Check outnew cars at Yahoo! Autos.
---------------------------------
Ahhh...imagining that irresistible "new car" smell?
Check outnew cars at Yahoo! Autos.
