You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org> on 2010/01/25 08:53:43 UTC

[jira] Assigned: (SM-1812) jbi-maven-plugin and package goal support

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

Jean-Baptiste Onofré reassigned SM-1812:
----------------------------------------

    Assignee: Jean-Baptiste Onofré

> jbi-maven-plugin and package goal support
> -----------------------------------------
>
>                 Key: SM-1812
>                 URL: https://issues.apache.org/activemq/browse/SM-1812
>             Project: ServiceMix
>          Issue Type: Bug
>          Components: tooling
>    Affects Versions: 4.0
>         Environment: Maven 2.0.9
> Sun JDK 1.5
> ServiceMix 3.3
> JBI Maven Plugin 4.0
>            Reporter: Jean-Baptiste Onofré
>            Assignee: Jean-Baptiste Onofré
>
> When building a project containing a SA and one or more SU with the 'package'
> task, two things can happen:
> - if the SU is not present in the local repository (ex: first time building the
> project with a version), the build will fail as the SA cannot find the SU
> - if the SU is already in the local repository, the build will succeed but the
> packaged SU will be the one present in the repository not the one we just
> built, which may result in an invalid SA
> The jbi-maven-plugin should resolves SU in the same way as the dependency
> plugin: look for a SU built in the current project first, then local repository
> later, instead of always looking in the local repository.
> The main issue with this bug is that it prevents the release plugin from
> working, as it uses the package task.

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