Component leads, please tag your repositories!
(Note: if you changed nothing in this milestone, you don't have to tag.
Looking at you, Portlet & Freemarker.)
$ git fetch jbosstools jbosstools-4.2.x #assuming remote is called
jbosstools, also often called origin
$ git tag jbosstools-4.2.3.CR1 FETCH_HEAD
$ git push jbosstools jbosstools-4.2.3.CR1
Then, once tagged, *IF YOU CONTRIBUTED FIXES IN Beta1 or CR1 ONLY*
please bump your root pom to use the latest parent pom,
I will send out the usual Task JIRA nags, too.
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
We have an issue in the latest Forge 2.15.1.Final (upgraded in JBDS
8.1.0.CR1) - https://issues.jboss.org/browse/JBIDE-19468
It prevents creating a forge addon. The workaround described in the JIRA.
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 *IF* we can do a respin for the forge
component (with upgraded forge) *with no big cost* maybe it's worth doing.
So about a year ago I bumped facet support for wildfly and eap6.x to
include the jee7 facets. See:
Unfortunately there's no JIRA id attached to the commit.
Does anyone remember specifically asking me to enable some jee7 facets
on eap6.1+ runtime? Or was this purely a mistake on my part? As I
recall, there was a minor discussion where it was determined eap6.x was
"partially compliant" and it was better to leave the facets enabled than
not. But I can't find any written documentation of this at all, which is
a failure on my part to not post summaries to any jiras.
- Rob Stryker