Nick, We would probably have to use Eclipse 4.3M5a because it contains the fix for https://issues.jboss.org/browse/JBIDE-13490 Snjeza On 2/7/2013 8:39 PM, Nick Boldt wrote: > In case you missed it, the sources for the new Kepler M5 target > platforms for JBT 4.1 / JBDS 7.0 are located here: > > https://github.com/jbosstools/jbosstools-target-platforms/tree/4.3.0 > > The resulting built target platform sites are here (unpacked sites and > zips too, for use offline): > > http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/ > http://www.qa.jboss.com/binaries/RHDS/targetplatforms/jbdevstudiotarget/ > (VPN required) > > Currently, the only difference between the JBT and JBDS target platforms > is that the JBDS one excludes swtbot, birt, and GWT/GPE. Therefore, if > you can't access the JBDS one and don't want to build it locally, you > should be fine to use the JBT one. > > This change is documented here: > > https://github.com/jbosstools/jbosstools-build/blob/master/target-platfor... > -and- > https://issues.jboss.org/browse/JBIDE-13386 > > Cheers, > _______________________________________________ jbosstools-dev mailing list jbosstools-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jbosstools-dev

My +1 for this! Regards, Victor On 02/08/2013 11:17 PM, Snjezana Peco wrote: > Nick, > > We would probably have to use Eclipse 4.3M5a because it contains the fix > for https://issues.jboss.org/browse/JBIDE-13490 > > Snjeza > > On 2/7/2013 8:39 PM, Nick Boldt wrote: >> In case you missed it, the sources for the new Kepler M5 target >> platforms for JBT 4.1 / JBDS 7.0 are located here: >> >> https://github.com/jbosstools/jbosstools-target-platforms/tree/4.3.0 >> >> The resulting built target platform sites are here (unpacked sites and >> zips too, for use offline): >> >> http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/ >> http://www.qa.jboss.com/binaries/RHDS/targetplatforms/jbdevstudiotarget/ >> (VPN required) >> >> Currently, the only difference between the JBT and JBDS target platforms >> is that the JBDS one excludes swtbot, birt, and GWT/GPE. Therefore, if >> you can't access the JBDS one and don't want to build it locally, you >> should be fine to use the JBT one. >> >> This change is documented here: >> >> https://github.com/jbosstools/jbosstools-build/blob/master/target-platfor... >> -and- >> https://issues.jboss.org/browse/JBIDE-13386 >> >> Cheers, >> > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev > > _______________________________________________ jbosstools-dev mailing list jbosstools-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jbosstools-dev

New bits are being mirrored as we speak from eclipse.org to qa cluster, despite slow mirrors & snow drifts. When that's done I'll: * push them to download.jboss.org * update the .target files from version 4.30.2 to 4.30.3 * rebuild the target sites * update the parent pom TARGET_PLATFORM_VERSION from version 4.30.2 to 4.30.3 * respin the buildflow jobs to verify everything builds w/ the updated TP: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-buildflow... On 02/08/2013 03:08 PM, Victor Rubezhny wrote: > My +1 for this! > > Regards, > Victor > > On 02/08/2013 11:17 PM, Snjezana Peco wrote: >> Nick, >> >> We would probably have to use Eclipse 4.3M5a because it contains the >> fix >> for https://issues.jboss.org/browse/JBIDE-13490 >> >> Snjeza >> >> On 2/7/2013 8:39 PM, Nick Boldt wrote: >>> In case you missed it, the sources for the new Kepler M5 target >>> platforms for JBT 4.1 / JBDS 7.0 are located here: >>> >>> https://github.com/jbosstools/jbosstools-target-platforms/tree/4.3.0 >>> >>> The resulting built target platform sites are here (unpacked sites and >>> zips too, for use offline): >>> >>> http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/ >>> http://www.qa.jboss.com/binaries/RHDS/targetplatforms/jbdevstudiotarget/ >>> >>> (VPN required) >>> >>> Currently, the only difference between the JBT and JBDS target >>> platforms >>> is that the JBDS one excludes swtbot, birt, and GWT/GPE. Therefore, if >>> you can't access the JBDS one and don't want to build it locally, you >>> should be fine to use the JBT one. >>> >>> This change is documented here: >>> >>> https://github.com/jbosstools/jbosstools-build/blob/master/target-platfor... >>> >>> -and- >>> https://issues.jboss.org/browse/JBIDE-13386 >>> >>> Cheers, >>> >> _______________________________________________ >> jbosstools-dev mailing list >> jbosstools-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jbosstools-dev >> >> > > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev >

Why do you want to build target platfroms? They are available from Nexus so you don't need local builds to use them. -- Mickael Istria Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools> My blog <http://mickaelistria.wordpress.com> - My Tweets <http://twitter.com/mickaelistria> _______________________________________________ jbosstools-dev mailing list jbosstools-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jbosstools-dev

Why do you want to build target platfroms?

They are available from Nexus so you don't need local builds to use them.

Actually not only. I need to test an issue against eclipse 4.3M5a (which was to be included into 4.3.0 TPs at Friday) but with not updating the jbosstools-target-platforms I see that my component (jbosstools-jst) is still built and tested against eclipse 4.3M5 (not M5a). So, the point was to refresh and rebuild TP in my repo... And it's failed.

I'm using -P maximum argument when building and testing my components...

Also, shouldn't the latest TP version be used when building? Should I manually specify something like -DTARGET_PLATFORM_VERSION=4.30.3.Alpha1-SNAPSHOT due to make sure that the latest TP will be used?

Ok, but if so, eclipse 4.3M5a still isn't included to our latest TP? I thought that Nick has done this at Friday evening...

Victor: If you're using 4.30.3, then yes, M5a will be in there. If it's not, open a JIRA showing the IUs you expect to see which are in fact missing and I will get that fixed. I'm seeing jdt, pde, platform & rcp plugins versioned 4.3.0.v201302041400 [1], which aligns with the version on the M5a page [2]: [1] http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.3... [2] http://download.eclipse.org/eclipse/downloads/drops4/S-4.3M5a-201302041400/ Try using the "unified" target instead of the "multiple" one -- it will pull from the TP update site on jboss.org instead of pulling from eclipse.org directly. Cheers, N On 02/11/2013 08:26 AM, Mickael Istria wrote: > On 02/11/2013 02:25 PM, Victor Rubezhny wrote: >> >> Ok, but if so, eclipse 4.3M5a still isn't included to our latest TP? I >> thought that Nick has done this at Friday evening... > That could be a bug in the target-platform. Please report it in a Jira. > -- > Mickael Istria > Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools> > My blog <http://mickaelistria.wordpress.com> - My Tweets > <http://twitter.com/mickaelistria> > > > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev >

Nick, Just forked it and here is the log eskimo@dgolovin-desktop:~/Projects/jbds/jbosstools-fork-submodules$ git submodule add git@github.com:dgolovin/jbosstools-target-platforms.git jbosstools-target-platforms Cloning into 'jbosstools-target-platforms'... remote: Counting objects: 6773, done. remote: Compressing objects: 100% (2351/2351), done. remote: Total 6773 (delta 3488), reused 6756 (delta 3471) Receiving objects: 100% (6773/6773),*53.70 MiB* | 974 KiB/s, done. Resolving deltas: 100% (3488/3488), done. It is to much for such a small young repository? for example jbosstools-jst with all its history more than twice less space. eskimo@dgolovin-desktop:~/Temp$ git clone git@github.com:jbosstools/jbosstools-jst.git Cloning into 'jbosstools-jst'... X11 forwarding request failed on channel 0 remote: Counting objects: 37604, done. remote: Compressing objects: 100% (5442/5442), done. remote: Total 37604 (delta 19647), reused 37454 (delta 19501) Receiving objects: 100% (37604/37604), *23.94 MiB* | 659 KiB/s, done. Resolving deltas: 100% (19647/19647), done. Why do you keep master branch empty? Are there some reasons to have branches named different from the actual versions? Thanks Denis On 02/07/2013 11:39 AM, Nick Boldt wrote: > In case you missed it, the sources for the new Kepler M5 target > platforms for JBT 4.1 / JBDS 7.0 are located here: > > https://github.com/jbosstools/jbosstools-target-platforms/tree/4.3.0 > > The resulting built target platform sites are here (unpacked sites and > zips too, for use offline): > > http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/ > http://www.qa.jboss.com/binaries/RHDS/targetplatforms/jbdevstudiotarget/ > (VPN required) > > Currently, the only difference between the JBT and JBDS target platforms > is that the JBDS one excludes swtbot, birt, and GWT/GPE. Therefore, if > you can't access the JBDS one and don't want to build it locally, you > should be fine to use the JBT one. > > This change is documented here: > > https://github.com/jbosstools/jbosstools-build/blob/master/target-platfor... > -and- > https://issues.jboss.org/browse/JBIDE-13386 > > Cheers, >

It is to much for such a small young repository?

for example jbosstools-jst with all its history more than twice less space.

Why do you keep master branch empty?

Are there some reasons to have branches named different from the actual versions?

Thanks Denis On 02/07/2013 11:39 AM, Nick Boldt wrote: > In case you missed it, the sources for the new Kepler M5 target > platforms for JBT 4.1 / JBDS 7.0 are located here: > > > https://github.com/jbosstools/jbosstools-target-platforms/tree/4.3.0 > > > The resulting built target platform sites are here (unpacked sites and > zips too, for use offline): > > > http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/ > http://www.qa.jboss.com/binaries/RHDS/targetplatforms/jbdevstudiotarget/ > > (VPN required) > > Currently, the only difference between the JBT and JBDS target platforms > is that the JBDS one excludes swtbot, birt, and GWT/GPE. Therefore, if > you can't access the JBDS one and don't want to build it locally, you > should be fine to use the JBT one. > > This change is documented here: > > > https://github.com/jbosstools/jbosstools-build/blob/master/target-platfor... > > -and- > > https://issues.jboss.org/browse/JBIDE-13386 > > > Cheers, > > _______________________________________________ jbosstools-dev mailing list jbosstools-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jbosstools-dev

never mind - spotted it now...yeah - branches got specific versions (4.3.0) where it should have been something like 4.3.0.x, but then the actual version inside the repo says 4.30.<something>. Yeah - thats not very consistent. :( Have to fix that somehow without breaking past builds.