You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@servicemix.apache.org by "Freeman Fang (JIRA)" <ji...@apache.org> on 2009/12/08 17:03:52 UTC

[jira] Updated: (SM-1918) SU dependency from active profile in SA pom should also be taken into account in jbi.xml

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

Freeman Fang updated SM-1918:
-----------------------------

    Summary: SU dependency from active profile in SA pom should also be taken into account in jbi.xml  (was: SU dependency from active profile in SA pom should also be taken into account)

> SU dependency from active profile in SA pom should also be taken into account in jbi.xml
> ----------------------------------------------------------------------------------------
>
>                 Key: SM-1918
>                 URL: https://issues.apache.org/activemq/browse/SM-1918
>             Project: ServiceMix
>          Issue Type: Bug
>    Affects Versions: jbi-maven-plugin-4.1
>            Reporter: Freeman Fang
>            Assignee: Freeman Fang
>             Fix For: jbi-maven-plugin-4.2
>
>
> When a Mavem profile contains a SU dependency, and the profile is activated, jbi:jbi-service-assembly appends the SU.zip to SA correctly, but jbi.xml created by jbi:generate-jbi-service-assembly-descriptor doesn't contain entry about this SU.

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