Conceptually, I believe this is a case bad separation of concerns. Build
tools and production code often require different development skills and
techniques, have different dependencies. You really need to wear two
different hats to work on the tools and production code, and I think
many devs have difficulties switching (I certainly do). As a result,
collocated build tools tend to be poorly written, with no or very little
tests and virtually impossible to refactor. Of course, keeping build
tools outside of production codebase does not guarantee anything by
itself, but I think it increases the likelihood of maintainable code.
Other practical problems
* can't run partial lifecycle (as in "mvn generate-sources"), or at
least not always. java annotation processors, for example, must be
packages into jars, so really must run "mvn package".
* no m2e integration
--
Regards,
Igor
On 2015-01-15 0:43, Kristian Rosenvold wrote:
2015-01-15 4:48 GMT+01:00 Igor Fedorenko <i...@ifedorenko.com>:
Although I generally *strongly* discourage resolution of plugins and
plugin dependencies from the reactor
Why ?
Kristian
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
