Hi,
I would like to get the following improvement into the release:
http://svn.apache.org/viewvc?rev=823280&view=rev.
We have two cases for the compile dependencies on a project:
1) They don't supply any packages to the Import-Package of the current
project
* To certain extent, these dependencies should be downgraded to the runtime
scope as they are not really required for compilation. But that can be
cumbersome as some of them are dragged in transitively from other artifacts.
2) They supply one or more packages to the Import-Package of the current
project
* In this case, such dependencies are pulled in by the PDE
PluginDependencies ClassPathContainer. We used to discard all the
compile-scoped dependencies to avoid duplicate classpath entries against the
PDE container.
With this fix, we now add "compile" scoped dependent projects or jars to the
.classpath file if they don't supply any packages to the Import-Package of
the current project. We simply treat them as runtime dependencies. The new
behavior makes the Eclipse PDE project more consistent with the maven
dependencies as well as the mvn eclipse:eclipse command.
Thanks,
Raymond
--------------------------------------------------
From: "ant elder" <[email protected]>
Sent: Thursday, October 08, 2009 12:30 AM
To: <[email protected]>
Subject: [VOTE] Release Tuscany Maven Bundle Plugin
Please vote on releasing the Tuscany Maven Bundle Plugin.
The Tuscany Maven Bundle Plugin is used by the Tuscany SCA project to
build an OSGi bundle for a project's third-party dependencies,
generate a directory containing OSGi bundles for all the project's
module dependencies, and create Eclipse project files (.project,
.classpath etc) to configure the Eclipse PDE environment for a
project. See the RELEASE_NOTES files changes in this release.
The tag for the release is:
https://svn.apache.org/repos/asf/tuscany/maven-plugins/tags/maven-bundle-plugin-1.0.4/
the Maven staging repository is:
http://people.apache.org/~antelder/tuscany/maven-bundle-plugin-1.0.4-RC1/
+1 from me.
...ant
