On Fri, May 11, 2018 at 3:23 AM, dbrosIus <dbros...@baybroadband.net> wrote:
> You missed the point. If I publish an artifact to maven when my artifact > depends on xerces, my users will come at me with pitch forks. > I agree that its certainly useful to have Xerces jars in Maven central. One thing that worries me is following, Please look here: https://search.maven.org/#search%7Cga%7C1%7Cxerces how Xerces in the past has been made available in Maven central. Different organizations/individuals have uploaded Xerces to Maven central. It usually is confusing for users, to see various Xerces artifacts on Maven central from different sources. I also stick to the point, that if certain Xerces artifacts are not in Maven central, still Xerces can be used in Maven projects. Here's another idea on how to make it easier, Use the command "mvn install:install-file" to install Xerces jars locally in Maven, and then ask different users to copy the relevant folder tree (somewhere within .m2\repository) from your machine. This document, http://www.apache.org/dev/publishing-maven-artifacts.html on the topic "how to publish Maven artifacts at Apache" says on top, <quote>Note that this document describes how to release Maven artifacts. *These are optional*.</quote>. -- Regards, Mukul Gandhi
