Hi Buillaum,
On 06/06/17 23:24, Guillaume Boué wrote:
Thanks for confirming this Karl. So in this case, I think that part of
the code in maven-artifact-transfer can be safely deleted (calling
setRepository and catching an exception). The repository to deploy to is
set on the main artifact
Thanks for confirming this Karl. So in this case, I think that part of
the code in maven-artifact-transfer can be safely deleted (calling
setRepository and catching an exception). The repository to deploy to is
set on the main artifact and, even if it didn't throw an exception,
there would be
Hi,
On 06/06/17 22:38, Guillaume Boué wrote:
In the new API ProjectDeployer (in maven-artifact-transfer), I noticed
the default implementation raises a warning in the case that it cannot
set the repository to an attached artifact:
Yes this code has been "stolen" from the maven-deploy-plugin
In the new API ProjectDeployer (in maven-artifact-transfer), I noticed
the default implementation raises a warning in the case that it cannot
set the repository to an attached artifact:
