You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Hudson (Jira)" <ji...@apache.org> on 2022/05/20 19:28:00 UTC

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=17540264#comment-17540264 ] 

Hudson commented on MARCHETYPES-72:
-----------------------------------

Build succeeded in Jenkins: Maven » Maven TLP » maven-archetypes » master #6

See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-archetypes/job/master/6/

> 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
>            Assignee: Maarten Mulders
>            Priority: Minor
>              Labels: up-for-grabs
>             Fix For: 1.5
>
>
> 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.20.7#820007)