You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Paul Gier (JIRA)" <ji...@codehaus.org> on 2009/04/09 00:02:19 UTC

[jira] Closed: (MSOURCES-28) No test for up todate/no ablity to exclude pom.properties from resulting jar

     [ http://jira.codehaus.org/browse/MSOURCES-28?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Paul Gier closed MSOURCES-28.
-----------------------------

    Resolution: Fixed

Added a forceCreation parameter similar to the jar plugin.

> No test for up todate/no ablity to exclude pom.properties from resulting jar
> ----------------------------------------------------------------------------
>
>                 Key: MSOURCES-28
>                 URL: http://jira.codehaus.org/browse/MSOURCES-28
>             Project: Maven 2.x Source Plugin
>          Issue Type: Bug
>    Affects Versions: 2.0.3
>         Environment: Windows **
>            Reporter: EJ Ciramella
>            Assignee: Paul Gier
>             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 is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira