<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/14/2012 09:19 AM, Max Rydahl
Andersen wrote:<br>
</div>
<blockquote
cite="mid:C2F1A4E7-BA5A-40F8-8843-9E226808A150@redhat.com"
type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">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 class="moz-txt-link-freetext" 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.
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.
</pre>
</blockquote>
<pre wrap="">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.
</pre>
</blockquote>
<pre wrap="">
Both JBT and JBDS want the best and greatest to *run* against, but they both should have the "minimal compatibility" to *compile/build* against.
Only the installer/product build of JBDS should use the "latest/greatest" for its binary build.</pre>
</blockquote>
OK.<br>
<br>
<blockquote
cite="mid:C2F1A4E7-BA5A-40F8-8843-9E226808A150@redhat.com"
type="cite">
<blockquote type="cite">
<pre wrap="">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)
</pre>
</blockquote>
<pre wrap="">
should really get another name than multiple.</pre>
</blockquote>
I'll try to push a rename to "composite" or "development" after all
changes in already planned happened. I'll ping all of you later for
the debate.<br>
<br>
<blockquote
cite="mid:C2F1A4E7-BA5A-40F8-8843-9E226808A150@redhat.com"
type="cite">
<blockquote type="cite">
<pre wrap="">* unified.target: resolves against the aggregated target site. It's the one we recommand for "sporadic" local builds.
</pre>
</blockquote>
<pre wrap="">
"sporadic" ? I thought this was *the* recommended and default one used for builds ?
</pre>
</blockquote>
It's the recommanded way locally, and local builds are sporadic.<br>
It's unfortunately not what we use on Jenkins because of
performances. Using mirrors for Target platform in Tycho 0.16 will
help to fix that: <a class="moz-txt-link-freetext" href="https://issues.jboss.org/browse/JBIDE-12608">https://issues.jboss.org/browse/JBIDE-12608</a> . Then
we'll use unified in Jenkins + mirrors to improve performances.<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>