>> I would not want it to be log4j-core-tests-3.0.0-SNAPSHOT.jar as that would not be understood to be a test jar.
If this artifact is intended for log4j only, consider skipping install/deploy. But then I wonder why there's a need for a module descriptor. If it is intended to be used by users of log4j for testing, this name does make sense to me, similar to spring-test. Robert On 22-6-2021 23:20:11, Ralph Goers <ralph.go...@dslextreme.com> wrote: > On Jun 22, 2021, at 11:16 AM, Robert Scholte wrote: > > If I understand correctly you want both log4j-core main classes and test > classes be distributed as modularized jars. > To me with JPMS you should move the modularized test-classes to a separate > Maven module as a first citizen artifact. > That should make it a lot easier. Robert, I have a question on the above. I am generating log4j-core-3.0.0-SNAPSHOT.jar and log4j-core-3.0.0-SNAPSHOT-tests.jar. If the source is left in log4j-core and I create a log4j-core-tests module what would I specify in the pom to get it to create the test jar as log4j-core-3.0.0-SNAPSHOT-tests.jar? I would not want it to be log4j-core-tests-3.0.0-SNAPSHOT.jar as that would not be understood to be a test jar. Ralph --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
