[jbosstools-issues] [JBoss JIRA] (JBIDE-16651) Remove hard-coded enterprise dependency resolution for upcoming archetypes embedding RedHat techpreview repo

[Fred Bricon (JIRA)]

Fred Bricon created JBIDE-16651:
-----------------------------------

             Summary: Remove hard-coded enterprise dependency resolution for upcoming archetypes embedding RedHat techpreview repo
                 Key: JBIDE-16651
                 URL: https://issues.jboss.org/browse/JBIDE-16651
             Project: Tools (JBoss Tools)
          Issue Type: Task
          Components: maven, project-examples
    Affects Versions: 4.1.1.Final
            Reporter: Fred Bricon
            Assignee: Fred Bricon
             Fix For: 4.1.2.CR1


In JBoss Central, when an Enterprise runtime is selected for any given  Archetype, we check if the Red Hat Enterprise repository is available by trying to resolve a redhat version of org.jboss.spec:jboss-javaee-web-6.0. Then, if some essential dependencies are defined in stacks.yaml, we also try to resolve these. If the dependencies can't be resolved, a warning message appears with a link allowing users to add the RH repo to their Maven settings.xml

Upcoming archetypes will have the Red Hat repository already added to the generated pom.xml, so adding it to settings.xml becomes unnecessary. However, we'd get false positive warning by trying to resolve org.jboss.spec:jboss-javaee-web-6.0 from the settings.xml *before* generating the archetype.

Our goal is to remove the hardcoded check from MavenArtifactHelper and, when necessary, declare org.jboss.spec:jboss-javaee-web-6.0 as an essential dependency in stacks.yaml for *old* archetypes, not declaring the RH repo in the gen'd pom.xml

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira