[
https://issues.jboss.org/browse/JBDS-3075?page=com.atlassian.jira.plugin....
]
Mickael Istria commented on JBDS-3075:
--------------------------------------
{quote}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){quote}
Because from development/build/installation POV, Central comes downstream of JBDS (so
having JBDS build depending on Central is somehow a circular dependency without all the
pain to guarantee and maintain happy behaviour), and JBDS shoudl be able to build without
Central (that's the purpose of its TP to contain everything necessary for
dev/build/install).
Maybe we could remove TestNG from JBDS Central TP as well if we are sure that JBDS Central
site always reference a site containing TestNG.
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: Task
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)