>>>>> "Tom Huybrechts" <[EMAIL PROTECTED]>:

>> One complication is that the source plugins are directories rather
>> than JARs.  I don't know if they have to be.  Can maven handle
>> artifacts that are directories?  Or do they have to be single files?
>> Can the dependency-maven-plugin be persuaded to unpack a JAR into a
>> directory, when installing into $HOME/pde_target_platform/plugins/?

> If I remember correctly, you need a directory per bundle. Inside that
> bundle, you create one src.zip file corresponding to the classes in
> the root of your bundle-classpath, and one XXXsrc.zip per embedded
> XXX.jar

I just successfully created one using a bourne shell script.  The
structure looked like this, as seen from the PDE target platform
plugins directory:
  bundlename-source-bundleversion/
  bundlename-source-bundleversion/META-INF/MANIFEST.MF
  bundlename-source-bundleversion/plugin.xml
  bundlename-source-bundleversion/src/bundlesymbolicname_bundleversion/src.zip

(the reason for injecting the extra directory under src, was that
that's what eclipse's own source plugins did.  But when I think of it,
I did it wrong.  Because eg. GEF's structure is to have one directory
for each actual bundle it carries source for.  I used the source
bundle's bundle name.   But I think it doesn't matter since it just
scans down the src file, finds zip files and looks for source in them)

> I doubt the manifest is important, just the plugin.xml should do...

The MANIFEST.MF had to be there for eclipse to plug it up as a
plugin.  I tried both with and without.

I didn't try paring the manifest down to a minimum, I more or less
copied one of an eclipse source bundle and changed what was
appropriate, but I believe what minimally has to be there, is
Bundle-SymbolicName and Bundle-Version.

Those are the two values that show up in the Plug-ins explorer
treeview. 

So now the question is whether it's possible to coerce maven into
creating something similar...?


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to