[
https://issues.apache.org/jira/browse/XERCESJ-1800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18139670#comment-18139670
]
Elliotte Rusty Harold commented on XERCESJ-1800:
------------------------------------------------
It looks like the issue is when the test class is in org.apahe.xerces. Most
existing test classes aren't but copilot flagged this on a new test that is.
> Tests included in production. jar?
> ----------------------------------
>
> Key: XERCESJ-1800
> URL: https://issues.apache.org/jira/browse/XERCESJ-1800
> Project: Xerces2-J
> Issue Type: Bug
> Reporter: Elliotte Rusty Harold
> Priority: Critical
>
> Copilot thinks we're including tests in the production jar:
> Putting this test in the production package causes it to be shipped in
> xercesImpl.jar when packaging after tests (for example, ant test jar). The
> tests target compiles into ${build.dest} (build.xml:374–375), and the jar
> target packages org/apache/** from that same directory (build.xml:333–336),
> including this JUnit-dependent class. Move the test to a package outside the
> production include patterns and update its batch-test entry, or explicitly
> exclude test classes from the production jars.
> I'm not sure this is true but if it is it needs to be fixed
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
