On Wed, 24 Feb 2016 09:52:06 +0100, Alan Bateman <alan.bate...@oracle.com>
wrote:
On 23/02/2016 21:10, Robert Scholte wrote:
:
If I understand this correctly I need to know the module name.
Has there been any discussion around having the module name in the POM?
From the mails then it sounds like the project is mostly "unaware" that
it is creating a module. The other thing that comes to mind is the
source layout and whether it will get to the point where the module name
is in the file path. I'm mostly thinking of multi module projects where
one might have the source to multiple modules in the same source tree.
-Alan
The name of the module with not end up in pom-4.0.0, it'll simply break
the xsd and would have effect on all other tools/IDEs/etc depending on the
pom.
The only place where one might specify the module name is in the
configuration of the maven-compiler-plugin.
In Brussels we talked about multimodules, but it makes more sense that 1
Maven project contains zero or one module-info[1].
And yes, I think a MavenProject will probably be unaware of its own module
name. It knows its source roots and outputdirectories (for both main/java
and test/java) and the packaged jar. Based on the availability of the
module-info in one of these locations it knows how to construct the
commandline arguments.
At least, this is what I'm hoping to achieve.
thanks,
Robert
[1] https://twitter.com/rfscholte/status/694599731515899904
