maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stéphane Nicoll (JIRA) <>
Subject [jira] (MSOURCES-56) Parameter to skip the generation of the sources jar
Date Sat, 04 Aug 2012 10:22:21 GMT


Stéphane Nicoll commented on MSOURCES-56:

For the record, a skip parameter was added but it's not automatic, you have to configure it
> Parameter to skip the generation of the sources jar
> ---------------------------------------------------
>                 Key: MSOURCES-56
>                 URL:
>             Project: Maven 2.x Source Plugin
>          Issue Type: New Feature
>    Affects Versions: 2.0, 2.0.1, 2.0.2, 2.0.3, 2.0.4, 2.1, 2.1.1, 2.1.2
>            Reporter: Dieter König
>            Assignee: Olivier Lamy
>             Fix For: 2.2
> Generation of sources-jar should be automatically skipped when no sources were found.
> ###########
> Just in the same way as javadoc-plugin does!
> ###########
> For example if the sources- (default: src/main/java, configured value should be taken
into account) and testsources-folder are missing then no sources-jar should be generated.
Also if the folders are there but no files in that folders are available the generation should
be skipped.
> In other words: don't generate a sources jar which contains only META-INF/MANIFEST.MF
with following content:
> Manifest-Version: 1.0
> Archiver-Version: Plexus Archiver
> Created-By: 11.0-b15 (Sun Microsystems Inc.)
> Reason:
> - Generated sources-jar for empty sources is useless
> - Generated sources-jar for empty sources spams the maven repository!
> - Generation of sources-jar "costs" expensive build time
> - explicit skipping of plugin (which is one of the features for 2.2-release) is annoying/would
be an expensive work as you have to go through all the pom's...
> If you are aware of old behaviour (someone could need the useless empty jars) then provide
the possibility to configure/enable the automatic skip behaviour.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message