[
http://jira.codehaus.org/browse/MERCURY-48?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=157512#action_157512
]
Oleg Gusakov commented on MERCURY-48:
-------------------------------------
Gilles, than you for the comment!
*#1 coupling with repo*
In Mercury - Repository was re-implemented -
http://docs.codehaus.org/display/MAVEN/Mercury+Repository+Abstraction, as a
result - I can plug in any object, implementing Repository interface. For now
there are
* RemoteM2
* LocalM2
* LocalFlat - write-only repository with one folder, holding all the artifacts
I plan to also add read-only metadata-only repository, to which you will be
able to drop POMs
gem also looks like a good candidate.
All those are (will be) captured in the *type* attribute of the *repo* tag, so
that *<merc:repo type="flat" dir="/opt/plugins" id="local-store"/>* will map
into it's own implementation. n the future - it will be nice to provide
type->implementation mapping configuration
*#2 re-execution*
<merc:resolve /> is equivalent to <path />, it does create a named path or
appends to the existing one (if you use *refpathid* instead of *pathid*) as a
result of it's execution. I fails it if *pathId* already exists, so idea would
be to place it so that it executes once. Treat it almost as a data type, and
place so that it executes once.
Does it work ?
> Document and vet the design
> ---------------------------
>
> Key: MERCURY-48
> URL: http://jira.codehaus.org/browse/MERCURY-48
> Project: Mercury
> Issue Type: Sub-task
> Components: Ant tasks
> Reporter: Oleg Gusakov
> Assignee: Oleg Gusakov
> Original Estimate: 2 days
> Remaining Estimate: 2 days
>
--
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
