I think the removal of the third party jar is OK but we just have to update the plugin.xml to point to the orbit xalan jar. I already changed the extension point so that if the jar name being with ${orbit: then it will try to locate the jar in the set of plugins. i can't remember whether I already change the plugin.xml, I'll check later.
----- Original Message ----
From: David M Williams <david_williams@xxxxxxxxxx>
To: WTP Incubator Dev list <wtp-incubator-dev@xxxxxxxxxxx>
Sent: Monday, 11 February, 2008 5:34:10 PM
Subject: Re: [wtp-incubator-dev] Status of Builds for M5 and a question on non-jarred plugins
Thanks Doug ... I've opened bug 218535 to track the jarring up plugins issue. (Knowing me, I probably opened one last time we discussed too :( And, I've tried to revert the org.eclipse.wst.xsl.xalan so it builds itself into a jar with a known name, as before. But .. we may have to revert the whole "third party jar" work I did until this issue is better understood? Feel free to revert back to it's pre-Orbit work I did, if it doesn't work as is. And we'll deal with the Orbit issues later. Thanks,
| From:
| DOUG SATCHWELL <doug.satchwell@xxxxxxxxxxxxxx>
|
| To:
| WTP Incubator Dev list <wtp-incubator-dev@xxxxxxxxxxx>
|
| Date:
| 02/11/2008 10:15 AM
|
| Subject:
| Re: [wtp-incubator-dev] Status of Builds for M5 and a question on non-jarred plugins |
Hi David - I think we've been through this before on this list...but the reason is that neither of these plugins actually contribute anything to the Eclipse classpath, they simply build jars that are needed for when a transform is launched. It is very important that we know the name and location of the built jars, and also that we don't jar the bundles, so that we can add the built jars to the classpath of the launched process. In fact I notice that version 1.2 of build.properties in org.eclipse.wst.xsl.xalan is broken because it no longer specifes the name of the jar to be created...this needs to be fixed or else the launching won't work when the project is built! ----- Original Message ----
From: David
M Williams <david_williams@xxxxxxxxxx>
To: wtp-incubator-dev@xxxxxxxxxxx
Sent: Sunday, 10 February, 2008 9:44:18 PM
Subject: [wtp-incubator-dev] Status of Builds for M5 and a question on non-jarred plugins
I've changed the build scripts to produce "S" builds now, instead of "I" builds.
I'm using the xalan jar from Orbit, instead of having our own "embedded" one.
I am done experimenting with signing now, so if you see an S build that is signed, it's an error.
(and ... let me know!).
And, an important question ... I've noticed that two plugins are not jarred up.
org.eclipse.wst.xsl.xalan
org.eclipse.wst.xsl.debug
Why is that? Was it because they contained embedded jars?
If so,
org.eclipse.wst.xsl.xalan
no longer does ... so, guess we could jar that one up.
And ... why is there two jars in
org.eclipse.wst.xsl.debug?
History? Or some functional need?
Can we eliminate them, and jar up that plugin too?
Thanks, _______________________________________________
wtp-incubator-dev mailing list
wtp-incubator-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-incubator-dev
