Folks, it took us 7 years and 5 months to get a new release out. I would hope that alone would make it evident that this project needs more help from the community if it's going to keep moving forward.
I see at least a few people feel strongly about Maven and would encourage them to contribute. The same goes for anything else you feel passionate about seeing implemented of fixed in Xerces. Thanks. Michael Glavassevich XML Technologies and WAS Development IBM Toronto Lab E-mail: mrgla...@ca.ibm.com E-mail: mrgla...@apache.org Mukul Gandhi <muk...@apache.org> wrote on 05/10/2018 02:39:32 AM: > Hi Dave, > > On Thu, May 10, 2018 at 11:23 AM, Dave Brosius <dbros...@mebigfatguy.com > > wrote: > Yes, but if i want to publish an artifact to maven, and my artifact > depends on xerces, are you expecting all the users of my artifact to > do the same? And if someone else creates an artifact based on my > artifact, etc, etc.? > As far as I know, Maven provides following ways to fetch build dependencies: > > 1) Get dependencies from a global Maven repository. This requires a > connection to internet. Some environments prohibit an internet > connection. Also on slow internet connections, getting tons of > artifacts from the global Maven repository during the build may be difficult. > 2) Get dependencies from a Maven repository on an Intranet server. > 3) Get dependencies from a Maven repository on the local host. > > You & people in favor of your point seems to say that 1) above is > the best/only method. But clearly, 2) is also another method. Of > course, 3) above is also yet another method for fetching Maven dependencies. > > -- > Regards, > Mukul Gandhi
