You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Carlos Sanchez (JIRA)" <ji...@codehaus.org> on 2006/05/26 23:57:40 UTC

[jira] Moved: (MEV-397) xfire 1.1 pom isn't sycn'd to repo from codehaus

     [ http://jira.codehaus.org/browse/MEV-397?page=all ]

Carlos Sanchez moved MAVENUPLOAD-919 to MEV-397:
------------------------------------------------

           Group ID: 1.1
         Bundle URL:   (was: http://dist.codehaus.org/org.codehaus.xfire/poms/xfire-parent-1.1.pom)
        Project URL:   (was: http://xfire.codheuas.org)
        Artifact ID: xfire
            Version: xfire
    Contributor URL:   (was: http://xfire.codehaus.org/Team)
           Workflow: jira  (was: Maven New)
                Key: MEV-397  (was: MAVENUPLOAD-919)
            Project: Maven Evangelism  (was: maven-upload-requests)

> xfire 1.1 pom isn't sycn'd to repo from codehaus
> ------------------------------------------------
>
>          Key: MEV-397
>          URL: http://jira.codehaus.org/browse/MEV-397
>      Project: Maven Evangelism
>         Type: Bug

>     Reporter: Dan Diephouse
>     Assignee: Carlos Sanchez

>
>
> The xfire-parent pom wasn't sync'd from the codehaus repository to ibiblio, causing extreme confusion for users. I've attached it here. There is no jar file.

-- 
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