Re: [epp-dev] Neon M7 packages

[Markus Knauer <mknauer@xxxxxxxxxxxxxxxxx>]

Two thoughts...

Based on the fact that there are NPEs I doubt that this feature is really optional. Without a deep dive into the issue I would expect it to be included (as a non-option, required) feature in one of the web tools features. Or the code needs to deal with the NPE when it is not available. In other words: My guess without deeper knowledge is that there is something else "wrong", and that the issue should be fixed somewhere else.

A respin after the release is not really possible. Given the short timespan between build time (sometime on Thursday), the time that is needed by the mirror servers, and the release on Friday is extremely short. Usually a -1 for a package means that it is not part of this milestone. All I could offer is that we copy the updated _javascript_ package archives (.zip, .tar.gz) into the download location.

Regards,

Markus

On 9 May 2016 at 13:46, Mickael Istria <mistria@xxxxxxxxxx> wrote:

On 05/06/2016 06:25 PM, Mickael Istria wrote:

On 05/06/2016 04:52 PM, Chuck Bridgham wrote:

I also would like to vote -1 for the _javascript_ EPP, as it was missing the V8 chromium debugger feature, and results in an NPE, when launching a JS debug session.
I just pushed this change:  https://git.eclipse.org/r/#/c/70999/   I vote for respin.

I agre with Chuck. -1 for JS EPP.
The missing feature per se isn't critical for M7 IMHO, but the NPE isn't something we should deliver.

How should we proceed to have a respin? When would it be available for testing?

--
Mickael Istria
Eclipse developer at JBoss, by Red Hat
My blog - My Tweets

_______________________________________________
epp-dev mailing list
epp-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/epp-dev