<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">It worth to update dependencies to
Kepler version:<br>
1. Hibernate Tools depends on Dali that requires Kepler;<br>
2. JBoss Tools are going to be called on JBoss Tools (Kepler) in
Eclipse marketplace.<br>
<br>
If we let install JBoss Tools on Juno and Kepler, devs can install
for example CDI Tools Feature on Juno and then try to add
Hibernate Tools and installation would fail.<br>
<br>
I would prefer to have installation behavior that matches the name
"JBoss Tools (Kepler)", which means it is installable only on
Kepler and fails for Juno.<br>
<br>
Denis<br>
<br>
On 02/06/2013 10:09 AM, Mickael Istria wrote:<br>
</div>
<blockquote cite="mid:51129C5B.8070103@redhat.com" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<div class="moz-cite-prefix">On 02/06/2013 06:58 PM, Alexey
Kazakov wrote:<br>
</div>
<blockquote cite="mid:511299D9.4000608@exadel.com" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<div class="moz-cite-prefix">On 02/06/2013 01:07 AM, Mickael
Istria wrote:<br>
</div>
<blockquote cite="mid:51121D5C.4030903@redhat.com" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<br>
<blockquote cite="mid:5111669D.7010102@exadel.com" type="cite">
<pre wrap="">Should we change Eclipse (wtp, etc.) dependencies in plugin.xml too even
if we don't use any new API from Kepler?</pre>
</blockquote>
No, you shouldn't do it. MANIFEST.MF must contain the "wider"
compatible version range.<br>
</blockquote>
<br>
The problem is that we don't know if JBT compatible with Juno
until we test it against Juno, do we?<br>
</blockquote>
We'll test only for Kepler. But you can expect it to work or not
with Juno.<br>
Next JBT will only be supported (ie guaranteed to work on Kepler),
but if you think your component still support Juno, you'd better
not change versions in MANIFEST because:<br>
1. Some people may want to install your component on Juno, and
will be happy if it works. If it doesn't work, it's not that bad
because we don't support it.<br>
2. It's more effort and risk for you to change MANIFEST.<br>
3. If we change our mind and decide to support Juno, you won't
have anything to change.<br>
So I recommend you change MANIFEST only when you _need_ it (ie
when you have some breaking API or feature changes in your
dependencies).<br>
<br>
If your stuff can still work on Juno, changing versions in
MANIFEST will make it impossible to use it on Juno. There is no
added-value to it. The target-platforms provide all the safety you
need.<br>
<div class="moz-signature">-- <br>
Mickael Istria<br>
Eclipse developer at <a moz-do-not-send="true"
href="http://www.jboss.org/tools">JBoss, by Red Hat</a><br>
<a moz-do-not-send="true"
href="http://mickaelistria.wordpress.com">My blog</a> - <a
moz-do-not-send="true" href="http://twitter.com/mickaelistria">My
Tweets</a></div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
jbosstools-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:jbosstools-dev@lists.jboss.org">jbosstools-dev@lists.jboss.org</a>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/jbosstools-dev">https://lists.jboss.org/mailman/listinfo/jbosstools-dev</a></pre>
</blockquote>
<br>
</body>
</html>