You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Jason van Zyl (JIRA)" <ji...@codehaus.org> on 2007/04/25 19:25:26 UTC

[jira] Created: (MNG-2963) Do not update metadata unless the artifact actually made it down

Do not update metadata unless the artifact actually made it down
----------------------------------------------------------------

                 Key: MNG-2963
                 URL: http://jira.codehaus.org/browse/MNG-2963
             Project: Maven 2
          Issue Type: Bug
          Components: Artifacts and Repositories
    Affects Versions: 2.0.x
            Reporter: Jason van Zyl


We can also have a secondard check to see that if a metadata file contains no valid versions to nuke it and try to download a valid one. This will correct anything left over from previous versions of Maven.

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

        

[jira] Updated: (MNG-2963) Do not update metadata unless the artifact actually made it down

Posted by "Jason van Zyl (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MNG-2963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jason van Zyl updated MNG-2963:
-------------------------------

    Fix Version/s:     (was: 2.0.9)
                   2.1-alpha-1

I'm going to fix this in Maven Artifact and we can decide to use that in 2.0.9 for the fix.

> Do not update metadata unless the artifact actually made it down
> ----------------------------------------------------------------
>
>                 Key: MNG-2963
>                 URL: http://jira.codehaus.org/browse/MNG-2963
>             Project: Maven 2
>          Issue Type: Bug
>          Components: Artifacts and Repositories
>    Affects Versions: 2.0.x
>            Reporter: Jason van Zyl
>            Assignee: Jason van Zyl
>             Fix For: 2.1-alpha-1
>
>
> We can also have a secondary check to see that if a metadata file contains no valid versions to nuke it and try to download a valid one. This will correct anything left over from previous versions of Maven.

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

        

[jira] Updated: (MNG-2963) Do not update metadata unless the artifact actually made it down

Posted by "Brian Fox (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MNG-2963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Fox updated MNG-2963:
---------------------------

    Fix Version/s:     (was: 2.0.8)
                   2.0.9

bumping to the next version

> Do not update metadata unless the artifact actually made it down
> ----------------------------------------------------------------
>
>                 Key: MNG-2963
>                 URL: http://jira.codehaus.org/browse/MNG-2963
>             Project: Maven 2
>          Issue Type: Bug
>          Components: Artifacts and Repositories
>    Affects Versions: 2.0.x
>            Reporter: Jason van Zyl
>             Fix For: 2.0.9
>
>
> We can also have a secondary check to see that if a metadata file contains no valid versions to nuke it and try to download a valid one. This will correct anything left over from previous versions of Maven.

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

        

[jira] Updated: (MNG-2963) Do not update metadata unless the artifact actually made it down

Posted by "Wendy Smoak (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MNG-2963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Wendy Smoak updated MNG-2963:
-----------------------------

      Description: We can also have a secondary check to see that if a metadata file contains no valid versions to nuke it and try to download a valid one. This will correct anything left over from previous versions of Maven.  (was: We can also have a secondard check to see that if a metadata file contains no valid versions to nuke it and try to download a valid one. This will correct anything left over from previous versions of Maven.)
    Fix Version/s: 2.0.8

To reproduce (with 2.0.7):

mvn archetype:create -DgroupId=com.example -DartifactId=test
cd test
# build offline with clean local repo, which fails
mvn install -Dmaven.repo.local=/path/to/tempdir -o
# repeat build while online-- still fails
mvn install -Dmaven.repo.local/path/to/tempdir

Example plugin metadata file:
 <?xml version="1.0" encoding="UTF-8" ?> 
- <metadata>
  <groupId>org.apache.maven.plugins</groupId> 
  <artifactId>maven-resources-plugin</artifactId> 
  </metadata>

> Do not update metadata unless the artifact actually made it down
> ----------------------------------------------------------------
>
>                 Key: MNG-2963
>                 URL: http://jira.codehaus.org/browse/MNG-2963
>             Project: Maven 2
>          Issue Type: Bug
>          Components: Artifacts and Repositories
>    Affects Versions: 2.0.x
>            Reporter: Jason van Zyl
>             Fix For: 2.0.8
>
>
> We can also have a secondary check to see that if a metadata file contains no valid versions to nuke it and try to download a valid one. This will correct anything left over from previous versions of Maven.

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

        

[jira] Closed: (MNG-2963) Do not update metadata unless the artifact actually made it down

Posted by "Jason van Zyl (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MNG-2963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jason van Zyl closed MNG-2963.
------------------------------

    Resolution: Fixed

In Maven Artifact we won't write out anything if we can't get hold of the actual metadata.

> Do not update metadata unless the artifact actually made it down
> ----------------------------------------------------------------
>
>                 Key: MNG-2963
>                 URL: http://jira.codehaus.org/browse/MNG-2963
>             Project: Maven 2
>          Issue Type: Bug
>          Components: Artifacts and Repositories
>    Affects Versions: 2.0.x
>            Reporter: Jason van Zyl
>            Assignee: Jason van Zyl
>             Fix For: 2.1-alpha-1
>
>
> We can also have a secondary check to see that if a metadata file contains no valid versions to nuke it and try to download a valid one. This will correct anything left over from previous versions of Maven.

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