How about moving it to Mercury and closing it there, or closing as
won't fix?
It would be confusing seeing these show up on a changleog for an
artifact release (though I expect this might be about to be folded
back into MNG?)
Thanks,
Brett
On 28/11/2008, at 9:23 AM, Jason van Zyl (JIRA) wrote:
[ http://jira.codehaus.org/browse/MARTIFACT-7?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason van Zyl closed MARTIFACT-7.
---------------------------------
Resolution: Fixed
We'll deal with this in mercury.
Clear separation of local versus remote concerns
------------------------------------------------
Key: MARTIFACT-7
URL: http://jira.codehaus.org/browse/MARTIFACT-7
Project: Maven Artifact
Issue Type: Improvement
Reporter: Jason van Zyl
Fix For: 3.0
The resolution very much couples local with remote repositories.
For example simply querying for all available versions requires
some twiddling and faking out the resolver because the local
metadata is always used but I only want to know about remote
repositories. We just need to be able to query remote repositories
easily. Getting all the remote versions to prevent redeployment is
a perfect use case.
--
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
--
Brett Porter
[EMAIL PROTECTED]
http://blogs.exist.com/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
