Community
Participate
Working Groups
We currently build xsl separately from the rest of the wst and wtp. But, we also build it with wst and wtp. So ... during the separate build, if we "prereq" wst as-is, PDE build gets confused since the plugins already exists in the target we are compiling against. (there's a dev. env. version of a bug open against, pde, I think). So, to build, XSL requires we create a wst zip, with the xsl plugins and features removed. In practice, this is easy to do ... and, so I won't forget :) something like the following works cp wtp-wst-sdk-S-3.1M4-20081219210304.zip wtp-xml-sdk-S-3.1M4-20081219210304.zip zip -d wtp-xml-sdk-S-3.1M4-20081219210304.zip \*org.eclipse.wst.xsl\* \*org.eclipse.wst.xml.xpath.\* \*org.eclipse.wst.xml.ui.editor.outline\* As we move forward, hopefully a P2 based build will avoid this problem. And/Or ... we may stop building XSL separately, when we start to build an "XML Product".
This is fixed, for the moment. Long term, we'll try to avoid the whole issue with P2 based builds.
Also, should remove org.apache.commons.jxpath bundle, such as zip -d wtp-xml-sdk-I-3.1-20090430124930.zip \*org.apache.commons.jxpath\*
