[jbosstools-issues] [JBoss JIRA] (JBIDE-21567) JBoss EAP 7 Maven repository is not recognized

[Josef Kopriva (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-21567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Josef Kopriva closed JBIDE-21567.
---------------------------------


Retested with repository: http://download.eng.brq.redhat.com/released/JBEAP-7/7.0.0-Beta/jboss-eap-7.0.0.Beta-maven-repository.zip 
(the mentioned repository has not accessible)
Extracted zip was correctly recognized as a JBoss EAP Maven Repository.
Closing issue.

Tested in version: 
Version: 10.0.0.Alpha1
Build id: Alpha1-v20160429-1112-B5258
Build date: 20160429-1112

> JBoss EAP 7 Maven repository is not recognized
> ----------------------------------------------
>
>                 Key: JBIDE-21567
>                 URL: https://issues.jboss.org/browse/JBIDE-21567
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: maven
>    Affects Versions: 4.3.0.Final
>            Reporter: Fred Bricon
>            Assignee: Fred Bricon
>             Fix For: 4.4.0.Alpha1
>
>
> - 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.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)