[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-7297) Problem with mavenized Seam project and Seam bundled with EAP

[Max Andersen (JIRA)]

    [ https://jira.jboss.org/browse/JBIDE-7297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12564751#comment-12564751 ] 

Max Andersen commented on JBIDE-7297:
-------------------------------------

There is no repository we can use for EAP 5 - brew exists but is not consistent thus shouldn't be exposed/used.

pushing to 3.3.x

> Problem with mavenized Seam project and Seam bundled with EAP
> -------------------------------------------------------------
>
>                 Key: JBIDE-7297
>                 URL: https://jira.jboss.org/browse/JBIDE-7297
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: maven
>    Affects Versions: 3.2.0.M2
>            Reporter: Snjezana Peco
>            Assignee: Max Andersen
>             Fix For: 3.3.x
>
>
> A mavenized Seam project uses the <SEAM_HOME>build/root.pom.xml file to resolve versions of some maven artifacts Seam requires.
> Seam included in EAP contains some artifacts that don't exist on https://repository.jboss.org/nexus/content/groups/public and http://repository.jboss.org/maven2.
> For instance, 3.3.2.GA_CP03 is the version of hibernate-core, 3.3.1.SP2 is the version of richfaces, beta3.SP13 is the version of jboss-embedded-api  ... and aren't on any of these two repositories. They exist on the http://repository.jboss.org/maven2-brew repository.
> Max,
> Should we add this repository to the pom.xml of a Seam parent project?

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira