[
http://jira.codehaus.org/browse/MERCURY-48?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=157967#action_157967
]
Oleg Gusakov edited comment on MERCURY-48 at 12/14/08 4:52 PM:
---------------------------------------------------------------
* *config* - I would like it to be as little maven-like, as possible, I think
it should be yet another dependency management framework for ant. Usually
developers are using the temr *config*,not *settings*. I don't hold on to it,
we can create several syntaxes, or change this one.
* *layout* - I don't agree with this one as truely - this should be a mapping
from repository id to repository implementation class. I can envision
type="gem", type="cpan", etc. This also explains deviation from "local/remore"
- they all are just implementations of a repository. The default one is
type="m2" and that uniquely select the correct implementation.
What could be wrong - *dir* and *url* attributes, but they seem to be generic
enough for any implementation
* *dep* instead of dependencies - to make it shorter, no other ideas. Two
parallel syntaxes possible
* *pom* - one <dependency ..> can define either one artifact, or a whole
subtree - if it hides a pom file behind it. *This is a moot point* because - as
i said - I would like to get away from Maven specifics. Mercury in general (and
ant tasks inherit it) - does not depend on POM files - it defines an abstract
DependencyProcessor interface, and anyone can plug in their own. This btw also
explains *xmlns* - I would like to be able to interpret dependency in the
context of a supplied DependencyProcessor. Maybe it should be higher up - in
the <dep[endencies] ..> tag. Or - maybe - we should allow to mix-n-match
* *write* - totally agree with *file* instead of *bin*, already implemented as
file.
* *attach* - can you give an example what are you trying to address? Currently
one can *<write name="a:a:1.0:tests" .../>*, which is equivalent to attaching
the tests classifier jar. Or you can write a zip file with *name="a:b:1.0::zip"*
The full syntax of the name is defined in Mercury as:
"groupId:artifactId:version:classifier:type:scope:{attributes}", where
attributes is a comma-separated list of name=value pairs.
And - *Herve* - thank you for the comments! Don't hesitate to indicate if I
mis-understand something - rarely, but it happens :)
was (Author: olle):
* *config* - I would like it to be as little maven-like, as possible, I
think it should be yet another dependency management framework for ant. Usually
developers are using the temr *config*,not *settings*. I don't hold on to it,
we can create several syntaxes, or change this one.
* *layout* - I don't agree with this one as truely - this should be a mapping
from repository id to repository implementation class. I can envision
type="gem", type="cpan", etc. This also explains deviation from "local/remore"
- they all are just implementations of a repository. The default one is
type="m2" and that uniquely select the correct implementation.
What could be wrong - *dir* and *url* attributes, but they seem to be generic
enough for any implementation
* *dep* instead of dependencies - to make it shorter, no other ideas. Two
parallel syntaxes possible
* *pom* - one <dependency ..> can define either one artifact, or a whole
subtree - if it hides a pom file behind it. *This is a moot point* because - as
i said - I would like to get away from Maven specifics. Mercury in general (and
ant tasks inherit it) - does not depend on POM files - it defines an abstract
DependencyProcessor interface, and anyone can plug in their own. This btw also
explains *xmlns* - I would like to be able to interpret dependency in the
context of a supplied DependencyProcessor. Maybe it should be higher up - in
the <dep[endencies] ..> tag. Or - maybe - we should allow to mix-n-match
* *write* - totally agree with *file* instead of *bin*, already implemented as
file.
* *attach* - can you give an example what are you trying to address? Currently
one can *<write name="a:a:1.0:tests" .../>*, which is equivalent to attaching
the tests classifier jar. Or you can write a zip file with *name="a:b:1.0::zip"*
The full syntax of the name is defined in Mercury as:
"groupId:artifactId:version:classifier:type:scope:{attributes}", where
attributes is a comma-separated list of name=value pairs.
> 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
> Time Spent: 1 day
> Remaining Estimate: 1 day
>
--
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
