[jboss-jira] [JBoss JIRA] (WFBUILD-33) Support non-jar artifacts properly

[Peter Palaga (JIRA)]

    [ https://issues.jboss.org/browse/WFBUILD-33?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13522917#comment-13522917 ] 

Peter Palaga commented on WFBUILD-33:
-------------------------------------

Work in progress https://github.com/ppalaga/wildfly-build-tools/commits/WFBUILD-33

> Support non-jar artifacts properly
> ----------------------------------
>
>                 Key: WFBUILD-33
>                 URL: https://issues.jboss.org/browse/WFBUILD-33
>             Project: WildFly Build Tools
>          Issue Type: Bug
>            Reporter: Peter Palaga
>            Assignee: Peter Palaga
>
> The immediate impetus for reporting this is the fact that after upgrading from 1.1.6.Final to 1.2.6.Final our 
> {code}
> <copy-artifact artifact="io.hawt:hawtio-wildfly" to-location="standalone/deployments/"/>
> {code}
> stopped working for the FP plugin. Changing it to 
> {code}<copy-artifact artifact="io.hawt:hawtio-wildfly:war" to-location="standalone/deployments/"/>{code}
> by adding :war made the FP plugin happy, but it made the provisioning plugin fail with an NPE.
> It looks like the code parsing and the rendering the groupId:artifactId:type:classifier:version strings is scattered over several methods whose behavior is not 100% consistent.
> The current objective is:
> (1) Write a few integration tests to pin the behavior before the change, identifying the broken cases
> (2) Write the actual fix in such a way that the plugins stay as backwards compatible as possible.
> I have a fix that works for me, I just need to ensure, my changes keep the plugins backwards compatible.



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)