[
https://issues.apache.org/jira/browse/MNG-7013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17227745#comment-17227745
]
Maarten Mulders commented on MNG-7013:
--------------------------------------
Then this may also be the reason why {{mvn archetype:generate}} writes a POM
that doesn't contain the {{<groupId>}} for official Maven plugins?
That's something I personally dislike (prefer to have that explicit rather than
implicit). As far as I'm concerned, we could reconsider this. But maybe there's
strong reasons why it was omitted in the first place?
> MavenXpp3Writer doesn't write plugin with groupId "org.apache.maven.plugins"
> ----------------------------------------------------------------------------
>
> Key: MNG-7013
> URL: https://issues.apache.org/jira/browse/MNG-7013
> Project: Maven
> Issue Type: Bug
> Components: Plugins and Lifecycle
> Affects Versions: 3.6.3
> Reporter: Carlos Matos
> Priority: Critical
>
> When writing a pom.xml, when I try to create a plugin with the groupId
> "org.apache.maven.plugins", this is ignored and the plugin is written without
> groupId in the pom.xml file. If I add a space at the end like:
> "org.apache.maven.plugins " it seems to work though.
>
> Here's some code to reproduce:
> {code:java}
> Model model = new Model();
> Writer writer = new FileWriter("pom.xml");
> Build build = new Build();
> List<Plugin> plugins = new ArrayList<>();
> Plugin mavenCompiler = new Plugin();
> mavenCompiler.setArtifactId("maven-compiler-plugin");
> mavenCompiler.setGroupId("org.apache.maven.plugins");
> mavenCompiler.setVersion("3.1");
> plugins.add(mavenCompiler);
> build.setPlugins(plugins);
> model.setName("test");
> model.setArtifactId("test");
> model.setModelVersion("4.0.0");
> model.setVersion("0.0.1");
> model.setGroupId("test");
> model.setBuild(build);
> new MavenXpp3Writer().write(writer, model);
> writer.close();
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
