Hi Reinhard,
Some notes inlined..
<snip>
1) Running eclipse:eclipse should generate the project definition
just as it does now, it detects if a "org.eclipse.pde.PluginNature"
is specified for .project and setups the PDE nature (updates to
.classpath) accordingly.
2) A Bundle Manifest writer could write out the Bundle Manifest. We
could default some of the headers to 'sensible' default values
(extracted from pom.xml), and allow for user to specify them via
configuration for the Eclipse plugin.
3) Plugin dependencies could be copied from the local M2 repo to
under <Plugin>/lib and Manifest updated for Bundle-Classpath values.
I thought I'd rake up a discussion :-)
As Cocoon 3.0 will be based on OSGi I need PDE support too. For the
time being I started with a branch of the maven-eclipse-plugin within
the Cocoon SVN tree (see
http://svn.apache.org/repos/asf/cocoon/trunk/tools/cocoon-maven-eclipse-plugin/).
The goal is providing a patch for the "offical" maven eclipse plugin
within the next weeks.
So far I added the configuration parameter "pde". If set to true, the
PluginNature and the schema and manifest builders are added to
.project.
I have a patch submitted for this for the maven-eclipse-plugin. Though
not sure when that gets integrated into the plugin. IMHO you would not
need a separate config param but just detect the natures being specified
in the config and that should set up PDE project definition.
Additionally, instead of pointing to libraries in the local
repository, I copy them to "target/osgi/lib" and point to them from
within .classpath - unfortunatly PDE doesn't allow referencing
libraries outside of the project (as you describe in 3).
Yep, I noticed that too. Just curious why do want to copy them to the
target/osgi/lib and then reference them from there. Why not copy them
under the PDE project/osgi/lib directory (and may be add that folder to
ignore list in for CVS/SVN). I think you will need to update both
.classpath and Manifest.mf (see 3) for the libs.
Before I will provide a patch, I will implement what you describe in
2). I was thinking of keeping "Bundle-ClassPath" in sync with the
libraries in "target/osgi/lib".
You can also look under Apache Felix sources, they have a maven osgi
plugin implemented, may be you can draw some ideas from there as well.
What do you think?
</snip>
Cheers,
Rahul
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
