Herve,
It also works now - I can compile java with mercury supplied jars. You
can checkout the Mercury trunk. Unfortunately - thank to unknown
samaritan - I cannot logon to people.apache.org and cannot deploy
snapshots, so you'll have to install Mercury snapshots and package
mecrcury-ant: it creates a shaded ..-all.jar that contains everything,
including maven trunk components.
Then look at build.xml in the root on mercury-ant-tasks project.
My plan is outlined in http://jira.codehaus.org/browse/MERCURY-10, I
hope to finish all major functionality early next week, then we can
tweak/modify anything to your heart's desire :)
Thanks,
Oleg
Hervé BOUTEMY wrote:
ok, I understand: for you, the tasks code is big then it is difficult to
integrate Mercury, and for me, Mercury is big then it is difficult to
integrate it into the tasks. :)
For the doc and the overall logic, now that the doc has been rewritten, split
into parts (big thank you Dennis), learning Maven Ant Tasks should be easier:
the usage section is a good introduction
http://maven.apache.org/ant-tasks/usage.html
but this Mercury change is a chance to have a second look at the tasks
organization to improve their usability.
I had a second look at MERCURY-48 for the proposed syntax.
Like for the compact dependency syntax, I see some areas of
improvements/simplifications in it. On the other hand, I see some unneeded
changes, like dep instead of dependencies, write instead of deploy.
I think good ideas from your proposal can be merged with existing syntax:
- config to assemble local repo, remote repo and settings (these 3 should not
have their name changed IMHO)
- separation of dependencies and resolve tasks
I'll work on it more closely next days.
Regards,
Hervé
Le mercredi 10 décembre 2008, Oleg Gusakov a écrit :
Herve,
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.
At first I honestly tried to plug in Mercury into existing code, but:
* as the current code is functionally big, I would have to implement
everything before trying it out in real
* I have been always confused in the past by how to use existing
maven-ant-tasks, and had to look it up each time. Although on conceptual
level it's exactly the same, I want to simplify usage and make it a
little more logical: syntax, usage pattern - at least how I understand
this logic and ant usage patterns.
I completely agree that there are no fundamental changes, after all
Mercury is just a simplification of existing Maven components. And in
this spirit I tried to simplify ant tasks as well :)
I would really appreciate if you can help/guide this development, I
believe we can do a lot of cool things if separated from the former code
base and syntax obligations.
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]
