[jira] [Comment Edited] (MNG-5940) Change the maven-source-plugin jar goal into jar-no-fork in Maven Super POM

["Florian Brunner (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MNG-5940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16491821#comment-16491821 ] 

Florian Brunner edited comment on MNG-5940 at 5/26/18 8:32 PM:
---------------------------------------------------------------

[~michael-o]: the release-profile should either be removed or this issue should be fixed.


was (Author: puce):
[~michael-o]: the release-profile should either be removed or this issue should be fixed as there seems to be no way to override this goal without getting two deployments.

> Change the maven-source-plugin jar goal into jar-no-fork in Maven Super POM
> ---------------------------------------------------------------------------
>
>                 Key: MNG-5940
>                 URL: https://issues.apache.org/jira/browse/MNG-5940
>             Project: Maven
>          Issue Type: Improvement
>          Components: core
>            Reporter: Karl Heinz Marbaise
>            Priority: Minor
>             Fix For: needing-scrub-3.4.0-fallout
>
>
> At the moment the {{maven-source-plugin:jar}} goal is defined in the Maven super pom:
> {code:xml}
>   <plugin>
>             <inherited>true</inherited>
>             <artifactId>maven-source-plugin</artifactId>
>             <executions>
>               <execution>
>                 <id>attach-sources</id>
>                 <goals>
>                   <goal>jar</goal>
>                 </goals>
>               </execution>
>             </executions>
>           </plugin>
> {code}
> where the goal of {{maven-source-plugin}} should be changed from {{jar}} into {{jar-no-fork}}, cause most of the time you need to override this behaviour.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)