Re: [wtp-releng] [Hudson] Build failed in Hudson: WTP-R3_7_x_Maintenance

["Chuck Bridgham" <cbridgha@xxxxxxxxxx>]

I also wonder if this would be avoided
if the 3.7.1 build was pulling from a separate maintenance branch? 


Thanks - Chuck

Senior Architect, WebSphere Developer
Tools, Eclipse WTP PMC Lead
IBM Software Lab - Research Triangle Park, NC



From:      
 Mickael Istria <mistria@xxxxxxxxxx>
To:      
 wtp-releng@xxxxxxxxxxx
Date:      
 09/08/2015 09:18 AM
Subject:    
   Re: [wtp-releng]
[Hudson] Build failed in Hudson: WTP-R3_7_x_Maintenance #87
Sent by:    
   wtp-releng-bounces@xxxxxxxxxxx

---

The upstream experimental Easymport framework had some
API changes. The WTP connector was affected. I proposed a fix on Gerrit
to avoid that.
Note that it affects a plugin that is not shipped as part of main JSDT
feature, nor on the WTP site, nor on SimRel, which has no consumer at Eclipse.org,
no API... So this issue doesn't affect the WTP binary delivery.
In order to prevent from such issues in the future, I plan to make those
"experimental" and weak components part of a profile so they
would cascade to WTP.

-- 
Mickael Istria
Eclipse developer at JBoss,
by Red Hat
My
blog - My
Tweets_______________________________________________
wtp-releng mailing list
wtp-releng@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/wtp-releng