You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While building with Maven 3.6, I encountered issues related to the type test-jar in the pom files. Replaging those type lines with tests solved the issue. You may find my patch proposal enclosed.
What issues does using the dependency type test-jar cause? I fail to understand how it would be more correct to use <classifier>tests</classifier> instead of <type>test-jar</type>?
My build was attempted within the automated Maven workflow in Debian, with the aim of packaging apfloat for Debian. By using <type>test-jar</type>, the submodules could not load the test jar and the issue was solved by using the classifier approach instead.
But if you don't meet this issue, I guess it is specific to the Debian packaging workflow and the patch I have written should not be used outside. The issue can thus be closed.
Hello,
While building with Maven 3.6, I encountered issues related to the type test-jar in the pom files. Replaging those type lines with tests solved the issue. You may find my patch proposal enclosed.
All the best,
Pierre
managing_test_dependency.txt
The text was updated successfully, but these errors were encountered: