On Thu, 18 Aug 2011 14:00:26 -0500
Wayne Fay wayne...@gmail.com wrote:
I guess this has been asked before, but is there any way to
gracefully handle situations in a multi-level modular project where
the artifactId does not always correspond to the folder name of the
module?
Maven
Hi,
I guess this has been asked before, but is there any way to gracefully
handle situations in a multi-level modular project where the artifactId
does not always correspond to the folder name of the module?
It's especially about the scm url and connection.
So my folder structure is like this:
Hi,
I am not aware of any other solution, but I remember the following
comment by Benjamin, quoted from http://jira.codehaus.org/browse/MNG-5000:
The cause of the issue was that module-2 has a different artifactId
than its module name. Let me stress that such a layout is a recipe for
I guess this has been asked before, but is there any way to gracefully
handle situations in a multi-level modular project where the artifactId
does not always correspond to the folder name of the module?
Maven operates under certain conventions. This is not the convention,
thus it is not well
