Maven is almost always right.
Figure out why your methodology is not following "Best Practices" and
change the way that you work so that maven does it for you automatically.
You can fight Maven as much as you want but it will always win.
If you can identify why you are building an application that is so
unusual that no one else has your workflow, then you may be able to get
a solution.
In most cases, the application is pretty normal, it is the newbee's
workflow that is broken.
If you are pioneering some new application platform, you may have a
problem but I think that I have seen ejbs with dependent libraries being
used in applications before.
Mavenize your workflow.
I hope that this helps.
Ron
On 04/10/2010 6:49 AM, Caoilte O'Connor wrote:
It bites in quite a lot of places. I wanted to define one "execution"
of the build-helper-maven-plugin in a parent pom and another in one of
it's children then have the two merged together. However, Maven
overrode the parent configuration in the child.
Given that some sections of the pom (eg dependencies, properties)
merge so seamlessly it is disappointing to discover sections which
don't. Perhaps future versions of Maven will improve things.
c
On Sat, Oct 2, 2010 at 3:41 PM, Marshall Schor<[email protected]> wrote:
On 10/2/2010 7:42 AM, Benjamin Bentmann wrote:
Xavier D. wrote:
My pom structure is: pom.xml has a parent: parent-pom.xml.
Both have a<resources> section to include files.
The (child) pom.xml is executed directly and has the effect of only copying
the child's resources. Commenting out this resource section, results in
the parent's resources being copied.
This is expected behavior,<resources> given in a child POM are not merged
with<resources> in the parent but completely override those.
I'm curious as to why this design decision was taken, versus an approach which
allows merging, or perhaps some kind of user (pom - specified) choice.
I was "bitten" by this also.
-Marshall Schor
Benjamin
---------------------------------------------------------------------
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]
---------------------------------------------------------------------
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]
