You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Steve Kondik (JIRA)" <ji...@apache.org> on 2007/06/08 23:56:33 UTC

[jira] Commented: (SM-891) Maven plugin should use finalName

    [ https://issues.apache.org/activemq/browse/SM-891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39240 ] 

Steve Kondik commented on SM-891:
---------------------------------

This is also an issue with the other mojos (shared libraries, etc).  I'll try to get a patch submitted this week.

> Maven plugin should use finalName
> ---------------------------------
>
>                 Key: SM-891
>                 URL: https://issues.apache.org/activemq/browse/SM-891
>             Project: ServiceMix
>          Issue Type: Bug
>          Components: tooling
>    Affects Versions: 3.1
>            Reporter: Steve Kondik
>            Assignee: Guillaume Nodet
>             Fix For: 3.1.1, 3.2
>
>         Attachments: plugin-finalname.diff
>
>
> When generating a JBI component in Maven, the plugin currently uses "${project.artifactId}-${project.version}.jar" when looking for the original packaged JAR.  This causes problems when the plugin is running in a forked lifecycle that changes the artifact name, such as the Clover plugin (clover:instrument will fail with an exception).
> Attached is a patch (vs. servicemix-3.1) that modifies GenerateComponentMojo to use project.build.finalName instead.  I'm not sure if this is the correct way to do it, but it works here.

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