[seam-issues] [JBoss JIRA] Commented: (SEAM-10) Wrong artifact id for jboss-javaee-6.0

Adam Warski (JIRA) jira-events at lists.jboss.org
Tue Jun 8 02:40:38 EDT 2010


    [ https://jira.jboss.org/browse/SEAM-10?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12534368#action_12534368 ] 

Adam Warski commented on SEAM-10:
---------------------------------

Ah, I didn't know about Maven3.

The group and artifact ids are indeed correct now (someone must have fixed them), but the build still fails as maven only looks in the central and jboss snapshots repositories (as it's the only repo specified by weld parent pom), disregarding any repositories configured globally or for my projecct. But maybe that's a Maven2 vs Maven3 thing.

I'm trying to build a project which uses seam3-faces.

> Wrong artifact id for jboss-javaee-6.0
> --------------------------------------
>
>                 Key: SEAM-10
>                 URL: https://jira.jboss.org/browse/SEAM-10
>             Project: Seam 3
>          Issue Type: Bug
>          Components: Build Infrastructure
>            Reporter: Adam Warski
>            Assignee: Pete Muir
>
> In seam-bom-3.0.0-SNAPSHOT.pom there's a dependency on org.jboss.spec:jboss-javaee-6.0:1.0.0.Beta4. The group id should be jboss-javaee-6.0 (https://repository.jboss.org/nexus/content/groups/public/org/jboss/spec/jboss-javaee-6.0/)
> This prevents projects dependent on seam3 module snapshots to build.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the seam-issues mailing list