You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@archiva.apache.org by "apache maillist (JIRA)" <ji...@codehaus.org> on 2012/01/05 19:10:02 UTC

[jira] (MRM-1568) Artifact metadata is incomplete, opposite case to MRM-1567

apache maillist created MRM-1568:
------------------------------------

             Summary: Artifact metadata is incomplete, opposite case to MRM-1567
                 Key: MRM-1568
                 URL: https://jira.codehaus.org/browse/MRM-1568
             Project: Archiva
          Issue Type: Bug
          Components: Metadata Repository
    Affects Versions: 1.4-M2
         Environment: linux
            Reporter: apache maillist


I am experiencing the opposite situation compare to MRM-1567:

2 repos:
release_repo
sansphot_repo

while browsing the SNAPSHOT version of the artifact that is uploaded to the sanpshot_repo where its parent pom is a release version that located at the release_repo

I got the following error on the GUI

Artifact metadata is incomplete: Error in resolving artifact's parent POM file. /apps/maven2/snapshot_repo/org/kp/wpp/utils/parentpom/2.5.3/parentpom-2.5.3.pom (No such file or directory)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] (MRM-1568) Artifact metadata is incomplete, opposite case to MRM-1567

Posted by "Olivier Lamy (JIRA)" <ji...@codehaus.org>.
     [ https://jira.codehaus.org/browse/MRM-1568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Olivier Lamy updated MRM-1568:
------------------------------

    Fix Version/s: 1.4-M3
    
> Artifact metadata is incomplete, opposite case to MRM-1567
> ----------------------------------------------------------
>
>                 Key: MRM-1568
>                 URL: https://jira.codehaus.org/browse/MRM-1568
>             Project: Archiva
>          Issue Type: Bug
>          Components: Metadata Repository
>    Affects Versions: 1.4-M2
>         Environment: linux
>            Reporter: apache maillist
>             Fix For: 1.4-M3
>
>
> I am experiencing the opposite situation compare to MRM-1567:
> 2 repos:
> release_repo
> sansphot_repo
> while browsing the SNAPSHOT version of the artifact that is uploaded to the sanpshot_repo where its parent pom is a release version that located at the release_repo
> I got the following error on the GUI
> Artifact metadata is incomplete: Error in resolving artifact's parent POM file. /apps/maven2/snapshot_repo/org/kp/wpp/utils/parentpom/2.5.3/parentpom-2.5.3.pom (No such file or directory)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] (MRM-1568) Artifact metadata is incomplete, opposite case to MRM-1567

Posted by "Olivier Lamy (JIRA)" <ji...@codehaus.org>.
     [ https://jira.codehaus.org/browse/MRM-1568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Olivier Lamy closed MRM-1568.
-----------------------------

    Resolution: Fixed

fixed r1299489
                
> Artifact metadata is incomplete, opposite case to MRM-1567
> ----------------------------------------------------------
>
>                 Key: MRM-1568
>                 URL: https://jira.codehaus.org/browse/MRM-1568
>             Project: Archiva
>          Issue Type: Bug
>          Components: Metadata Repository
>    Affects Versions: 1.4-M2
>         Environment: linux
>            Reporter: apache maillist
>            Assignee: Olivier Lamy
>             Fix For: 1.4-M3
>
>
> I am experiencing the opposite situation compare to MRM-1567:
> 2 repos:
> release_repo
> sansphot_repo
> while browsing the SNAPSHOT version of the artifact that is uploaded to the sanpshot_repo where its parent pom is a release version that located at the release_repo
> I got the following error on the GUI
> Artifact metadata is incomplete: Error in resolving artifact's parent POM file. /apps/maven2/snapshot_repo/org/kp/wpp/utils/parentpom/2.5.3/parentpom-2.5.3.pom (No such file or directory)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] (MRM-1568) Artifact metadata is incomplete, opposite case to MRM-1567

Posted by "Olivier Lamy (JIRA)" <ji...@codehaus.org>.
     [ https://jira.codehaus.org/browse/MRM-1568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Olivier Lamy updated MRM-1568:
------------------------------

    Assignee: Olivier Lamy
    
> Artifact metadata is incomplete, opposite case to MRM-1567
> ----------------------------------------------------------
>
>                 Key: MRM-1568
>                 URL: https://jira.codehaus.org/browse/MRM-1568
>             Project: Archiva
>          Issue Type: Bug
>          Components: Metadata Repository
>    Affects Versions: 1.4-M2
>         Environment: linux
>            Reporter: apache maillist
>            Assignee: Olivier Lamy
>             Fix For: 1.4-M3
>
>
> I am experiencing the opposite situation compare to MRM-1567:
> 2 repos:
> release_repo
> sansphot_repo
> while browsing the SNAPSHOT version of the artifact that is uploaded to the sanpshot_repo where its parent pom is a release version that located at the release_repo
> I got the following error on the GUI
> Artifact metadata is incomplete: Error in resolving artifact's parent POM file. /apps/maven2/snapshot_repo/org/kp/wpp/utils/parentpom/2.5.3/parentpom-2.5.3.pom (No such file or directory)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira