ssle for it. :)
B
-Original Message-
From: Kenney Westerhof [mailto:[EMAIL PROTECTED]
Sent: Saturday, June 09, 2007 3:57 AM
To: Maven Developers List
Subject: Re: Idea for enhancement
I'm basically against this idea.
It can result in polluted jars very easily. Even if you have 2 poms
I'm basically against this idea.
It can result in polluted jars very easily. Even if you
have 2 poms in the same dir, both specifying different source directories,
the files in target/ will overlap. the second executed pom will also contain
the files from the first executed pom.
Unless the tar
On 07/06/2007, at 10:11 AM, Deacon, Brian wrote:
But does the Maven Jedi Council have any problem in principal with
allowing the element to specify the name of the pom file?
Thought of it already someone has, ? http://jira.codehaus.org/
browse/MNG-1493
I'd actually be happy with treat
But does the Maven Jedi Council have any problem in principal with
allowing the element to specify the name of the pom file?
Brian
-Original Message-
From: Evan Worley [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 06, 2007 3:24 PM
To: Maven Developers List
Subject: Re: Idea for enhanc
Brian,
I have encountered the same issue and I believe I can safely assume that you
are in a java/C# environment in which you would like to have one pom which
has two modules, one for the java component and one for the dotnet.
One thing to consider is that even if you could construct the pom thi
Hi guys,
Thought I'd kick this around to see how it would be received.
I just posted to the Users list and got confirmation that I can't
currently do the following in a pom parent
multi-module pom:
foo/bar
foo/bar/SiblingPom.xml
The current behavior is that it looks for foo/bar/S
