[
http://issues.ops4j.org/jira/browse/PAXRUNNER-159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=11631#action_11631
]
Stuart McCulloch commented on PAXRUNNER-159:
--------------------------------------------
Processing transitive dependencies properly would require a full-blown embedded
version of Maven, rather than the much simpler artifact logic already in place.
You might want to consider using the pax-construct scripts, or the
maven-pax-plugin, which (because they use maven) will process transitive
dependencies and store them in a single deployment pom which is then passed on
to pax-runner for the actual provisioning. For example:
mvn org.ops4j:maven-pax-plugin:provision
or if you have the pax-construct scripts installed on your path:
pax-provision
See http://www.ops4j.org/projects/pax/construct/help/provision.html and
http://www.ops4j.org/projects/pax/construct/maven-pax-plugin/provision-mojo.html
> pom scanning should find transitive depedencies
> -----------------------------------------------
>
> Key: PAXRUNNER-159
> URL: http://issues.ops4j.org/jira/browse/PAXRUNNER-159
> Project: Pax Runner
> Issue Type: Improvement
> Components: scanner pom
> Reporter: Richard Wallace
> Assignee: Alin Dreghiciu
>
> The pom scanning currently only gets dependencies that are declared in the
> pom. This means that any transitive dependencies are ignored and must be
> added directly to the pom.
--
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
[email protected]
http://lists.ops4j.org/mailman/listinfo/general
