maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bob Fields (JIRA)" <>
Subject [jira] Commented: (MSOURCES-13) No-Forking mojos for use within a POM instead of CLI
Date Wed, 16 Feb 2011 16:22:22 GMT


Bob Fields commented on MSOURCES-13:

Still an issue with plugin version 2.1.2 and maven 2.2.1: If the maven-source-plugin is declared
as a <plugin> in a parent pom, generate-sources is executed multiple times in all children,
actually causing an infinite loop in our case (MDA code generator project). If declared as
<pluginManagement> and referenced in all child projects, it is only executed once. I
was using jar-no-fork and test-jar-no-fork. This is an annoyance (we have about a hundred
children) but manageable.

> No-Forking mojos for use within a POM instead of CLI
> ----------------------------------------------------
>                 Key: MSOURCES-13
>                 URL:
>             Project: Maven 2.x Source Plugin
>          Issue Type: Improvement
>    Affects Versions: 2.0.3
>         Environment: ALL
>            Reporter: Ben Tatham
>            Assignee: Paul Gier
>             Fix For: 2.1
>         Attachments: nofork.patch, nofork.patch,
> The exiting jar at test-jar mojos will always cause a lifecycle fork and generate-sources.
 This can cause all kinds of undesired side effects when using the source plugin with a pom,
instead of CLI.  I propose a simple fix (patch attached) to extend these two mojos in no-forking
mode.  I can't think of a better name for them.  
> This behaviour is similar to the difference between assembly:assembly and assembly:attached.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message