On 10/12/2008, at 7:52 PM, Hervé BOUTEMY wrote:
Hi Oleg,
In fact, I have only one question: why create a completely new
codebase?
Of course, the new code with less features is simpler *for the
moment*: less
features is less code.
This was my first reaction as well. I think you might win more fans by
making it easier to migrate from the existing version rather than
having to search/replace. Rewriting the docs would not be much fun
either :) I felt reading from a POM was a very important feature of
the previous version to encourage people to create one even for their
Ant projects.
As for this version, I like particularly the <config /> element. My
personal preference would be to remain explicit on the tags, eg <repo
id="something" file="/path" /> could be a file:// remote repo, but
it's implied to be local? And <dep /> is not descriptive enough that
it is a dependency group.
Features are exactly same as current ant-tasks: see the
documentation [1]
http://maven.apache.org/ant-tasks/index.html
I see some little differences/improvements that I like, for example
the
compact form
dependency name="ant:ant:1.6.5"
instead of
dependency groupId="ant" artifactId="ant" version="1.6.5"
But it doesn't change much things: this additional syntax could
simply be
added to the actual ant-tasks.
+1. Supporting both is good, but I prefer the look of the original.
To me, this seems like reinventing the wheel: there are good ideas
in the new
one, which should be kept, but nothing fundamental.
Current trunk depends on maven-project, maven-settings, maven-
artifact and
wagon components, which are now replaced in Maven 3 with Mercury:
yes, with
Maven 3.0, "Maven Ant Tasks 3.0" should become naturally "Mercury
Ant Tasks
1.0", simply by upgrading components.
Did you try to upgrade maven-ant-tasks trunk?
Regards,
Hervé
Cheers,
Brett
Le lundi 08 décembre 2008, Oleg Gusakov a écrit :
Whoever might be interested, and especially Herve:
I am putting together a simplified ant wrapper for Mercury. Can you
please critique http://jira.codehaus.org/browse/MERCURY-48 ?
Main idea - create a simple to use syntax, yet being able to extend
it
to full power of Mercury. The game plan is:
* configuration
* classpath resolution
* repository writes (install, deploy -they are the same in Mercury)
* reading deps. from pom
* ? reading config from settings
Thanks,
Oleg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Brett Porter
[EMAIL PROTECTED]
http://blogs.exist.com/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
