[jbosstools-dev] Content and usage of target platforms (was Re: New mechanism for target=platforms)

On 09/13/2012 11:26 PM, Denis Golovin wrote: Hi Denis, This change we're about to make does not affect the content (plugins and features) of the target-platform. Instead it affects what is the process to publish a new platform. I agree with you that the less often .target change for JBT, the less often we may have issues. However, it's not the same for JBDS, for which we want the latest/greatest/stablest version of Eclipse. You note probably highlight the need for 2 target-platforms: the "minimal compatibiliy" for JBT, and the "Best and greatest" for JBDS. About the file we have, I sent some mails a few month ago on this topic, I'll try to sum it up: * multiple.target: points to the composite target site, good to use inside IDE with PDE since it also contains source (PDE is greedy and also finds sources from the composite) * local.target: if you want to perform lots of local build and save time, just run "mvn install" on local.target, you'll get all the TP repo locally, and you'll be able to consume it in your builds using the -Plocal.target profile. Not that this target is probably going to be replaced by Maven mirrors as soon as Tycho 0.16 is resolved: https://issues.jboss.org/browse/JBIDE-12608 * unified.target: resolves against the aggregated target site. It's the one we recommand for "sporadic" local builds. HTH -- 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>