maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul Gier (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (MSOURCES-13) No-Forking mojos for use within a POM instead of CLI
Date Fri, 29 May 2009 13:10:42 GMT

    [ http://jira.codehaus.org/browse/MSOURCES-13?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=178588#action_178588
] 

Paul Gier commented on MSOURCES-13:
-----------------------------------

Did you change the goal from "jar" to "[jar-no-fork|http://maven.apache.org/plugins/maven-source-plugin/]"?

> 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
>            Assignee: Paul Gier
>             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 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

        

Mime
View raw message