ppkarwasz commented on issue #3255: URL: https://github.com/apache/logging-log4j2/issues/3255#issuecomment-2508871764
I think we are talking about the Maven `sources` artifact. That one has even less requirements: it is not a complete source file, so you can not build the binary artifact using it. It is mostly used by IDEs to show you the source of external libraries. Currently it contains some generated code/resources: - The code generated by annotation processors in `target/generated-sources/annotations` ends up in the `source` JAR and is also used by the compiler. - The resources generated in `target/maven-shared-archive-resources` end up in the `source` JAR and the binary JAR. Even if we do decompile `module-info.class`, I can not find a mechanism in the Maven Source Plugin that would allow us to add the file to the `source` JAR, without it ending up also in the binary JAR or on the compiler classpath. Solving this feature request will probably need: - Changes to the Maven Source Plugin. - Changes to the BND Maven Plugin. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
