[jira] [Closed] (MSOURCES-24) jar misses resources from "generate-resources" phase

["Michael Osipov (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/MSOURCES-24?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Osipov closed MSOURCES-24.
----------------------------------
    Resolution: Auto Closed

This issue has been auto closed because it has been inactive for a long period of time. If you think this issue still applies, retest your problem with the most recent version of Maven and the affected component, reopen and post your results.

> jar misses resources from "generate-resources" phase
> ----------------------------------------------------
>
>                 Key: MSOURCES-24
>                 URL: https://issues.apache.org/jira/browse/MSOURCES-24
>             Project: Maven 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 was sent by Atlassian JIRA
(v6.3.4#6332)