[overlord-issues] [JBoss JIRA] (SRAMP-514) Allow generate-features-xml to use dirs on the classpath, rather than artifact jars only

[Brett Meyer (JIRA)]

     [ https://issues.jboss.org/browse/SRAMP-514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Meyer closed SRAMP-514.
-----------------------------
    Resolution: Out of Date


> Allow generate-features-xml to use dirs on the classpath, rather than artifact jars only
> ----------------------------------------------------------------------------------------
>
>                 Key: SRAMP-514
>                 URL: https://issues.jboss.org/browse/SRAMP-514
>             Project: S-RAMP
>          Issue Type: Enhancement
>            Reporter: Brett Meyer
>            Assignee: Eric Wittmann
>            Priority: Optional
>
> Definitely a low priority...
> https://overlord.ci.cloudbees.com/job/s-ramp.master.integration/job/s-ramp.master.integration.tomcat/2/console
> When that's configured to use "mvn clean test", generate-features-xml blows up.  But, it works with "mvn clean install".  Oddly enough, "test" works perfectly locally.
> {quote}
> [ERROR] Failed to execute goal org.overlord:overlord-commons-maven-plugin:2.0.3-SNAPSHOT:generate-features-xml (default) on project s-ramp-distro-fuse61: Resolved artifact is not a file: /scratch/jenkins/workspace/s-ramp.master.integration/s-ramp.master.integration.tomcat/s-ramp-api/target/classes
> {quote}
> I'm not at all sure what's causing the artifact to resolve to /classes, rather than the actual jar.  But, theoretically, we should be able to improve the mojo to use directories, rather than require jars.



--
This message was sent by Atlassian JIRA
(v6.3.8#6338)