[
http://issues.ops4j.org/jira/browse/PAXCONSTRUCT-66?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_11073
]
Stuart McCulloch commented on PAXCONSTRUCT-66:
----------------------------------------------
FYI, here's how I typically use scopes when building bundles in Maven:
"compile" - contains classes/resources that I want to embed
because my code needs them to load and I don't
expect them to be provided by another bundle.
"runtime" - contains classes/resources that I want to embed
because my code might need them during runtime
(via reflection, etc.) and I don't expect them to be
provided by another bundle
"provided" - contains classes/resources that I expect to be
provided by another bundle or the framework
"test" - contains classes/resources used in any unit or
integration tests (ie. not needed to load/run the
bundle - just needed to test with)
> Add all Maven compilation dependencies to the Eclipse classpath
> ---------------------------------------------------------------
>
> Key: PAXCONSTRUCT-66
> URL: http://issues.ops4j.org/jira/browse/PAXCONSTRUCT-66
> Project: Pax Construct
> Issue Type: Improvement
> Components: maven-pax-plugin
> Affects Versions: 0.6.4
> Reporter: Stuart McCulloch
> Assignee: Stuart McCulloch
> Priority: Minor
> Fix For: 1.0
>
>
> Currently, the maven-pax-plugin only adds provided and test dependencies to
> the Eclipse classpath.
> This is done because Eclipse/PDE uses the manifest to determine the Plug-in
> Dependencies, so we
> cannot assume these dependencies will be found by PDE even if they are
> plug-ins or OSGi bundles.
> Therefore we add them as Required Libraries, so they will always be found.
> Compile and runtime scope dependencies weren't previously added because it
> was assumed they
> would be used when embedding content inside bundles - and embedded entries
> already appear on
> the classpath, hence no need to add the raw dependencies.
> However, people often add bundle dependencies with the default scope
> (compile) which means that
> they wouldn't see these dependencies (as they might expect) - so to make
> things simpler I've decided
> to add *all* Maven dependencies to the Eclipse classpath.
--
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
