You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Guillaume Nodet (JIRA)" <ji...@codehaus.org> on 2006/01/02 10:39:12 UTC
[jira] Created: (MNG-1908) M1 snapshots on legacy repos can not be
used with m2
M1 snapshots on legacy repos can not be used with m2
----------------------------------------------------
Key: MNG-1908
URL: http://jira.codehaus.org/browse/MNG-1908
Project: Maven 2
Type: Bug
Versions: 2.0.1
Reporter: Guillaume Nodet
Priority: Critical
It seems from the log info that m2 is trying to locate the artifact metadata on the repository.
SInce this artifact has been generated from m1, there is no metadata.
So whatever repository settings are configured, m2 will never update snapsots.
--
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-1908) snapshots not deployed using m2, or
deployed with uniqueVersion = false are not updated if present locally
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-1908?page=all ]
Brett Porter updated MNG-1908:
------------------------------
Fix Version: (was: 2.0.3)
2.1
fix only applied to trunk
> snapshots not deployed using m2, or deployed with uniqueVersion = false are not updated if present locally
> ----------------------------------------------------------------------------------------------------------
>
> Key: MNG-1908
> URL: http://jira.codehaus.org/browse/MNG-1908
> Project: Maven 2
> Type: Bug
> Components: Artifacts and Repositories
> Versions: 2.0.1
> Reporter: Guillaume Nodet
> Assignee: Brett Porter
> Priority: Critical
> Fix For: 2.1
>
> Original Estimate: 30 minutes
> Time Spent: 2 hours, 30 minutes
> Remaining: 0 minutes
>
> It seems from the log info that m2 is trying to locate the artifact metadata on the repository.
> SInce this artifact has been generated from m1, there is no metadata.
> So whatever repository settings are configured, m2 will never update snapsots.
--
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-1908) snapshots not deployed using m2, or
deployed with uniqueVersion = false are not updated if present locally
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-1908?page=all ]
Brett Porter updated MNG-1908:
------------------------------
Summary: snapshots not deployed using m2, or deployed with uniqueVersion = false are not updated if present locally (was: snapshots not deployed using m2, or deployed with uniqueVersion = false, cannot be downloaded by m2 as a snapshot)
downloading is fine, its the updating that's a problem
> snapshots not deployed using m2, or deployed with uniqueVersion = false are not updated if present locally
> ----------------------------------------------------------------------------------------------------------
>
> Key: MNG-1908
> URL: http://jira.codehaus.org/browse/MNG-1908
> Project: Maven 2
> Type: Bug
> Components: Artifacts and Repositories
> Versions: 2.0.1
> Reporter: Guillaume Nodet
> Assignee: Brett Porter
> Priority: Critical
> Fix For: 2.0.3
>
> Original Estimate: 30 minutes
> Remaining: 30 minutes
>
> It seems from the log info that m2 is trying to locate the artifact metadata on the repository.
> SInce this artifact has been generated from m1, there is no metadata.
> So whatever repository settings are configured, m2 will never update snapsots.
--
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-1908) M1 snapshots on legacy repos can not be
used with m2
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-1908?page=all ]
Brett Porter updated MNG-1908:
------------------------------
Fix Version: 2.0.3
> M1 snapshots on legacy repos can not be used with m2
> ----------------------------------------------------
>
> Key: MNG-1908
> URL: http://jira.codehaus.org/browse/MNG-1908
> Project: Maven 2
> Type: Bug
> Versions: 2.0.1
> Reporter: Guillaume Nodet
> Priority: Critical
> Fix For: 2.0.3
>
>
> It seems from the log info that m2 is trying to locate the artifact metadata on the repository.
> SInce this artifact has been generated from m1, there is no metadata.
> So whatever repository settings are configured, m2 will never update snapsots.
--
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] Commented: (MNG-1908) M1 snapshots on legacy repos can not
be used with m2
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-1908?page=comments#action_54945 ]
Brett Porter commented on MNG-1908:
-----------------------------------
look into the unique version = false problem which is probably the same too
> M1 snapshots on legacy repos can not be used with m2
> ----------------------------------------------------
>
> Key: MNG-1908
> URL: http://jira.codehaus.org/browse/MNG-1908
> Project: Maven 2
> Type: Bug
> Versions: 2.0.1
> Reporter: Guillaume Nodet
> Priority: Critical
> Fix For: 2.0.3
>
>
> It seems from the log info that m2 is trying to locate the artifact metadata on the repository.
> SInce this artifact has been generated from m1, there is no metadata.
> So whatever repository settings are configured, m2 will never update snapsots.
--
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-1908) snapshots not deployed using m2, or
deployed with uniqueVersion = false, cannot be downloaded by m2 as a
snapshot
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-1908?page=all ]
Brett Porter updated MNG-1908:
------------------------------
Component: Artifacts and Repositories
Summary: snapshots not deployed using m2, or deployed with uniqueVersion = false, cannot be downloaded by m2 as a snapshot (was: M1 snapshots on legacy repos can not be used with m2)
> snapshots not deployed using m2, or deployed with uniqueVersion = false, cannot be downloaded by m2 as a snapshot
> -----------------------------------------------------------------------------------------------------------------
>
> Key: MNG-1908
> URL: http://jira.codehaus.org/browse/MNG-1908
> Project: Maven 2
> Type: Bug
> Components: Artifacts and Repositories
> Versions: 2.0.1
> Reporter: Guillaume Nodet
> Priority: Critical
> Fix For: 2.0.3
>
>
> It seems from the log info that m2 is trying to locate the artifact metadata on the repository.
> SInce this artifact has been generated from m1, there is no metadata.
> So whatever repository settings are configured, m2 will never update snapsots.
--
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] Commented: (MNG-1908) snapshots not deployed using m2, or
deployed with uniqueVersion = false are not updated if present locally
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-1908?page=comments#action_58020 ]
Brett Porter commented on MNG-1908:
-----------------------------------
should be able to obtain this mix by merging r375485 and r375497 from the trunk to the maven-2.0.2 tag.
All trunk and branch builds will now contain it - eg:
http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20060207.061502.tar.gz
> snapshots not deployed using m2, or deployed with uniqueVersion = false are not updated if present locally
> ----------------------------------------------------------------------------------------------------------
>
> Key: MNG-1908
> URL: http://jira.codehaus.org/browse/MNG-1908
> Project: Maven 2
> Type: Bug
> Components: Artifacts and Repositories
> Versions: 2.0.1
> Reporter: Guillaume Nodet
> Assignee: Brett Porter
> Priority: Critical
> Fix For: 2.0.3
>
> Original Estimate: 30 minutes
> Time Spent: 2 hours
> Remaining: 0 minutes
>
> It seems from the log info that m2 is trying to locate the artifact metadata on the repository.
> SInce this artifact has been generated from m1, there is no metadata.
> So whatever repository settings are configured, m2 will never update snapsots.
--
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] Closed: (MNG-1908) snapshots not deployed using m2, or
deployed with uniqueVersion = false are not updated if present locally
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-1908?page=all ]
Brett Porter closed MNG-1908:
-----------------------------
Resolution: Fixed
note that this is significantly slower when using local snapshots not in the reactor during a daily or forced update period. We should investigate a better solution.
> snapshots not deployed using m2, or deployed with uniqueVersion = false are not updated if present locally
> ----------------------------------------------------------------------------------------------------------
>
> Key: MNG-1908
> URL: http://jira.codehaus.org/browse/MNG-1908
> Project: Maven 2
> Type: Bug
> Components: Artifacts and Repositories
> Versions: 2.0.1
> Reporter: Guillaume Nodet
> Assignee: Brett Porter
> Priority: Critical
> Fix For: 2.0.3
>
> Original Estimate: 30 minutes
> Time Spent: 2 hours, 30 minutes
> Remaining: 0 minutes
>
> It seems from the log info that m2 is trying to locate the artifact metadata on the repository.
> SInce this artifact has been generated from m1, there is no metadata.
> So whatever repository settings are configured, m2 will never update snapsots.
--
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-1908) snapshots not deployed using m2, or
deployed with uniqueVersion = false, cannot be downloaded by m2 as a
snapshot
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-1908?page=all ]
Brett Porter updated MNG-1908:
------------------------------
Assign To: Brett Porter
Remaining Estimate: 30 minutes
Original Estimate: 30 minutes
> snapshots not deployed using m2, or deployed with uniqueVersion = false, cannot be downloaded by m2 as a snapshot
> -----------------------------------------------------------------------------------------------------------------
>
> Key: MNG-1908
> URL: http://jira.codehaus.org/browse/MNG-1908
> Project: Maven 2
> Type: Bug
> Components: Artifacts and Repositories
> Versions: 2.0.1
> Reporter: Guillaume Nodet
> Assignee: Brett Porter
> Priority: Critical
> Fix For: 2.0.3
>
> Original Estimate: 30 minutes
> Remaining: 30 minutes
>
> It seems from the log info that m2 is trying to locate the artifact metadata on the repository.
> SInce this artifact has been generated from m1, there is no metadata.
> So whatever repository settings are configured, m2 will never update snapsots.
--
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