Note that there are some explanatory texts on larger screens.

plurals
  1. USpoussma
    primarykey
    data
    text
    plurals
    1. COI entirely agree with you, they are **meant** to be autonomous. In practice, this is the case at the beginning of a project and after two weeks it becomes a spaghetti because it was easiest to copy a file from another module instead of configuring a plugin in maven... BTW, configuring all the versions of the dependencies in the main pom as the advantage to be consistent across all modules. If your need is just to execute multiple pom, maybe the modules aren't the solution.
      singulars
    2. COwhy the child need to know the parent? To get the default plugin configuration, the common properties, the artifact versions, ... Why in maven they decided that it must be in the direct sub folder... and not configurable in contrary of everything else... this I don't know. But the organization allows the user to easily copy / access resources of another module (even if it is probably not a good practice) by using ${basedir}/../my-module/...
      singulars
    3. COI am afraid that _must be located under a subdirectory_ means there is no way to change that. If that would have been possible, you'll have to configure the main pom to declare where are the children and in the children where is the parent. Nothing like that exists in maven.
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload