Calling dist:deploy and jar:deploy from same goal causes problems

[Neil Blue <Ne...@denovopharma.com>]

Have set up the following goal:

<goal name="deploy-all">
   <echo>
   +--------------------------------------+
   | Deploying project dist, jar and site |
   +--------------------------------------+
   </echo>
   <attainGoal name="jar:deploy"/>
   <attainGoal name="dist:deploy"/>
</goal>

The jar:deploy runs correctly, deploying the jar to the jars directory in the remote repository. The dist:deploy goal then deploys the distributions to the jars directory (rather than the distributions directory).

Swapped the jar:deploy with the dist:deploy, so deploy-all now looks like:

<goal name="deploy-all">
   <echo>
   +--------------------------------------+
   | Deploying project dist, jar and site |
   +--------------------------------------+
   </echo>
   <attainGoal name="dist:deploy"/>
   <attainGoal name="jar:deploy"/>
</goal>

This time dist:deploy works correctly, deploying the distributions to the distributions, but the jar:deploy then also deploys the jars to the distributions directory.

Have done some investigation, the plugin.jelly files in both dist and jar use deploy:artifact and pass in a type (as distributions and jars respectively). It seems that the second call to deploy:artifact does not successfully set the type (when run from within the same goal).

Incidentally, when running dist:deploy or jar:deploy directly from the command line, they both behave as expected.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org