[
https://issues.apache.org/jira/browse/ARCHETYPE-457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed ARCHETYPE-457.
------------------------------------
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.
> Clarify documentation around module.name and module.dir
> -------------------------------------------------------
>
> Key: ARCHETYPE-457
> URL: https://issues.apache.org/jira/browse/ARCHETYPE-457
> Project: Maven Archetype
> Issue Type: Bug
> Affects Versions: 2.2
> Reporter: Konrad Windszus
> Priority: Major
>
> From the reference at
> https://maven.apache.org/archetype/archetype-models/archetype-descriptor/archetype-descriptor.html#class_module
> is is unclear how the attribute name is evaluated. For me the following
> behaviour would make sense
> - dir: the name of the source directory (from which the new module will be
> created)
> - name: the name of the module directory (destination). Usually is equivalent
> to artifactId. Currently the name does not seem to be evaluated at all.
> That way no placeholder replacement on the weird syntax __<property>__ would
> need to take place on the dir entry, but rather that would just specify from
> where to copy the files for the module (this can always be hardcoded). The
> placeholder mechanism (i.e. the regular one with the $ syntax would then only
> be necessary on id and name attributes.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
