[jbosstools-issues] [JBoss JIRA] (TOOLSDOC-363) NeedInfo: When are the redhat and jboss maven repos necessary?

[Fred Bricon (JIRA)]

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

Fred Bricon resolved TOOLSDOC-363.
----------------------------------

    Resolution: Done


Please re-open if you need more info
                
> NeedInfo: When are the redhat and jboss maven repos necessary?
> --------------------------------------------------------------
>
>                 Key: TOOLSDOC-363
>                 URL: https://issues.jboss.org/browse/TOOLSDOC-363
>             Project: Documentation for JBoss Tools and Developer Studio
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Getting Started Guide
>    Affects Versions: 4.1.0
>            Reporter: Michelle Murray
>            Assignee: Fred Bricon
>             Fix For: 4.1.0
>
>
> 1. Under Window>Preferences>JBoss Tools>JBoss Maven Integration, click 'Configure Maven Repositories'.
> 2. Click 'Add Repository'.
> 3. In the 'Profile ID' field, click the drop down list. Two of the options are:
> * jboss-public-repository
> * redhat-techpreview-all-repository
> What is each repo? When would you use each? Is the readhat one instead of having to download individual maven repos for EAP and WFK?
> When you create the JavaEE Web Project and select EAP as target runtime, then you need an EAP specific (or redhat-techpreview) maven repo specified in settings.xml. So I assumed that when you create the JavaEE Web Project and select JBoss AS as target runtime, then you need a jboss specific maven repo specified in settings.xml but it seems that you don't need any maven repos specified. Is that right?

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