[
http://jira.codehaus.org/browse/MSOURCES-13?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ben Tatham updated MSOURCES-13:
-------------------------------
Attachment: nofork.patch
My previous patch was a bit premature. This one actually does what it says. I
didn't realize that maven plugin javadoc annotations were inherited!
> No-Forking mojos for use within a POM instead of CLI
> ----------------------------------------------------
>
> Key: MSOURCES-13
> URL: http://jira.codehaus.org/browse/MSOURCES-13
> Project: Maven 2.x Sources Plugin
> Issue Type: Improvement
> Environment: ALL
> Reporter: Ben Tatham
> 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:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
