You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@archiva.apache.org by "Eric Barboni (JIRA)" <ji...@codehaus.org> on 2011/12/20 14:28:03 UTC

[jira] (MRM-1567) Artifact data incomplete

Eric Barboni created MRM-1567:
---------------------------------

             Summary: Artifact data incomplete
                 Key: MRM-1567
                 URL: https://jira.codehaus.org/browse/MRM-1567
             Project: Archiva
          Issue Type: Bug
    Affects Versions: 1.4-M1
         Environment: fedora fc16, maven 3.0.3
            Reporter: Eric Barboni


Hi folks,

I have a strange error (using the 1.4-M1 or 1.4-M2 ) when browsing an artifact using a parent with snapshot version.

Artifact metadata is incomplete: Error in resolving artifact's parent POM file.
/complex/path/parent-1.1-SNAPSHOT.pom (No such file or directory)

This folder exists but contains only timestamped pom and the metadata. The metadata show a valid build number.

Is it fine to have snapshot parent ? should I use a non-snapshot one?

I try to post first to users archiva mailing list before registration (sorry).

Best regards
Eric


--
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-1567) Artifact data incomplete

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

Olivier Lamy closed MRM-1567.
-----------------------------

    Resolution: Fixed

fixed r1299489
                
> Artifact data incomplete
> ------------------------
>
>                 Key: MRM-1567
>                 URL: https://jira.codehaus.org/browse/MRM-1567
>             Project: Archiva
>          Issue Type: Bug
>    Affects Versions: 1.4-M1
>         Environment: fedora fc16, maven 3.0.3
>            Reporter: Eric Barboni
>            Assignee: Olivier Lamy
>             Fix For: 1.4-M3
>
>
> Hi folks,
> I have a strange error (using the 1.4-M1 or 1.4-M2 ) when browsing an artifact using a parent with snapshot version.
> Artifact metadata is incomplete: Error in resolving artifact's parent POM file.
> /complex/path/parent-1.1-SNAPSHOT.pom (No such file or directory)
> This folder exists but contains only timestamped pom and the metadata. The metadata show a valid build number.
> Is it fine to have snapshot parent ? should I use a non-snapshot one?
> I try to post first to users archiva mailing list before registration (sorry).
> Best regards
> Eric

--
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-1567) Artifact data incomplete

Posted by "Eric Barboni (JIRA)" <ji...@codehaus.org>.
    [ https://jira.codehaus.org/browse/MRM-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=286491#comment-286491 ] 

Eric Barboni commented on MRM-1567:
-----------------------------------

If it may help:

Configuration 
4 managed repository
  external mirror of snapshot artifact
  external mirror of normal artifact
  internal snapshot artifact (ics_snapshot)
  internal normal artifact 

when browsing such a artifact stored on a managed repository call ics_snapshot

I have warning for 3 repository saying  org.apache.archiva.metadata.repository.storag.maven2.Maven2RepositoryStorage Invalid metadata name of the file

but no log on the ics_snapshot repository. 

I don't know if the process pass by this repository with no log or if it avoid processing the current.

That is the only log I have seen.

Regards










                
> Artifact data incomplete
> ------------------------
>
>                 Key: MRM-1567
>                 URL: https://jira.codehaus.org/browse/MRM-1567
>             Project: Archiva
>          Issue Type: Bug
>    Affects Versions: 1.4-M1
>         Environment: fedora fc16, maven 3.0.3
>            Reporter: Eric Barboni
>
> Hi folks,
> I have a strange error (using the 1.4-M1 or 1.4-M2 ) when browsing an artifact using a parent with snapshot version.
> Artifact metadata is incomplete: Error in resolving artifact's parent POM file.
> /complex/path/parent-1.1-SNAPSHOT.pom (No such file or directory)
> This folder exists but contains only timestamped pom and the metadata. The metadata show a valid build number.
> Is it fine to have snapshot parent ? should I use a non-snapshot one?
> I try to post first to users archiva mailing list before registration (sorry).
> Best regards
> Eric

--
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-1567) Artifact data incomplete

Posted by "apache maillist (JIRA)" <ji...@codehaus.org>.
    [ https://jira.codehaus.org/browse/MRM-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=287195#comment-287195 ] 

apache maillist commented on MRM-1567:
--------------------------------------

Hi,

I am experiencing the opposite:
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)
                
> Artifact data incomplete
> ------------------------
>
>                 Key: MRM-1567
>                 URL: https://jira.codehaus.org/browse/MRM-1567
>             Project: Archiva
>          Issue Type: Bug
>    Affects Versions: 1.4-M1
>         Environment: fedora fc16, maven 3.0.3
>            Reporter: Eric Barboni
>
> Hi folks,
> I have a strange error (using the 1.4-M1 or 1.4-M2 ) when browsing an artifact using a parent with snapshot version.
> Artifact metadata is incomplete: Error in resolving artifact's parent POM file.
> /complex/path/parent-1.1-SNAPSHOT.pom (No such file or directory)
> This folder exists but contains only timestamped pom and the metadata. The metadata show a valid build number.
> Is it fine to have snapshot parent ? should I use a non-snapshot one?
> I try to post first to users archiva mailing list before registration (sorry).
> Best regards
> Eric

--
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-1567) Artifact data incomplete

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

Olivier Lamy reassigned MRM-1567:
---------------------------------

    Assignee: Olivier Lamy
    
> Artifact data incomplete
> ------------------------
>
>                 Key: MRM-1567
>                 URL: https://jira.codehaus.org/browse/MRM-1567
>             Project: Archiva
>          Issue Type: Bug
>    Affects Versions: 1.4-M1
>         Environment: fedora fc16, maven 3.0.3
>            Reporter: Eric Barboni
>            Assignee: Olivier Lamy
>             Fix For: 1.4-M3
>
>
> Hi folks,
> I have a strange error (using the 1.4-M1 or 1.4-M2 ) when browsing an artifact using a parent with snapshot version.
> Artifact metadata is incomplete: Error in resolving artifact's parent POM file.
> /complex/path/parent-1.1-SNAPSHOT.pom (No such file or directory)
> This folder exists but contains only timestamped pom and the metadata. The metadata show a valid build number.
> Is it fine to have snapshot parent ? should I use a non-snapshot one?
> I try to post first to users archiva mailing list before registration (sorry).
> Best regards
> Eric

--
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-1567) Artifact data incomplete

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

Olivier Lamy updated MRM-1567:
------------------------------

    Fix Version/s: 1.4-M3
    
> Artifact data incomplete
> ------------------------
>
>                 Key: MRM-1567
>                 URL: https://jira.codehaus.org/browse/MRM-1567
>             Project: Archiva
>          Issue Type: Bug
>    Affects Versions: 1.4-M1
>         Environment: fedora fc16, maven 3.0.3
>            Reporter: Eric Barboni
>             Fix For: 1.4-M3
>
>
> Hi folks,
> I have a strange error (using the 1.4-M1 or 1.4-M2 ) when browsing an artifact using a parent with snapshot version.
> Artifact metadata is incomplete: Error in resolving artifact's parent POM file.
> /complex/path/parent-1.1-SNAPSHOT.pom (No such file or directory)
> This folder exists but contains only timestamped pom and the metadata. The metadata show a valid build number.
> Is it fine to have snapshot parent ? should I use a non-snapshot one?
> I try to post first to users archiva mailing list before registration (sorry).
> Best regards
> Eric

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