----- Original Message -----
From: "Gerard Ryan" <galileo(a)fedoraproject.org>
Sent: Thursday, May 31, 2012 10:03:39 PM
Subject: [fedora-java] Eclipse plugins questions
-----BEGIN PGP SIGNED MESSAGE-----
So, I haven't got much experience with building eclipse plugins, but
that is changing quickly.
For JBoss Tools, I need some additional parts of wtp, which I have
trying to do over the last few days. One problem I'm running into, is
that some stuff that I need from there seems to depend on old
of stuff that we have in fedora, and I don't know what to do in this
Example: I'm trying to build the feature
org.eclipse.wst.ws_core.feature, in wtp-webservices. One of the
that this feature builds is org.eclipse.wst.wsdl.validation. This
depends on org.apache.xerces 2.8.0. In fedora, we've got 2.11.0.
Somewhere between these two versions, some things changed, and the
plugin is not fully compatible with the new version. See the
[javac] 6. ERROR in
(at line 311)
[javac] public void reportError(String domain, String key,
arguments, short severity) throws XNIException
[javac] The return type is incompatible with
XMLErrorReporter.reportError(String, String, Object, short)
If I comment org.eclipse.wst.wsdl.validation out of the feature, try
rebuild, there will be new errors, because other plugins depend on
different versions of other stuff.
What's the next step here? Here's a few possibilities rolling around
head, I'm not sure if any of them are right:
- - package the older versions of deps for fedora. I'm pretty sure
isn't the answer.
- - patch all of the files to fix the errors, and apply those patches
the fedora package. This doesn't feel right either, as there would be
quite a large number of patches.
- - submit patches upstream, wait until they are accepted, then
for fedora. This sounds the most right I think, but I've no idea if
patches will be accepted (upstream might be sticking to older deps
good reasons, so as not to break other stuff). I'm also under time
constraints, as I'm packaging JBoss Tools as part of Google Summer of
Are any of these the right way to go about this, or are there other
The correct answer is 2+3. Patch it to use the version in Fedora, put the package in
Fedora and send the patch for inclusion upstream.
Gerard Ryan :: galileo(a)fedoraproject.org ::