[
https://issues.jboss.org/browse/JBIDE-11684?page=com.atlassian.jira.plugi...
]
Snjezana Peco commented on JBIDE-11684:
---------------------------------------
The problem was happening because the Project Examples was checking for existence of the
org.jboss.spec:jboss-javaee-web-6.0:pom:3.0.0.Beta1-redhat-1 artifact. See JBIDE-11242
The 3.0.0.Beta1-redhat-1 version isn't contained by EAP6 ER6 repository, but
3.0.0.Final-redhat-1.
Now the Project Examples checks if there is the org.jboss.spec:jboss-javaee-web-6.0
artifact with a version containing "redhat".
This fixes the issue with recognizing the JBoss Maven Enterprise repository.
However, the archetype still contains the 3.0.0.Beta1-redhat-1 version that doesn't
exist in the EAP6 ER6 repository. I think the version of this artifact should be defined
as an archetype preference.
Committed to the trunk. Attached is a patch.
Max,
Assigning this jira to you because I can't change archetypes.
EAP 5.0. ER6 Maven artefacts are not compatible with JBT Java EE Web
Project
----------------------------------------------------------------------------
Key: JBIDE-11684
URL:
https://issues.jboss.org/browse/JBIDE-11684
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: central, project-examples
Affects Versions: 3.3.0.Beta3
Environment: JBT 3.3.0.beta3-trunk, L64, EAP 6.0.ER6 (as and mvn repo)
Reporter: Jiri Peterka
Assignee: Snjezana Peco
Priority: Critical
Fix For: 3.3.0.Beta3
Attachments: ER6-maven-repo.png
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira