Apache EasyAnt

1 on this

On one hand I agree, on the other hand I think it may be a problem for reproducibility. Reproducibility is not an easy tassk any way, you always depend on your environment, on the network, ... What I usually do when I setup a build system is that ... [More] things that I can't put under control of the build system for any reason (too complex, costs too much, ...) - like the [Less]

It seems that certain plugins could be very useful this way (e.g. the emma plugin), others seems they could pose great problems (e.g. a plugin that could do some sort of expansion at the process-sources phase). This could be dangerous. Maybe when creating a plugin you can define whether or not it's

After a night of reflection i think it's enough to have: - system plugins - project plugins and hooks for customization of either of these plugins. I think we will introduce settings.xml in 0.6, but i've made some changes on trunk revision, so now you should be able to use system plugins as excepted.

Humm my bad it seems i have made an error when i've refactored the example directory i will update the example tomorrow. I am really interested in understanding how easyant addresses the In a few words talking about multi-modules project we have ... [More] almost two differents needs : 1. A way to manage the choregraphy of all submodules (done by meta-build [Less]

Yes! (See bellow) I think both (System / globals plugins) can be configurated in settings.xml Maybe it's enough But i think it could be pretty usefull to have globals plugins. Suppose you work on a project with your team and all plugins that checks code quality (code coverage / checkstyle / etc...) are not enabled in your

Hi guys, I saw there is a example-multimodule in the examples directory of easyant... but it's empty! I am really interested in understanding how easyant addresses the problem of multimodule projects, so it would be great to have some information there. Can you please give me a high level explanation and/or update the

Hi Jean-Louis, I am not sure I understand what you define as global project plugins. Is it a sort of developer's preferences regarding plugins that he wants to use in all projects? If that is the case it seems to me that what this means is another way of declaring plugins (outside of ${EASYANT_HOME}/settings.xml).

Hi Riccardo, Nice :p I think this is the correct flow to do it . I think we should change this, for historical reasons easyant was only able to build if such a file exists. As we introduce "system plugins" we should be able to run it even if module.ivy doesn't exists. I think we should make a distinction between :

Hi guys, I am developing a build framework for my company and, through Xavier, I found out about this project which seems to go the same direction I was heading for. I was playing with easyant, going through the code and taking a quick glance at how things work, I saw this post, which actually is related