You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "John Casey (JIRA)" <ji...@codehaus.org> on 2005/06/07 01:11:22 UTC
[jira] Created: (MNG-452) --update-snapshots overwrites metadata from locally-installed snapshot artifacts
--update-snapshots overwrites metadata from locally-installed snapshot artifacts
--------------------------------------------------------------------------------
Key: MNG-452
URL: http://jira.codehaus.org/browse/MNG-452
Project: Maven 2
Type: Bug
Components: maven-artifact
Reporter: John Casey
Fix For: 2.0-alpha-3
this appears to be a problem with detection of newer snapshot metadata installed on the local repo.
to reproduce:
1. make an api change in a m2 dependency (I found this by making an api change to plexus-container-default)
2. build the changed api using 'm2 install' to install the SNAPSHOT artifact locally
3. bootstrap m2.
(at this point, if you look at the .version.txt file for that artifact, you should see a timestamped build from the repository in place of your -SNAPSHOT version from the local install)
4. bootstrap m2 again.
On the second run of the bootstrap, you'll get all kinds of compilation errors, as the api changes you've made to maven in accordance with the new api of your dependency (plexus in my case) are rolled back in the local repo.
--
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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Updated: (MNG-452) --update-snapshots overwrites metadata from locally-installed snapshot artifacts
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-452?page=all ]
Brett Porter updated MNG-452:
-----------------------------
Description:
this appears to be a problem with detection of newer snapshot metadata installed on the local repo.
to reproduce:
1. make an api change in a m2 dependency (I found this by making an api change to plexus-container-default)
2. build the changed api using 'm2 install' to install the SNAPSHOT artifact locally
3. bootstrap m2.
(at this point, if you look at the .version.txt file for that artifact, you should see a timestamped build from the repository in place of your -SNAPSHOT version from the local install)
4. bootstrap m2 again.
On the second run of the bootstrap, you'll get all kinds of compilation errors, as the api changes you've made to maven in accordance with the new api of your dependency (plexus in my case) are rolled back in the local repo.
was:
this appears to be a problem with detection of newer snapshot metadata installed on the local repo.
to reproduce:
1. make an api change in a m2 dependency (I found this by making an api change to plexus-container-default)
2. build the changed api using 'm2 install' to install the SNAPSHOT artifact locally
3. bootstrap m2.
(at this point, if you look at the .version.txt file for that artifact, you should see a timestamped build from the repository in place of your -SNAPSHOT version from the local install)
4. bootstrap m2 again.
On the second run of the bootstrap, you'll get all kinds of compilation errors, as the api changes you've made to maven in accordance with the new api of your dependency (plexus in my case) are rolled back in the local repo.
Fix Version: (was: 2.0-beta-1)
2.0-beta-2
Environment:
> --update-snapshots overwrites metadata from locally-installed snapshot artifacts
> --------------------------------------------------------------------------------
>
> Key: MNG-452
> URL: http://jira.codehaus.org/browse/MNG-452
> Project: Maven 2
> Type: Bug
> Components: maven-artifact
> Reporter: John Casey
> Fix For: 2.0-beta-2
>
>
> this appears to be a problem with detection of newer snapshot metadata installed on the local repo.
> to reproduce:
> 1. make an api change in a m2 dependency (I found this by making an api change to plexus-container-default)
> 2. build the changed api using 'm2 install' to install the SNAPSHOT artifact locally
> 3. bootstrap m2.
> (at this point, if you look at the .version.txt file for that artifact, you should see a timestamped build from the repository in place of your -SNAPSHOT version from the local install)
> 4. bootstrap m2 again.
> On the second run of the bootstrap, you'll get all kinds of compilation errors, as the api changes you've made to maven in accordance with the new api of your dependency (plexus in my case) are rolled back in the local repo.
--
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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Updated: (MNG-452) --update-snapshots overwrites metadata from locally-installed snapshot artifacts
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-452?page=all ]
Brett Porter updated MNG-452:
-----------------------------
Description:
this appears to be a problem with detection of newer snapshot metadata installed on the local repo.
to reproduce:
1. make an api change in a m2 dependency (I found this by making an api change to plexus-container-default)
2. build the changed api using 'm2 install' to install the SNAPSHOT artifact locally
3. bootstrap m2.
(at this point, if you look at the .version.txt file for that artifact, you should see a timestamped build from the repository in place of your -SNAPSHOT version from the local install)
4. bootstrap m2 again.
On the second run of the bootstrap, you'll get all kinds of compilation errors, as the api changes you've made to maven in accordance with the new api of your dependency (plexus in my case) are rolled back in the local repo.
was:
this appears to be a problem with detection of newer snapshot metadata installed on the local repo.
to reproduce:
1. make an api change in a m2 dependency (I found this by making an api change to plexus-container-default)
2. build the changed api using 'm2 install' to install the SNAPSHOT artifact locally
3. bootstrap m2.
(at this point, if you look at the .version.txt file for that artifact, you should see a timestamped build from the repository in place of your -SNAPSHOT version from the local install)
4. bootstrap m2 again.
On the second run of the bootstrap, you'll get all kinds of compilation errors, as the api changes you've made to maven in accordance with the new api of your dependency (plexus in my case) are rolled back in the local repo.
Fix Version: (was: 2.0-alpha-3)
2.0-beta-1
Environment:
> --update-snapshots overwrites metadata from locally-installed snapshot artifacts
> --------------------------------------------------------------------------------
>
> Key: MNG-452
> URL: http://jira.codehaus.org/browse/MNG-452
> Project: Maven 2
> Type: Bug
> Components: maven-artifact
> Reporter: John Casey
> Fix For: 2.0-beta-1
>
>
> this appears to be a problem with detection of newer snapshot metadata installed on the local repo.
> to reproduce:
> 1. make an api change in a m2 dependency (I found this by making an api change to plexus-container-default)
> 2. build the changed api using 'm2 install' to install the SNAPSHOT artifact locally
> 3. bootstrap m2.
> (at this point, if you look at the .version.txt file for that artifact, you should see a timestamped build from the repository in place of your -SNAPSHOT version from the local install)
> 4. bootstrap m2 again.
> On the second run of the bootstrap, you'll get all kinds of compilation errors, as the api changes you've made to maven in accordance with the new api of your dependency (plexus in my case) are rolled back in the local repo.
--
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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org