On 9 Jan 2015, at 9:40, Mickael Istria wrote:
On 01/08/2015 11:43 PM, Max Rydahl Andersen wrote:
>> 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).
> is that your comment or some decision on
Eclipse.org side ?
This is my comment.
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 ?
why is this dependency in here in the first place ?
if not part of release train there should be a reason..
> I wonder though if parts of WTP uses/needs it ?
Target-platform-validation is expected to fail because of a missing
dependency in that case.
However, I can see that org.apache.jasper.glassfish bundle still
remains (it's actually included in JBDS 8).
/max
http://about.me/maxandersen