In context of XXX Rob was asking what version of WTP we are using.

That is best found by looking in the build/target-platform/*.target files (they list the exact feature versions we extract) or the less precise but kinda close list of requirement folders listed in http://download.jboss.org/jbosstools/updates/helios/compositeArtifacts.xml But that doesn't actually help when you want to check what version of org.eclipse.jst.common.frameworks will end up in the distro since this plugin is not listed in any feature as far as Rob and I can see. So, beyond just *hoping* the right plugin gets into the build what is the better/best way of checking this (beyond downloading additional 4-600 MB of builds to see what is in the resulting binary) ? /max http://about.me/maxandersen

E:\eclipse\eclipsec.exe -application org.eclipse.equinox.p2.director -repository http://download.jboss.org/jbosstools/updates/helios -installIU org.eclipse.jst.common.frameworks -destination E:\temp\eclipse -profile SDKProfile -noSplash You will get: Installing org.eclipse.jst.common.frameworks 1.1.403.v201012160000.

Snjeza Max Rydahl Andersen wrote: > In context of XXX Rob was asking what version of WTP we are using. > > That is best found by looking in the build/target-platform/*.target files (they list the exact feature versions we extract) > or the less precise but kinda close list of requirement folders listed in http://download.jboss.org/jbosstools/updates/helios/compositeArtifacts.xml > > But that doesn't actually help when you want to check what version of org.eclipse.jst.common.frameworks > will end up in the distro since this plugin is not listed in any feature as far as Rob and I can see. > > So, beyond just *hoping* the right plugin gets into the build what is the better/best way of checking this (beyond > downloading additional 4-600 MB of builds to see what is in the resulting binary) ? > > /max > http://about.me/maxandersen > > > > > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev >

Well, you could look in the target platform itself to see what's included: http://download.jboss.org/jbosstools/updates/target-platform/latest/plugins/ (yet another reason why an update site is WAY BETTER than a .target file)

Nick On 05/31/2011 04:25 AM, Max Rydahl Andersen wrote: > In context of XXX Rob was asking what version of WTP we are using. > > That is best found by looking in the build/target-platform/*.target files (they list the exact feature versions we extract) > or the less precise but kinda close list of requirement folders listed in http://download.jboss.org/jbosstools/updates/helios/compositeArtifacts.xml > > But that doesn't actually help when you want to check what version of org.eclipse.jst.common.frameworks > will end up in the distro since this plugin is not listed in any feature as far as Rob and I can see. > > So, beyond just *hoping* the right plugin gets into the build what is the better/best way of checking this (beyond > downloading additional 4-600 MB of builds to see what is in the resulting binary) ? > > /max > http://about.me/maxandersen > > > > > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com _______________________________________________ jbosstools-dev mailing list jbosstools-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jbosstools-dev

Why: because the list of IUs stated and the source repos from which the IUs are fetched comprise a self-contained installation plan, which p2 can resolve and drop onto disk. That's how p2.mirror, p2.director, and p2 install manager work.

What: the contents of the update site. Look in plugins/ and features/ and binaries/ for specifics.

As to "extra information" -- the target file lists IUs and repos. The target site contains IUs and is itself a repo. Same information, without the remote reference(s).

N On 05/31/2011 03:12 PM, Max Rydahl Andersen wrote: > >> Well, you could look in the target platform itself to see what's included: >> >> http://download.jboss.org/jbosstools/updates/target-platform/latest/plugins/ >> >> (yet another reason why an update site is WAY BETTER than a .target file) > > No, the updatesite gives no extra information - and especially with updatesites > disappearing/being reaaranged multiple times more than a few times i'm still > using .target as the only true messenger. > > It does not say *why* and *what* is actually ending up in the distribution. > > /max > >> >> Nick >> >> On 05/31/2011 04:25 AM, Max Rydahl Andersen wrote: >>> In context of XXX Rob was asking what version of WTP we are using. >>> >>> That is best found by looking in the build/target-platform/*.target files (they list the exact feature versions we extract) >>> or the less precise but kinda close list of requirement folders listed in http://download.jboss.org/jbosstools/updates/helios/compositeArtifacts.xml >>> >>> But that doesn't actually help when you want to check what version of org.eclipse.jst.common.frameworks >>> will end up in the distro since this plugin is not listed in any feature as far as Rob and I can see. >>> >>> So, beyond just *hoping* the right plugin gets into the build what is the better/best way of checking this (beyond >>> downloading additional 4-600 MB of builds to see what is in the resulting binary) ? >>> >>> /max >>> http://about.me/maxandersen >>> >>> >>> >>> >>> _______________________________________________ >>> jbosstools-dev mailing list >>> jbosstools-dev(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev >> >> -- >> Nick Boldt :: JBoss by Red Hat >> Productization Lead :: JBoss Tools& Dev Studio >> http://nick.divbyzero.com >> _______________________________________________ >> jbosstools-dev mailing list >> jbosstools-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jbosstools-dev > > /max > http://about.me/maxandersen > > > -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com