[
https://issues.apache.org/jira/browse/MSOURCES-13?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17959382#comment-17959382
]
Matthias Bünger commented on MSOURCES-13:
-----------------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-source-plugin#89|https://github.com/apache/maven-source-plugin/issues/89].
> No-Forking mojos for use within a POM instead of CLI
> ----------------------------------------------------
>
> Key: MSOURCES-13
> URL: https://issues.apache.org/jira/browse/MSOURCES-13
> Project: Maven Source Plugin (Moved to GitHub Issues)
> Issue Type: Improvement
> Affects Versions: 2.0.3
> Environment: ALL
> Reporter: Ben Tatham
> Assignee: Paul Gier
> Priority: Major
> Fix For: 2.1
>
> Attachments: nofork.patch, nofork.patch,
> project-still-running-twice-generate-sources-phase.zip
>
>
> 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 was sent by Atlassian Jira
(v8.20.10#820010)
