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.
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. 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é 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]
