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

Sakari Isoniemi (JIRA) jira-events at lists.jboss.org
Tue Jun 8 07:07:38 EDT 2010


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

Sakari Isoniemi commented on SEAM-10:
-------------------------------------


Change to setting.xml caused that Maven 2 stuff ws imported to ../M3
Is this wrong or should the import happen now  from .../maven3/... repository ?

The required directory ./org/jboss/spec/... didn't come by running
the ../build/trunk/parent/pom.xml

Then in next step the run ../dist/trunk/pom.xml resulted (of course) to same error

1 required artifact is missing.

for artifact:
  org.jboss.spec:jboss-javaee-6.0:pom:1.0.0.Beta4

> 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