[ http://jira.codehaus.org/browse/MEV-129?page=all ]
     
Edwin Punzalan closed MEV-129:
------------------------------

    Resolution: Fixed

Fixed.

NOTE: May take up to 4 hours before the fix reaches central repo.

> eXo POM's have incorrect groupId
> --------------------------------
>
>          Key: MEV-129
>          URL: http://jira.codehaus.org/browse/MEV-129
>      Project: Maven Evangelism
>         Type: Bug
>   Components: Invalid POM
>     Reporter: Stephen Duncan Jr
>     Assignee: Edwin Punzalan

>
>
> Example: 
> http://www.ibiblio.org/maven2/exo/exoplatform.portal.api/1.0/exoplatform.portal.api-1.0.pom
> I assume this happened during automatic conversion from Maven1.  The 
> dependency groupId has been correctly changed to "exo" to match the location 
> in the repository, but the groupId specified in each POM incorrectly uses "." 
> characters, and will not work with Maven 2.  They should all be changed to 
> exo.

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


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to