[jboss-jira] [JBoss JIRA] (JBASMP-57) Dependency is ignored when using "undeploy-artifact"
Martin Höller (JIRA)
issues at jboss.org
Fri Feb 14 08:35:29 EST 2014
[ https://issues.jboss.org/browse/JBASMP-57?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12944666#comment-12944666 ]
Martin Höller commented on JBASMP-57:
-------------------------------------
Same problem with wildfly-maven-plugin 1.0.0.Final and wildfly 8.0.0.Final.
> Dependency is ignored when using "undeploy-artifact"
> ----------------------------------------------------
>
> Key: JBASMP-57
> URL: https://issues.jboss.org/browse/JBASMP-57
> Project: JBoss AS Maven Plugins
> Issue Type: Bug
> Components: deploy
> Affects Versions: 7.5.Final
> Environment: Windows 7 - Maven 3.0.5 - EAP 6.1
> Reporter: Dieter Scholz
> Assignee: James Perkins
>
> Hello,
> I don't know if it's a bug.
> This is my situation:
> I define the configuration of the JBoss plugin in a profile that is located in the parent POM module of my project.
> Another module creates an EAR distribution.
> The last module uses the profile defined in the parent POM and runs the (local) JBoss instance. The EAR is listed as a dependency and inside the undeploy configuration with group and artifact id.
> Everything works fine but the undeploy (in the post-integration-test phase). The exception occurs in line 92 of the UndeployArtifact class.
> I found that in this case the call project.getArtifacts() (used a few lines before) returns a null-Set. If I change the call to project.getDependencyArtifacts() all dependencies are returned and the undeploy phase runs just fine.
> Is this a bug or a misconfiguration on my side? I am able to provide code samples if necessary.
> Greetings, Dieter
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list