[
https://issues.apache.org/jira/browse/MSOURCES-28?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17959393#comment-17959393
]
Matthias Bünger commented on MSOURCES-28:
-----------------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-source-plugin#111|https://github.com/apache/maven-source-plugin/issues/111].
> No test for up todate/no ablity to exclude pom.properties from resulting jar
> ----------------------------------------------------------------------------
>
> Key: MSOURCES-28
> URL: https://issues.apache.org/jira/browse/MSOURCES-28
> Project: Maven Source Plugin (Moved to GitHub Issues)
> Issue Type: Bug
> Affects Versions: 2.0.3
> Environment: Windows **
> Reporter: EJ Ciramella
> Assignee: Paul Gier
> Priority: Major
> Fix For: 2.1
>
>
> Every time a module builds, and this plugin is configured, it builds a new
> source jar even though nothing has changed.
> Is there no uptodate check as the regular jarring mechanism? And if there
> is, is there no way to exclude the pom.properties file that gets created
> every time?
> (see here: http://jira.codehaus.org/browse/MJAR-7)
> With as many modules as we have, this adds a considerable amount of time.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
