[jira] Resolved: (SM-1157) maven-jbi-plugin creates wrong classpath entries in jbi.xml for SE

["Bruce Snyder (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/activemq/browse/SM-1157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bruce Snyder resolved SM-1157.
------------------------------

    Resolution: Fixed

Committed to the 3.2 branch via [revision |http://svn.apache.org/viewvc?rev=614094&view=rev]. 

Committed to the trunk (3.3) via [via revision 614095|http://svn.apache.org/viewvc?rev=614095&view=rev]. 

> maven-jbi-plugin creates wrong classpath entries in jbi.xml for SE
> ------------------------------------------------------------------
>
>                 Key: SM-1157
>                 URL: https://issues.apache.org/activemq/browse/SM-1157
>             Project: ServiceMix
>          Issue Type: Bug
>          Components: tooling
>            Reporter: Tammo van Lessen
>             Fix For: 3.2.2, 3.3
>
>         Attachments: jbi-maven-patch.txt
>
>
> When the m2 build is customized and a <finalname> is set (i.e. is different to ${artifactname}-${version}), the generated jbi.xml is wrong.
> I guess the problem is located in Line 207in GenerateComponentDescriptorMojo.java
> Should be something like project.getBuild().getFinalName()
> http://maven.apache.org/ref/current/maven-model/apidocs/org/apache/maven/model/BuildBase.html#getFinalName()
> http://maven.apache.org/ref/2.0.4/maven-project/apidocs/org/apache/maven/project/MavenProject.html#getBuild()
> Cheers,
>   Tammo

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