[
https://issues.apache.org/jira/browse/MSOURCES-23?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17959401#comment-17959401
]
Matthias Bünger commented on MSOURCES-23:
-----------------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-source-plugin#105|https://github.com/apache/maven-source-plugin/issues/105].
> test-jar misses sources from "generate-test-sources" phase
> ----------------------------------------------------------
>
> Key: MSOURCES-23
> URL: https://issues.apache.org/jira/browse/MSOURCES-23
> Project: Maven Source Plugin (Moved to GitHub Issues)
> Issue Type: Improvement
> Affects Versions: 2.0.3
> Environment: Maven 2.0.7
> Reporter: Benjamin Bentmann
> Assignee: Olivier Lamy
> Priority: Minor
> Fix For: 2.2
>
>
> When the goal source:test-jar is run directly from the command-line, the
> plugin will miss source files that get generated during the
> "generate-test-sources" phase as the mojo currently only requires the
> "generate-sources" phase.
> Though simply increasing the mojos lifecycle requirement would solve the
> problem, it kind of looks ugly to have the lengthy and potentially failing
> "compile" phase get run just to package test sources (first time I realize
> practical limitations of Maven's simple waterfall lifecycle compared to
> partially ordered goals...). An additional mojo like "generated-test-jar"
> might therefore be the best solution to keep the majority of use-cases fast
> but support the more sophisticated cases as well.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
