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

Way ahead of you. https://issues.jboss.org/browse/JBIDE-11469?focusedCommentId=12684016&... https://issues.jboss.org/browse/JBIDE-11547 https://issues.jboss.org/browse/JBIDE-11546 https://issues.jboss.org/browse/JBIDE-11545 Just wanted to know if we needed that for the components that aren't in our SVN tree (namely, SOA Tooling). On 04/15/2012 04:59 AM, Max Rydahl Andersen wrote: > Why not just do what we do for the CI build ? > > it builds the full source tree without tests as far as I remember ? > > That will reveal any compilation problems without having to create 40+ new jobs ? > > /max > > On Apr 13, 2012, at 18:55 , Nick Boldt wrote: > >> 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 >> > -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com

looks like we are back to ODT disturbing us in Juno too ?! org.apache.maven.InternalErrorException: Internal error: java.lang.RuntimeException: "No solution found because the problem is unsatisfiable.": ["Unable to satisfy dependency from org.apache.jasper 7.0.21.v201203080607 to bundle org.apache.catalina [7.0.21,7.0.22).", "Unable to satisfy dependency from org.apache.tomcat.util 7.0.21.v201203080607 to bundle org.apache.catalina [7.0.21,7.0.22).", "Unable to satisfy dependency from org.eclipse.jdt.core 3.7.1.v_OTDT_r201_201109101025 to org.eclipse.objectteams.otdt.core.patch.feature.group [2.0.0,3.0.0).", "No solution found because the problem is unsatisfiable."] /max On Apr 16, 2012, at 14:50 , Nick Boldt wrote: > Way ahead of you. > > https://issues.jboss.org/browse/JBIDE-11469?focusedCommentId=12684016&... > > https://issues.jboss.org/browse/JBIDE-11547 > https://issues.jboss.org/browse/JBIDE-11546 > https://issues.jboss.org/browse/JBIDE-11545 > > Just wanted to know if we needed that for the components that aren't in our SVN tree (namely, SOA Tooling). > > On 04/15/2012 04:59 AM, Max Rydahl Andersen wrote: >> Why not just do what we do for the CI build ? >> >> it builds the full source tree without tests as far as I remember ? >> >> That will reveal any compilation problems without having to create 40+ new jobs ? >> >> /max >> >> On Apr 13, 2012, at 18:55 , Nick Boldt wrote: >> >>> 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 >>> >> > > -- > Nick Boldt :: JBoss by Red Hat > Productization Lead :: JBoss Tools& Dev Studio > http://nick.divbyzero.com