[
http://issues.ops4j.org/jira/browse/PAXCONSTRUCT-92?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=11816#action_11816
]
Hendy Irawan commented on PAXCONSTRUCT-92:
------------------------------------------
Information to make OSGi-friendly WAR/JAR packaging available at:
http://wiki.ops4j.org/confluence/display/ops4j/Getting+the+benefits+of+maven-bundle-plugin+in+other+project+types
> Pax-Construct pax:provision removes the depdency 'type' when creating
> runner/deploy-pom.xml
> -------------------------------------------------------------------------------------------
>
> Key: PAXCONSTRUCT-92
> URL: http://issues.ops4j.org/jira/browse/PAXCONSTRUCT-92
> Project: Pax Construct
> Issue Type: Bug
> Components: scripts
> Affects Versions: 1.3
> Environment: Generic
> Reporter: Hendy Irawan
> Assignee: Stuart McCulloch
> Fix For: 1.4
>
>
> When doing mvn pax:provision, then runner/deploy-pom.xml that is generated
> has the 'type' of every dependency removed.
> Therefore, it is impossible to deploy other bundles with other extensions
> such as war or ear or perhaps others. (There is no need for OSGi bundles to
> have 'jar' extension)
> When getting this issue, I was trying to use Pax Web Extender - War and this
> issue prevents it from working with the project.
> A workaround would be to specify the artifact mvn URL manually.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.ops4j.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
general mailing list
general@lists.ops4j.org
http://lists.ops4j.org/mailman/listinfo/general
