[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:comment-tabpanel&focusedCommentId=12784218#comment-12784218 ] 

Fred Bricon commented on TOOLSDOC-363:
--------------------------------------

The jboss-public-repository point at the JBoss public repository containing community bits produced by various JBoss projects. Usually, most of the files available in that repository are also synch'ed up to Maven Central, so they're available without needing any particular configuration. However, some projects files are not in Maven Central and are only available in the JBoss repo. In that case, it's necessary to tell Maven where to get these files.

Configuring redhat-techpreview-all-repository is an alternative to downloading and configuring a zipped enterprise repository. That repo contains all the JBoss certified bits used to build against EAP/WFK.

Also look at https://community.jboss.org/wiki/SettingUpTheJBossEnterpriseRepositories for more infos about configuring enterprise repos.

Repos can easily be added in your [pom.xml|http://docs.jboss.org/tools/whatsnew/maven/maven-news-3.3.0.M3.html#itemname5], but it's generally [frowned upon|http://blog.sonatype.com/people/2009/02/why-putting-repositories-in-your-poms-is-a-bad-idea/]

So, if you create a Java EE web project against JBoss AS/WildFly, chances are you won't even need to use jboss-public-repository. Other kind of projects might need it, or depending on the dependencies you need.
If you create the Java EE web project against EAP, a flag is set on the archetype to use maven dependencies only available in the EAP/WFK repos. In that case, you must either have a locally unzipped enterprise repo or use redhat-techpreview-all-repository

Hope it's clear enough :-)

                
> 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