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
Hi,
On 06/06/17 22:05, Guillaume Boué wrote:
Hi guys,
The AntRun plugin was migrated to Maven 3 in svn.apache.org/r1796930.
Can someone rename the 3.0 version that currently exists on JIRA to
3.0.0? I can then start closing a bunch of issues with this fix version.
Done..
Kind regards
Karl
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:
Hi guys,
The AntRun plugin was migrated to Maven 3 in svn.apache.org/r1796930.
Can someone rename the 3.0 version that currently exists on JIRA to
3.0.0? I can then start closing a bunch of issues with this fix version.
Thanks,
Guillaume
---
L'absence de virus dans ce courrier électronique a
Github user Fuud commented on the issue:
https://github.com/apache/maven-surefire/pull/114
Any questions?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so,
Github user britter commented on the issue:
https://github.com/apache/maven-surefire/pull/141
@Tibor17 so we can merge this to 3.0-rc1 branch? Than the branch will have
the correct SNAPSHOT version.
---
If your project is set up for it, you can reply to this email and have your
Github user britter commented on the issue:
https://github.com/apache/maven-surefire/pull/146
Thank you!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so,
