<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 01/09/2015 09:58 AM, Max Rydahl
Andersen wrote:<br>
</div>
<blockquote
cite="mid:2D4A7FE1-A4A3-4769-A9C5-269D5F004513@redhat.com"
type="cite">On 9 Jan 2015, at 9:40, Mickael Istria wrote:
<br>
<br>
<blockquote type="cite">On 01/08/2015 11:43 PM, Max Rydahl
Andersen wrote:
<br>
<blockquote type="cite">
<blockquote type="cite">and its dependencies (the dependency
chain for jasper got huge on Orbit, and it was simpler to
remove it than to cascade inclusion of all dependencies).
<br>
</blockquote>
is that your comment or some decision on Eclipse.org side ?
<br>
</blockquote>
This is my comment.
<br>
</blockquote>
so i'm a bit puzzled...if apache.jasper is part of eclipse release
train why do we even need to chase it on orbit ?<br>
why is this dependency in here in the first place ?
<br>
if not part of release train there should be a reason..
<br>
</blockquote>
Actually, it's not part of the Eclipse release train. Nothing on the
release train depends on it.<br>
I don't know why it used to be in our target definition, and I
imagine that it might have been there for some reason in the past,
and that it has become useless.<br>
<br>
Let's give a few days (until Friday) for developers to raise their
hand if they actually need it, if not, let's remove it; and in case
something is actually failing after that, we'll re-add jasper and
its family, and document on the target files why it needs to be
here.<br>
<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>