[jbosstools-dev] Question of the day: How to find out which version of a plugin we have in target platform

[Max Rydahl Andersen]

> 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.

Interesting - but how is that reached/fetched when we just declare a target with features.

Know of a way to get P2 to explain why it installs a certain thing based on a .target? 

/max

> 
> 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 at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>  
> 

/max
http://about.me/maxandersen