maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steinar Bang (JIRA)" <>
Subject [jira] Commented: (MSOURCES-13) No-Forking mojos for use within a POM instead of CLI
Date Sun, 13 Jan 2008 13:50:57 GMT


Steinar Bang commented on MSOURCES-13:

I was recently bitten by this bundle's forking behaviour:

My problem was that I used dependency:copy to copy in some artifacts (jar source attachments
into an eclipse source plugin), and then used antrun:run to rename some of the copied in files.
 Then dependency:copy was called two times more, putting artifacts in with their original

And then my two problems were:
 1. what caused the forking?
 2. what could I do to get a workaround?

The cause was this config to create source attachments for all jar and test jar projects in
the company super POM:

The workaround was moving all dependency:copy executions from the generate-sources phase to
the generate-resources phase (which isn't triggered by the forked maven-sources-plugins executions),
and of cours also move antrun:run from process-sources to process-resources.

> 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
>             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