You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Tim Clemons (JIRA)" <ji...@codehaus.org> on 2006/01/10 00:53:01 UTC
[jira] Created: (MRM-59) Proxy should work transparently with
either maven 1.x or 2.x repositories.
Proxy should work transparently with either maven 1.x or 2.x repositories.
--------------------------------------------------------------------------
Key: MRM-59
URL: http://jira.codehaus.org/browse/MRM-59
Project: Maven Repository Manager
Type: New Feature
Reporter: Tim Clemons
Have the maven-proxy act as either a maven 1.x or maven 2.x repository, depending on which client accesses it. Brett believed this should be managable with aliasing.
This was originally posted as a maven-proxy feature at http://jira.codehaus.org/browse/MAVENPROXY-39
--
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: (MRM-59) Proxy should work transparently with
either maven 1.x or 2.x repositories.
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-59?page=all ]
Brett Porter updated MRM-59:
----------------------------
Fix Version: 1.0-alpha-1
Component: remote proxy
> Proxy should work transparently with either maven 1.x or 2.x repositories.
> --------------------------------------------------------------------------
>
> Key: MRM-59
> URL: http://jira.codehaus.org/browse/MRM-59
> Project: Maven Repository Manager
> Type: New Feature
> Components: remote proxy
> Reporter: Tim Clemons
> Fix For: 1.0-alpha-1
>
>
> Have the maven-proxy act as either a maven 1.x or maven 2.x repository, depending on which client accesses it. Brett believed this should be managable with aliasing.
> This was originally posted as a maven-proxy feature at http://jira.codehaus.org/browse/MAVENPROXY-39
--
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: (MRM-59) Proxy should work transparently with
either maven 1.x or 2.x repositories.
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-59?page=comments#action_59376 ]
Brett Porter commented on MRM-59:
---------------------------------
Can you describe the solution you are thinking of? 12 hours sounds like it might be more than I was anticipating.
All I figured for this was:
- the MRM already handles working with remote repositories of any format by taking the artifact and converting it to the correct layout, right?
- the proxy servlet would be configured so that /proxy-m1/* maps to the proxy servlet with path format = legacy. So a path under there would be groupId/types/artifactId-version.ext
- the proxy servlet would be configured so that /proxy-m2/* maps to the proxy servlet with path format = default. So a path under there would be groupId/artifactId/version/artifactId-version.ext
> Proxy should work transparently with either maven 1.x or 2.x repositories.
> --------------------------------------------------------------------------
>
> Key: MRM-59
> URL: http://jira.codehaus.org/browse/MRM-59
> Project: Maven Repository Manager
> Type: New Feature
> Components: remote proxy
> Reporter: Tim Clemons
> Assignee: Edwin Punzalan
> Fix For: 1.0-alpha-1
>
> Original Estimate: 12 hours
> Remaining: 12 hours
>
> Have the maven-proxy act as either a maven 1.x or maven 2.x repository, depending on which client accesses it. Brett believed this should be managable with aliasing.
> This was originally posted as a maven-proxy feature at http://jira.codehaus.org/browse/MAVENPROXY-39
--
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: (MRM-59) Proxy should work transparently with either
maven 1.x or 2.x repositories.
Posted by "Edwin Punzalan (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-59?page=all ]
Edwin Punzalan closed MRM-59:
-----------------------------
Resolution: Fixed
> Proxy should work transparently with either maven 1.x or 2.x repositories.
> --------------------------------------------------------------------------
>
> Key: MRM-59
> URL: http://jira.codehaus.org/browse/MRM-59
> Project: Maven Repository Manager
> Type: New Feature
> Components: remote proxy
> Reporter: Tim Clemons
> Assignee: Edwin Punzalan
> Fix For: 1.0-alpha-1
>
> Original Estimate: 12 hours
> Remaining: 12 hours
>
> Have the maven-proxy act as either a maven 1.x or maven 2.x repository, depending on which client accesses it. Brett believed this should be managable with aliasing.
> This was originally posted as a maven-proxy feature at http://jira.codehaus.org/browse/MAVENPROXY-39
--
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: (MRM-59) Proxy should work transparently with
either maven 1.x or 2.x repositories.
Posted by "Edwin Punzalan (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-59?page=all ]
Edwin Punzalan updated MRM-59:
------------------------------
Remaining Estimate: 12 hours
Original Estimate: 12 hours
> Proxy should work transparently with either maven 1.x or 2.x repositories.
> --------------------------------------------------------------------------
>
> Key: MRM-59
> URL: http://jira.codehaus.org/browse/MRM-59
> Project: Maven Repository Manager
> Type: New Feature
> Components: remote proxy
> Reporter: Tim Clemons
> Assignee: Edwin Punzalan
> Fix For: 1.0-alpha-1
>
> Original Estimate: 12 hours
> Remaining: 12 hours
>
> Have the maven-proxy act as either a maven 1.x or maven 2.x repository, depending on which client accesses it. Brett believed this should be managable with aliasing.
> This was originally posted as a maven-proxy feature at http://jira.codehaus.org/browse/MAVENPROXY-39
--
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