On 14/05/2011 9:32 AM, labulle22 wrote:
I want to build a rather different version of my multi-module project (in
addition to the standard build) without having to dive into Maven profiles
that seem not so flexible at first glance. Having 2 different set of POMs is
surely not optimal but would be acceptable in my case.
Can you describe why you want to do this?
What are you trying to build?
Since thousands of different applications are built with Maven every
day, there probably is a best practice already known for your situation.
There is no point reinventing the wheel.
Ron
Regards,
Bruno
2011/5/14 Wendy Smoak<wsm...@gmail.com>
On Sat, May 14, 2011 at 7:21 AM, labulle22<labull...@gmail.com> wrote:
How to configure Maven in order to be able to not use the default pom
file
name ("pom.xml") for the sub-projects of a main project? AFAIU the -f
option
only applies on main project.
Why are your poms named differently?
(This usually comes up when you're trying to do something for which
there's a better solution, so explaining the underlying problem you're
trying to solve will get you better answers.)
--
Wendy
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
