<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 09/13/2012 11:26 PM, Denis Golovin
wrote:<br>
</div>
<blockquote cite="mid:50524F83.7050406@exadel.com" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<div class="moz-cite-prefix">For me as a developer .target file is
the window to update sites. This window lets in only those
versions of bundles/feature we can use in development. For JBT
it is features/bundles released for Juno 4.2.0 because I really
would like to avoid issues like <a moz-do-not-send="true"
href="https://issues.jboss.org/browse/JBIDE-12248">https://issues.jboss.org/browse/JBIDE-12248</a>
(JBoss Tools (Indigo) Installation from Eclipse Marketplace
fails for Eclipse Indigo 3.7.0 and 3.7.1). All these means
.target file for JBT 4.0.x should not be changed much. The only
reason to change it is to add some new dependency(ies) to it and
those dependencies should have versions released for 4.2.0 for
the same reason explained above. <br>
<br>
Could someone explain what are these unified/local/multiple
targets below used for? It looks like they point out to latest
version of Juno, which would not let to use them in development
process.<br>
</div>
</blockquote>
Hi Denis,<br>
<br>
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.<br>
I agree with you that the less often .target change for JBT, the
less often we may have issues.<br>
However, it's not the same for JBDS, for which we want the
latest/greatest/stablest version of Eclipse.<br>
<br>
You note probably highlight the need for 2 target-platforms: the
"minimal compatibiliy" for JBT, and the "Best and greatest" for
JBDS.<br>
<br>
About the file we have, I sent some mails a few month ago on this
topic, I'll try to sum it up:<br>
* 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)<br>
* 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:
<a class="moz-txt-link-freetext" href="https://issues.jboss.org/browse/JBIDE-12608">https://issues.jboss.org/browse/JBIDE-12608</a><br>
* unified.target: resolves against the aggregated target site. It's
the one we recommand for "sporadic" local builds.<br>
<br>
HTH<br>
<div class="moz-signature">-- <br>
Mickael Istria<br>
Eclipse developer at <a href="http://www.jboss.org/tools">JBoss,
by Red Hat</a><br>
<a href="http://mickaelistria.wordpress.com">My blog</a> - <a
href="http://twitter.com/mickaelistria">My Tweets</a></div>
</body>
</html>