You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Dennis Lundberg (JIRA)" <ji...@codehaus.org> on 2007/11/03 23:05:10 UTC

[jira] Updated: (MSOURCES-13) No-Forking mojos for use within a POM instead of CLI

     [ http://jira.codehaus.org/browse/MSOURCES-13?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dennis Lundberg updated MSOURCES-13:
------------------------------------

    Affects Version/s: 2.0.3
        Fix Version/s: 2.1

> 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 Source Plugin
>          Issue Type: Improvement
>    Affects Versions: 2.0.3
>         Environment: ALL
>            Reporter: Ben Tatham
>             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: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira