]
Alexey Kazakov updated JBIDE-20986:
-----------------------------------
Fix Version/s: 4.3.x
4.4.x
(was: 4.3.1.Beta1)
Moved to 4.3.x/4.4.x as a not high priority for 4.3.1.Beta1 release
JBoss EAP 7 Maven repository is not recognized
----------------------------------------------
Key: JBIDE-20986
URL:
https://issues.jboss.org/browse/JBIDE-20986
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: maven
Affects Versions: 4.3.0.Final
Reporter: Fred Bricon
Assignee: Fred Bricon
Fix For: 4.3.x, 4.4.x
- Unzip Maven repo from
http://download.devel.redhat.com/devel/candidates/JBEAP/JBEAP-7.0.0.DR11/
- Preferences > JBoss Tools > JBoss Maven Integration > Configure Maven
Repositories... > Add Repository > Recognize JBoss Maven Enterprise Repositories...
(point at unzipped maven DR11 repo dir)
- ASSERT the Maven repo should be recognized as an EAP repo
- FAILURE a "No new repository found" message is displayed
This is caused by the repository identifier looking for a com/sun/faces/jsf-impl"
folder containing a *-redhat-* jar, whereas the EAP 7 repo now contains *-jbossorg-*.jar
files.
The check can be updated in the code, but the best solution is to leverage the
.maven-repository marker file, that should be added at the root of the repository. See
JBIDE-18323.