[wtp-releng] Status of our builds and moving to M5

[David M Williams <david_williams@xxxxxxxxxx>]

The builds are at least building again,
but there will be a few compile errors, and quite a few JUnit failures.

We'll revert some M5 specific code,
to see how that improves the JUnit's, but after that, all teams may need
to investigate
and help track down problems. So, here's
all you ever wanted to know about our builds, but were afraid to ask: 

We are still building with M4 as the
base. We'll start looking at moving to M5 soon, but as I'm sure you are
all aware, with the 
removal of the startup.jar, there are
many scripts that will have to change ... and I'm waiting for everyone
else to work the kinks 
out of that, so hopefully once we change,
we'll just have to change once.  
http://wiki.eclipse.org/index.php/PDE_JUnit_Testing
https://bugs.eclipse.org/bugs/show_bug.cgi?id=173742

So, please don't release M5 specific
code until we are cleanly building on M5. 

I suspect it will be in a day or two,
but in the mean time, 
I have been making other changes we'll
need for M5. 

Or third party jars should eventually
all come from the orbit project. 
We will literally re-distribute all
these we need, so end-users won't be effected, 
and even developers will eventually
get these "for free" from a WTP target. 

But until we get some good builds, WTP
developers may have to get the 
jars from their original sources. 

Some, such as xerces, javax.servlet,
javax.servlet.jsp are available from orbit. 
http://download.eclipse.org/tools/orbit/downloads/drops/S200702082257/

Some that have not moved to orbit yet
are (still) available in a small temporary, packaging build of just our
third party bundles. 
http://download.eclipse.org/webtools/committers/drops/R2.0/T-T200702121557-200702121557/wtp-thirdpartyAssembly-T-T200702121557-200702121557.zip

John, please don't delete that "T-build"
for awhile :) 

Chris and team: you use the old "equinox.servlet"
in your web-app custom compile. that should be changed to the javax.servlet
bundle. 

Raghu, I think some JSF bundles used
the older equinox.servlet bundle? If so, that should be changed to the
javax.servlet.jsp bundle. 

All, we may need to specify the pre-req
range of our required JUnit bundle in our test plugins. In what's coming,
the JUnit bundles will now all have 
a symbolic name of "org.junit"
instead of having the version number codified in the name. As always, we
want to pre-req the lowest level possible, but 
all our tests are currently running
in a Java 5 VM. 

Xerces will now be three jarred up bundles,
instead of one directory plugin. So, while eventually transparent to everyone,
if 
you need to get a recent xerces bundle,
you'll have to get all three from orbit, org.apache.xerces, org.apache.xml.resolver,
org.w3c.dom. 

So, sorry for the churn, let us all
know if anyone finds other problems or fixes.