[
https://issues.apache.org/jira/browse/ARCHETYPE-393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed ARCHETYPE-393.
------------------------------------
Resolution: Auto Closed
This issue has been auto closed because it has been inactive for a long period
of time. If you think this issue still applies, retest your problem with the
most recent version of Maven and the affected component, reopen and post your
results.
> Provide ability to generate a submodule without parent declaration
> ------------------------------------------------------------------
>
> Key: ARCHETYPE-393
> URL: https://issues.apache.org/jira/browse/ARCHETYPE-393
> Project: Maven Archetype
> Issue Type: Improvement
> Affects Versions: 2.1
> Reporter: cdorot
> Priority: Major
>
> My use case deals about a multi modules projects having the following
> structure :
> {noformat}+ ${project-reactor}
> + ${project-module1}
> + ${project-module2}
> + ...
> + ${project-bom}
> + ${project-parent}{noformat}
> Each of the submodule's pom.xml (inside $\{project-module1},
> $\{project-module2}) which will be defined later, will have a parent
> declaration referring to $\{project-parent}.
> As mentioned in ARCHETYPE-110, the current implementation overwrites parent
> information if there are no existing parent definition inside the body of the
> pom.xml. So if we don't want such declaration we haven't no alternatives.
> It could be great if we have a way to have choice for each module to have or
> NOT the parent information.
> This could be done in :
> * /src/main/resources/META-INF/maven/archetype-metadata.xml (add a
> "generate-parent-declaration" for the "module" tag)
> * add a meta-information in the pom.xml such as <!-- @@NOPARENT @@ -->
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
