[
https://issues.jboss.org/browse/JBIDE-18379?page=com.atlassian.jira.plugi...
]
Fred Bricon commented on JBIDE-18379:
-------------------------------------
There's no hard requirement on specific mavenarchiver build timestamp. Just [0.16.0)
basically.
So yes, users can use the same version, as old as 2y ago, if they really really want it.
Update TP/Installer with m2eclipse-mavenarchiver 0.16.0.201409161210
--------------------------------------------------------------------
Key: JBIDE-18379
URL:
https://issues.jboss.org/browse/JBIDE-18379
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: target-platform
Reporter: Fred Bricon
Assignee: Mickael Istria
Priority: Critical
Fix For: 4.2.0.CR2
Reason: m2eclipse-mavenarchiver 0.16.0.201409161210 fixes JBIDE-17986
License and owner: EPL, Sonatype
Original repository:
http://repo1.maven.org/maven2/.m2e/connectors/m2eclipse-mavenarchiver/0.1...
JBoss Mirrored repository:
http://downloads.jboss.org/jbosstools/updates/requirements/???
Source:
https://github.com/tesla/m2eclipse-mavenarchiver
Affected projects:JBT/JBDS
Required in devstudio: Yes
Type of dependency: central|distribution
List of bundles added/removed: none, just an update
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)