kriegaex commented on PR #124: URL: https://github.com/apache/xalan-java/pull/124#issuecomment-1818085292
Can we please refrain from comparing Gradle to Maven? Some people love Gradle, others favour Maven, but that is not the point. We are in a Maven context here, therefore both Gradle advertising and Maven bashing are not solving any problem. Joe asked for help about Maven on the users mailing list, so I tried to lend a hand. If he has asked about Gradle, I would not be here. Vladimir, if you want to help with the Maven build, you are welcome. If you just want to spit into the soup and urge us to use Gradle instead, please stay away. Back to Maven: Maven **is** dependency-driven, but it revolves around dependendies between **modules**, not build tasks. Knowing that and knowing how to handle it, maybe throwing in a few flags and/or profiles, helps to solve most problems quite easily. Joe, that you deliberately decided to create javadocs only in the `site` lifecycle does not mean you cannot or should not create javadocs per module, which is actually the standard. If you want to deploy to Maven Central, nowadays each module requires javadoc and sources JARs on top of the binary JAR by default, so you want to configure Maven accordingly. You still can skip costly build steps with flags or profiles. I can help with all of that. -- 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: dev-unsubscr...@xalan.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
