You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Dennis Lundberg (JIRA)" <ji...@codehaus.org> on 2009/02/25 00:04:19 UTC
[jira] Updated: (MSOURCES-24) jar misses resources from
"generate-resources" phase
[ http://jira.codehaus.org/browse/MSOURCES-24?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dennis Lundberg updated MSOURCES-24:
------------------------------------
Fix Version/s: (was: 2.1)
> jar misses resources from "generate-resources" phase
> ----------------------------------------------------
>
> Key: MSOURCES-24
> URL: http://jira.codehaus.org/browse/MSOURCES-24
> Project: Maven 2.x Source Plugin
> Issue Type: Improvement
> Affects Versions: 2.0.3
> Environment: Maven 2.0.7
> Reporter: Benjamin Bentmann
> Priority: Minor
>
> When the goal source:jar is run directly from the command-line, the plugin will miss resource files that get generated during the "generate-resources" phase as the mojo currently only requires the "generate-sources" phase.
> Increasing the lifecycle requirements of the mojo to "generate-resources" would also cause "process-sources" to get run. I cannot judge whether this would cause any harm to existing plugin users. One might further consider to increase the lifecycle requirement to "process-resources" so that both sources and resources are in a consistent state before being packaged.
> Taking [MSOURCES-22|http://jira.codehaus.org/browse/MSOURCES-22] into account, it might be advisable to separate the packaging of sources and resources into two distinct mojos. The first mojo would only package the (compile) source files and would therefore only require the "generate-/process-sources" phase. The second mojo would package the source files and the resources (similar to the current jar goal), requiring the phase "generate-/process-resources". In contrast to adding a configuration option to exclude resources, introducing a new mojo would allow to tune the lifecycle requirements, hopefully supporting more use-cases for the plugin.
--
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