Re: [jbosstools-dev] Time to start using, testing, and building JBT & JBDS against Juno!

New Juno M6-based target platforms are available for use w/ your local builds. Do we need to have 40+ new jobs created to run the various components against these TPs, or can people take it upon themselves to try this effort locally? Here's all you need to do to test the TP and see if your bits work w/ the new Eclipse version: a) download new TP zip [1]. Unpack on disk. b) mvn clean install ... -Plocal.site -Dlocal.site=file:///path/to/juno.M6/target-platform/ If you prefer to use the remote repo, override the default Indigo SR2 site with this: -Djbosstools-target-site=http://download.jboss.org/jbosstools/updates/target-platform_3.3.juno.M6/latest/ [1] http://download.jboss.org/jbosstools/updates/target-platform_3.3.juno.M6/ On 04/11/2012 03:39 PM, Nick Boldt wrote: > As Juno is scheduled to be released this June, and is already on its M6 > milestone, it's time to start trying it out to find out what will break > in JBoss Tools / Dev Studio when installed into or built against Juno, > so we can either report issue upstream to eclipse.org, or fix them in > our code so we can run on both 3.7 and 4.2/3.8. > > We now have a Juno Composite Requirements Site which you can use for > building/testing against the latest Juno M6 milestone (Eclipse 4.2 / 3.8). > > http://download.jboss.org/jbosstools/updates/juno/ > > I'll be producing 2 new jobs shortly to generate Target Platforms (one > for JT, one for JBDS) using these bits instead of the Indigo SR2 ones. > > Comments? Please post thoughts to > https://issues.jboss.org/browse/JBIDE-11469 > -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com