Re: [jbosstools-dev] Moving Eclipse 3.7/Indigo onto trunk

Branch is now building 3.2.1.CR1 / 4.1.0.CR1*, with TP pointing at Eclipse 3.6 Helios (as before). Test failures: https://issues.jboss.org/browse/JBIDE-8551 (jsf) https://issues.jboss.org/browse/JBIDE-8552 (seam) https://issues.jboss.org/browse/JBIDE-8581 (cdi) https://issues.jboss.org/browse/JBIDE-8627 (cdi) https://issues.jboss.org/browse/JBIDE-8628 (seam) https://issues.jboss.org/browse/JBIDE-8636 (hibernate) Trunk is now (not**) building 3.3.0.M1 / 5.0.0.M1, with TP pointing at Eclipse 3.7 Indigo (my changes merged in from 3.3.helios branch). Component changes have yet to be merged in - assuming component leads &/or devs will do this. Test failures: https://issues.jboss.org/browse/JBIDE-8032 (struts) https://issues.jboss.org/browse/JBIDE-8404 (jsf) https://issues.jboss.org/browse/JBIDE-8638 (jsf) -- * - Upversioned from 4.0.1. ** - I've found and fixed a problem in the parent pom so this should be working now. Once the TP/PP job [1] is done in about 90 mins, I can verify my fix worked. [1] http://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.target-platfor... Nick On 03/29/2011 05:27 AM, Max Rydahl Andersen wrote: -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com