[jira] Commented: (SM-1202) Maven plugin not including jbi.xml and legal files in SA artifacts

["Chris Custine (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/activemq/browse/SM-1202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=41126#action_41126 ] 

Chris Custine commented on SM-1202:
-----------------------------------

I couldn't see why the working directory needed to be moved to the sus dir since the su's and the modified manifest are included correctly in the regular target/${artifactId}-${version} directory, so this patch cleans up the jbi-maven-plugin to match earlier behavior and everything seems to work fine.

> Maven plugin not including jbi.xml and legal files in SA artifacts
> ------------------------------------------------------------------
>
>                 Key: SM-1202
>                 URL: https://issues.apache.org/activemq/browse/SM-1202
>             Project: ServiceMix
>          Issue Type: Bug
>          Components: tooling
>    Affects Versions: 3.3
>            Reporter: Chris Custine
>             Fix For: 3.3
>
>         Attachments: SM-1202.patch
>
>
> It looks like the recent changes to add OSGi manifest info accidentally prevents the inclusion of the jbi.xml and legal files from target/classes, so using the jbi-maven-plugin from trunk (3.3-SNAPSHOT) to build SA's causes deployments to fail in certain situations.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.