Peter Kriens wrote:
you seem to be completely entangled in the clash between
Maven, and PDE. Not a pretty picture :-(
Just imagine what my brain is like. Got to debug that first ;) This is a
big help.
I think Maven is not a friend of PDE. The main reason is that PDE
maintains a set of bundles in the Target platform (see Eclipse
preferences) and more or less randomly picks providers from that set if
you organize your manifest. At the same time you have Maven that is
selecting imports from its repository. So you have two programs both
wanting to be in charge of the classpath and manifest. Looking at your
POM, your classpath must be a total entangled mess, e.g. split package
directives are rarely necessary, they usually indicate your classpath is
not managed and contains the same jars several times.
Those and the <_failok/> are vestiges of the com.ibm.icu meltdown
mentioned below that was causing even mvn eclipse:eclipse to fail.
An ArrayBounds exception in bnd somewhere. I'll send stack traces if
this resurfaces; its gone away for now. I think due to a bad class on
some repository somewhere. I saw it reported in a jira and didn't dig
further.
So you should make a choice between Maven OR PDE. If you pick Maven, you
That's JUST what I needed to know. I'm going with mvn then. This isn't
an eclipse plugin; its a server app.
I really would not know how to combine Maven and PDE :-( I know some
people are including the manifest from PDE in the pom:
<_include>~META-INF/MANIFEST.MF</_include>
I may give that a try once I get my mental model sorted out.
This will read the manifest from PDE, which means you have at least a
single definition of the manifest data shared between Maven and Eclipse.
The ~ indicates that any properties from the POM have priority over
manifest headers. However, it still means you have 2 classpaths. PDE has
his internal magic class path based on the Target platform, which can
not be read externally. Maven will have his repository based classpath.
That is, you will have to make sure these classpaths match, and this a
manual job last time I looked.
Does this mean the "Maven Dependencies" and "Plugin Dependencies"; two
separate entries in the "Build Settings" screen? These were constantly
getting crossed up, blocking the build with "same jar in two places"
errors. I'd been working around that by deleting Plugin Preferences.
Wish folks could agree on common names for such things. Which Plugin?
Maven's? Eclipse's? Argggh!
I know Jason van Zyl (Maven) and Jeff McAffer (Eclipse) are working on
creating an Eclipse plugin for maven. This would solve many of your
problems.
I've seen a number of blogs that claim to fix this. That's one of my
problems, knowing which blogs to believe ;)
In your pom, you manually add a zillion split-package: directives. I
guess you got a warning that there were split packages. This means that
bnd found multiple jars exporting the same package and was unsure what
to do: merge, first, or last. In my opinion, it is usually always wrong
and just means the same jar is on the classpath twice. Just cleanup the
classpath and the message goes away. The bnd diagnostic shows in which
jars it found the duplicate packages.
Yeah, flailing away. Suggestion: I couldn't understand bnd's error
message; just a long list of jar names with no indication of which is
the problem. So I put that directive everywhere, not knowing where it
was needed.
So my suggestion is to use JDT and let maven be in charge, until the
Eclipse Maven plugin becomes available. Or take a look what standalone
bnd can do for you.
That's just what I'll do. Thanks!
Do you mean http://maven.apache.org/eclipse-plugin.html ? I've been
trying to use that too which just adds to the confusion. Two of these
out there, Q for Eclipse and I recall another one. Hard to know which
ones to believe.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
