Details
-
Type:
Improvement
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 2.0.3
-
Fix Version/s: 2.1
-
Labels:None
-
Environment:ALL
-
Patch Submitted:Yes
-
Number of attachments :
Description
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.
Issue Links
- is duplicated by
-
MSOURCES-31
forking lifecycle of source:jar goal results in release-plugin error
-
-
MSOURCES-37
CLONE -maven-source-plugin causes generate-sources phase to execute twice
-
- relates to
-
MSOURCES-8
maven-source-plugin causes generate-sources phase to execute twice
-
-
MSOURCES-57
jar-no-fork should be changed to something more meaningful
-
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!