<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>Would we want to pull in the fix and try to release CR1 at be end of the planned QE test cycle? We've already missed the 18th. </div><div><br></div><div>--Len<br><br><div><br></div><div>(Sent from my iPhone)</div><div><br></div><div><br></div></div><div><br>On Mar 18, 2015, at 1:52 PM, Alexey Kazakov <<a href="mailto:akazakov@exadel.com">akazakov@exadel.com</a>> wrote:<br><br></div><blockquote type="cite"><div>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
Hi,<br>
<br>
We have an issue in the latest Forge 2.15.1.Final (upgraded in JBDS
8.1.0.CR1) - <a class="moz-txt-link-freetext" href="https://issues.jboss.org/browse/JBIDE-19468">https://issues.jboss.org/browse/JBIDE-19468</a><br>
It prevents creating a forge addon. The workaround described in the
JIRA.<br>
The issue itself doesn't look like a blocker for JBDS 8.1 to me.
However, George Gastaldi said that they are going to release a fixed
Forge 2.15.2 today or tomorrow and <b>IF</b> we can do a respin for
the forge component (with upgraded forge) <b>with no big cost</b>
maybe it's worth doing.<br>
<br>
WDYT?<br>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>jbosstools-dev mailing list</span><br><span><a href="mailto:jbosstools-dev@lists.jboss.org">jbosstools-dev@lists.jboss.org</a></span><br><span><a href="https://lists.jboss.org/mailman/listinfo/jbosstools-dev">https://lists.jboss.org/mailman/listinfo/jbosstools-dev</a></span></div></blockquote></body></html>