Lately, more developers have started changing pom.xml files,
which is a good thing, even for big changes :)
Of course, not everyone is a Maven expert yet.
Some changes cause issues (mainly for our users).
In the past, I fixed those issues directly, but that approach does not
devs kept committing new instances of the same issue.
So instead, I 'll send "[maven feedback]" mails, explaining the problem
and how to fix it.
Please fix the problem in a timely manner (or signal me that you can't
fix it a timely manner).
Don't take such mails personally - everyone (including me) introduces
I 'll CC the drools-dev list, so everyone can learn all maven pitfalls.
Hopefully, this way we can *keep our build fast* and stable.
Show replies by date