[
https://issues.jboss.org/browse/JBDS-3075?page=com.atlassian.jira.plugin....
]
Nick Boldt commented on JBDS-3075:
----------------------------------
I believe this was already fixed in the 4.40.0.Beta4-SNAPSHOT target platform:
https://github.com/jbosstools/jbosstools-target-platforms/commit/25e90ae0...
Because this is included in JBDS OOTB via the com.jboss.devstudio.core.feature, it needs
to remain in the JBDS TP.
Or, we could change the build to pull the feature/plugin from the Central TP instead.
[~mickael_istria], remind me why you think using Central TP to build JBDS is a bad idea?
(ref:
https://github.com/jbosstools/jbosstools-target-platforms/pull/54 which copied
TestNG into the JBDS TP, when previously it was only in Central, not in BOTH places)
Old/redundant m2e-apt in JBDS TP 4.40.0.Beta3
---------------------------------------------
Key: JBDS-3075
URL:
https://issues.jboss.org/browse/JBDS-3075
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: 3rd-party-dependencies
Affects Versions: 8.0.0.Beta2
Reporter: Martin Malina
Assignee: Nick Boldt
Fix For: 8.0.0.Beta3
I noticed there is an old version of m2e-apt in JBDS TP 4.40.0.Beta3 which will be
released with JBDS 8.0.0.Beta2.
http://download.jboss.org/jbosstools/targetplatforms/jbdevstudiotarget/4....
In JBoss Tools TP, we have the newer version:
http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.4...
This update was done in JBIDE-17306 .
The thing is that for JBDS, the updated feature is already included in JBDS installer /
update site. So it seems the one in the JBDS TP is a left over ready to be removed. Or if
it's needed, it should be updated to the newer version (or rather build).
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)