Now that JBoss Tools 3.2.1 / JBDS 4.1 is just about wrapped up, it's time to start thinking about what critical fixes need to make their way into the next release - JBoss Tools 3.2.2 / JBDS 4.1.1.
This includes any critical fixes, known incompatibilities with new versions of component SOA-P runtimes (ESB, Drools, Teiid, etc.), and any other critical bits.
Keep in mind this should be bug fixes and not new features. But if you know of anything that hasn't yet had a JIRA created, please create it and assign it to the appropriate fix version (3.2.2 in JBIDE or 4.1.1 in JBDS JIRAs).
To get you started, here are a few JIRA queries...
Here's a list of 3.2.x bugs:
Here's a list of JBDS issues that don't have fix versions:
Here's a list of JBoss Tools issues that don't have fix versions:
Thanks in advance for your help with this triage process!
Brian Fitzpatrick (aka "Fitz")
Senior Software Engineer, SOA-P
JBoss by Red Hat
I've added m2e-wtp 0.13.1 to the Eclipse Marketplace yesterday (or today
depending on where you are) :
Seems like it's been installed a few times already, however, what
concerns me is more than 50% of installs fail.
The 2 major reasons are :
1 - p2 doesn't find m2e 1.0
2 - p2 cannot update older versions of m2e 0.12 to 1.0, due to the
namespace change, thus prevents the m2e-wtp installation.
Nothing we can do about #2 but, I think #1 could be solved by adding the
m2e update site url to m2e-wtp's composite update site.
Is there ANY reason we might not want to do that?