You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Maarten Mulders (Jira)" <ji...@apache.org> on 2021/04/02 14:09:00 UTC
[jira] [Updated] (MARCHETYPES-72) Include empty .mvn/jvm.config and
.mvn/maven.config in all archetypes
[ https://issues.apache.org/jira/browse/MARCHETYPES-72?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maarten Mulders updated MARCHETYPES-72:
---------------------------------------
Description:
All [Maven archetypes|https://maven.apache.org/archetypes/index.html] should generate two empty files in the *.mvn* folder of the generated project: *jvm.config* and *maven.config*.
There are two reasons for this:
# This points users to the fact that they can use those files to customise their build.
# If the project is a multi-module project or is later converted to a multi-module project, Maven will be able to reliably determine the root of that multi-module project.
was:
All [Maven archetypes|https://maven.apache.org/archetypes/index.html] should generate two (possibly empty) files in the *.mvn* folder of the generated project: *jvm.config* and *maven.config*.
There are two reasons for this:
# This points users to the fact that they can use those files to customise their build. For that reason, we might even include a comment in those files referring them to [the documentation|https://maven.apache.org/configure.html].
# If the project is a multi-module project or is later converted to a multi-module project, Maven will be able to reliably determine the root of that multi-module project.
> Include empty .mvn/jvm.config and .mvn/maven.config in all archetypes
> ---------------------------------------------------------------------
>
> Key: MARCHETYPES-72
> URL: https://issues.apache.org/jira/browse/MARCHETYPES-72
> Project: Maven Archetype Bundles
> Issue Type: Improvement
> Reporter: Maarten Mulders
> Priority: Minor
>
> All [Maven archetypes|https://maven.apache.org/archetypes/index.html] should generate two empty files in the *.mvn* folder of the generated project: *jvm.config* and *maven.config*.
> There are two reasons for this:
> # This points users to the fact that they can use those files to customise their build.
> # If the project is a multi-module project or is later converted to a multi-module project, Maven will be able to reliably determine the root of that multi-module project.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)