Maven is a pretty standard way of deploying 3rd party libraries in the Java ecosystem. Supporting it is a no-brainer. It's fundamental for modern development.
- Jim On 5/11/18 10:52 AM, Eric J. Schwarzenbach wrote: > > How do you figure I missed your point? I simply added to Mukul > Gandhi's list of ways of getting maven artifacts with another way (or > I suppose an elaboration of his #2). > > On 05/10/2018 05:53 PM, dbrosIus 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. >> >> -------- Original message -------- >> From: "Eric J. Schwarzenbach" <eric.schwarzenb...@wrycan.com> >> Date: 5/10/18 5:28 PM (GMT-05:00) >> To: j-users@xerces.apache.org >> Subject: Re: [ANNOUNCEMENT]: Apache Xerces-J 2.12.0 now available >> >> >> On 05/10/2018 02:39 AM, Mukul Gandhi wrote: >>> Hi Dave, >>> >>> On Thu, May 10, 2018 at 11:23 AM, Dave Brosius >>> <dbros...@mebigfatguy.com <mailto: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. >>> >> Your company can also run its own maven repo server (such as Nexus), >> that can hold both your company's internal maven artifacts and proxy >> to external maven repos like maven central. Then when you need a 3rd >> party artifact that is not in maven central, you can simply load it >> once to this repo and none of your developers need to do anything. > -- Jim Manico Manicode Security https://www.manicode.com
