[jbosstools-issues] [JBoss JIRA] (JBIDE-15295) EAP 6.1 maven repo not recognized for use with Java EE Web Project wizard

[Michelle Murray (JIRA)]

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

Michelle Murray updated JBIDE-15295:
------------------------------------

    Description: 
For the Java EE Web Project wizard, the EAP 6.1 maven repo is not recognized as being a JBoss Enterprise Maven repository.

The project states that it can be used with EAP 6 so I would assume this to include EAP 6.0 and 6.1.

Attached are:
* my settings.xml file, with profiles generated by JBDS 'Configure Maven Repositories'
* screenshot of added EAP 6.1 maven repo
* Screenshot of enterprise maven repo warning in Java EE Web Project wizard

  was:
For the Java EE Web Project wizard, the EAP 6.1 maven repo is not recognized as being a JBoss Enterprise Maven repository.

The project states that it can be used with EAP 6 so I would assume this to include EAP 6.0 and 6.1.


    
> EAP 6.1 maven repo not recognized for use with Java EE Web Project wizard
> -------------------------------------------------------------------------
>
>                 Key: JBIDE-15295
>                 URL: https://issues.jboss.org/browse/JBIDE-15295
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: maven, project-examples
>    Affects Versions: 4.1.0.Final
>            Reporter: Michelle Murray
>         Attachments: Maven_EAP61.png, Maven_warning.png, settings.xml
>
>
> For the Java EE Web Project wizard, the EAP 6.1 maven repo is not recognized as being a JBoss Enterprise Maven repository.
> The project states that it can be used with EAP 6 so I would assume this to include EAP 6.0 and 6.1.
> Attached are:
> * my settings.xml file, with profiles generated by JBDS 'Configure Maven Repositories'
> * screenshot of added EAP 6.1 maven repo
> * Screenshot of enterprise maven repo warning in Java EE Web Project wizard

--
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