[ https://issues.apache.org/jira/browse/MDEPLOY-200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16344977#comment-16344977
]
Robert Seidel edited comment on MDEPLOY-200 at 1/30/18 12:49 PM:
-----------------------------------------------------------------
The static variables are part of the problem - please see the comment of Jérôme Joslet
here https://issues.apache.org/jira/browse/MDEPLOY-193. Chas Honton has a solution for this
by using session user properties and he already created a pull request [https://github.com/apache/maven-deploy-plugin/pull/1].
Another guy analyzed the problem ([http://dev.eclipse.org/mhonarc/lists/aether-users/msg00387.html]):
{quote}{{Also, your analysis suggests a bug in the maven-deploy-plugin in that it relies on
the erroneous assumption that a single class loader is used per plugin through out a multi-module
build.}}
{quote}
All the issues 193, 200, 224, 225, 226 are related to each other.
was (Author: robseidel):
The static variables are part of the problem - please see the comment of Jérôme Joslet
here https://issues.apache.org/jira/browse/MDEPLOY-193. Chas Honton has a solution for this
by using session user properties and he already created a pull request [https://github.com/apache/maven-deploy-plugin/pull/1].
Another guy analysed the problem ([http://dev.eclipse.org/mhonarc/lists/aether-users/msg00387.html]):(
{quote}{{Also, your analysis suggests a bug in the maven-deploy-plugin in that it relies on
the erroneous assumption that a single class loader is used per plugin through out a multi-module
build.}}
{quote}
All the issues 193, 200, 224, 225, 226 are related to each other.
> deployAtEnd fails if the last project to build skip deployment
> --------------------------------------------------------------
>
> Key: MDEPLOY-200
> URL: https://issues.apache.org/jira/browse/MDEPLOY-200
> Project: Maven Deploy Plugin
> Issue Type: Bug
> Components: deploy:deploy
> Affects Versions: 2.8.2
> Reporter: Victor
> Priority: Major
>
> Hi,
> It seems that with deployAtEnd, if the last project to be built (typically the pom declaring
all the modules of the reactor build) is set as being skipped by maven-deploy-plugin, then
nothing is deployed at the end!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
|