Re: [ANNOUNCEMENT]: Apache Xerces-J 2.12.0 now available
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" >> 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 >>> 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
Re: [ANNOUNCEMENT]: Apache Xerces-J 2.12.0 now available
I give up. You win. On 05/11/2018 04:52 PM, 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" 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 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.
Re: [ANNOUNCEMENT]: Apache Xerces-J 2.12.0 now available
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" 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 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.
Re: [ANNOUNCEMENT]: Apache Xerces-J 2.12.0 now available
On Fri, May 11, 2018 at 3:23 AM, 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. > 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, Note that this document describes how to release Maven artifacts. *These are optional*.. -- Regards, Mukul Gandhi
Re: [ANNOUNCEMENT]: Apache Xerces-J 2.12.0 now available
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" 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 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.
Re: [ANNOUNCEMENT]: Apache Xerces-J 2.12.0 now available
For Apache Commons, how well did that work for improving activity? Michael Glavassevich XML Technologies and WAS Development IBM Toronto Lab E-mail: mrgla...@ca.ibm.com E-mail: mrgla...@apache.org Dave Brosius wrote on 05/10/2018 05:15:22 PM: > From: Dave Brosius > To: j-users@xerces.apache.org > Date: 05/10/2018 05:16 PM > Subject: Re: [ANNOUNCEMENT]: Apache Xerces-J 2.12.0 now available > > What Apache Commons did, in a similar circumstance was unilaterally > open up committership to all commons projects to a much wider > audience. Perhaps Xerces should consider doing that as well. > > On 05/10/2018 01:48 PM, Michael Glavassevich wrote: > 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 wrote on 05/10/2018 02:39:32 AM: > > > Hi Dave, > > > > On Thu, May 10, 2018 at 11:23 AM, Dave Brosius > > 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 bedifficult. > > 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
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 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.
Re: [ANNOUNCEMENT]: Apache Xerces-J 2.12.0 now available
What Apache Commons did, in a similar circumstance was unilaterally open up committership to all commons projects to a much wider audience. Perhaps Xerces should consider doing that as well. On 05/10/2018 01:48 PM, Michael Glavassevich wrote: 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 wrote on 05/10/2018 02:39:32 AM: > Hi Dave, > > On Thu, May 10, 2018 at 11:23 AM, Dave Brosius > 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
Re: [ANNOUNCEMENT]: Apache Xerces-J 2.12.0 now available
Oops, typo: implemented of fixed in Xerces --> implemented or fixed in Xerces. Michael Glavassevich XML Technologies and WAS Development IBM Toronto Lab E-mail: mrgla...@ca.ibm.com E-mail: mrgla...@apache.org "Michael Glavassevich" wrote on 05/10/2018 01:48:52 PM: > From: "Michael Glavassevich" > To: j-users@xerces.apache.org > Cc: j-...@xerces.apache.org > Date: 05/10/2018 01:49 PM > Subject: Re: [ANNOUNCEMENT]: Apache Xerces-J 2.12.0 now available > > 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 wrote on 05/10/2018 02:39:32 AM: > > > Hi Dave, > > > > On Thu, May 10, 2018 at 11:23 AM, Dave Brosius > > 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 bedifficult. > > 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
Re: [ANNOUNCEMENT]: Apache Xerces-J 2.12.0 now available
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 wrote on 05/10/2018 02:39:32 AM: > Hi Dave, > > On Thu, May 10, 2018 at 11:23 AM, Dave Brosius > 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
Re: [ANNOUNCEMENT]: Apache Xerces-J 2.12.0 now available
Hi Dave, On Thu, May 10, 2018 at 11:23 AM, Dave Brosius 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
Re: [ANNOUNCEMENT]: Apache Xerces-J 2.12.0 now available
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.?
What's the problem with publishing to maven? All of Apache does it, so
far as i'm aware (ok so TIL not _all_ of apache does).. It's a solved
problem.
--dave
On 05/10/2018 01:17 AM, Mukul Gandhi wrote:
Hi Dave,
On Thu, May 10, 2018 at 5:43 AM, Dave Brosius
mailto:dbros...@mebigfatguy.com>> wrote:
Sorry it's 2018, that's just silly; maven, ivy, gradle, cobalt ...
all use the maven repository. I agree ... if it's not on maven, it
doesn't exist.
I think we're spreading FUD about using Xerces Jars within Maven. Lets
not do it.
I know very well about Maven and Gradle build systems. They both allow
having a local standalone Jar as part of Maven and Gradle builds
respectively. With Maven it can be done using the "mvn
install:install-file" command I referred in my previous mail. With
Gradle, it can be done via following syntax,
repositories {
flatDir {
dirs 'libs'
}
}
(a Jar needs to be simply available in a local "libs" folder, for
Gradle to pick it).
Any good java build system, ought to provide methods to have local
standalone Jars as part of builds.
--
Regards,
Mukul Gandhi
Re: [ANNOUNCEMENT]: Apache Xerces-J 2.12.0 now available
Hi Dave,
On Thu, May 10, 2018 at 5:43 AM, Dave Brosius
wrote:
> Sorry it's 2018, that's just silly; maven, ivy, gradle, cobalt ... all use
> the maven repository. I agree ... if it's not on maven, it doesn't exist.
>
I think we're spreading FUD about using Xerces Jars within Maven. Lets not
do it.
I know very well about Maven and Gradle build systems. They both allow
having a local standalone Jar as part of Maven and Gradle builds
respectively. With Maven it can be done using the "mvn
install:install-file" command I referred in my previous mail. With Gradle,
it can be done via following syntax,
repositories {
flatDir {
dirs 'libs'
}
}
(a Jar needs to be simply available in a local "libs" folder, for Gradle to
pick it).
Any good java build system, ought to provide methods to have local
standalone Jars as part of builds.
--
Regards,
Mukul Gandhi
Re: [ANNOUNCEMENT]: Apache Xerces-J 2.12.0 now available
Sorry it's 2018, that's just silly; maven, ivy, gradle, cobalt ... all use the maven repository. I agree ... if it's not on maven, it doesn't exist. On 05/09/2018 01:14 AM, Mukul Gandhi wrote: On Tue, May 8, 2018 at 7:58 PM, Gary Gregory mailto:ggreg...@rocketsoftware.com>> wrote: +1. If it’s not in Maven, it is not easily usable… I can say following with fully responsibility, Maven is conceptually just like any other build system (like ant for example). Till the time Xerces 2.12.0 jars are not in official public Maven repository, it should be possible to install Xerces 2.12.0 jars in the local Maven repository by users, and have Xerces jars function as Maven project dependencies. Following documentation, explains how to do this, https://maven.apache.org/guides/mini/guide-3rd-party-jars-local.html. -- Regards, Mukul Gandhi
Re: [ANNOUNCEMENT]: Apache Xerces-J 2.12.0 now available
On Tue, May 8, 2018 at 7:58 PM, Gary Gregory wrote: > +1. If it’s not in Maven, it is not easily usable… > I can say following with fully responsibility, Maven is conceptually just like any other build system (like ant for example). Till the time Xerces 2.12.0 jars are not in official public Maven repository, it should be possible to install Xerces 2.12.0 jars in the local Maven repository by users, and have Xerces jars function as Maven project dependencies. Following documentation, explains how to do this, https://maven.apache.org/guides/mini/guide-3rd-party-jars-local.html. -- Regards, Mukul Gandhi
Re: [ANNOUNCEMENT]: Apache Xerces-J 2.12.0 now available
I believe they got uploaded by other ASF committers / members so they're official in that sense. It just wasn't done by Xerces developers. There was no policy decision. It's more of a motivation issue. The developers (past and present) haven't shown much interest in Maven. Of course anyone interested is welcome to drive it. Just needs a volunteer to do the work. Thanks. Michael Glavassevich XML Technologies and WAS Development IBM Toronto Lab E-mail: mrgla...@ca.ibm.com E-mail: mrgla...@apache.org "Mark H. Wood" wrote on 05/08/2018 09:22:07 AM: > From: "Mark H. Wood" > To: j-users@xerces.apache.org > Date: 05/08/2018 09:22 AM > Subject: Re: [ANNOUNCEMENT]: Apache Xerces-J 2.12.0 now available > > On Tue, May 08, 2018 at 10:59:09AM +0530, Mukul Gandhi wrote: > > On Tue, May 8, 2018 at 6:19 AM, Dave Brosius wrote: > > > > > > xercesImpl.jar has still yet to show up on maven central, was this an > > > oversight? > > > > > Michael Glavassevich, replied to a question on same topic on list > > j-...@xerces.apache.org a while ago as follows, > > > > "Maven has never been part of our release process. Other people from the > > community would have uploaded those previous releases." > > > > I hope that could answer the question. > > Interesting that someone in the community has been sending up various > artifacts under the groupId "xerces" since 2005. It certainly > *looked* official. How disappointing. > > Was there a policy decision not to release Maven artifacts, or does it > just need someone to do the work? I could do the work. But I don't > want to perpetrate yet-another-confusing-unofficial-release. > > -- > Mark H. Wood > Lead Technology Analyst > > University Library > Indiana University - Purdue University Indianapolis > 755 W. Michigan Street > Indianapolis, IN 46202 > 317-274-0749 > www.ulib.iupui.edu
RE: [ANNOUNCEMENT]: Apache Xerces-J 2.12.0 now available
+1. If it's not in Maven, it is not easily usable... Gary From: Bernd Eckenfels [mailto:e...@zusammenkunft.net] Sent: Tuesday, May 8, 2018 05:13 To: j-users@xerces.apache.org Subject: Re: [ANNOUNCEMENT]: Apache Xerces-J 2.12.0 now available Hello, Can this process be changed? What is not on central does virtually not exist and the ASF should have a interest in a clean Apache group repo. The official ASF repo is automatically synced to maven central, so it just needs publishing to the nexus repo. This is especially easy as it allows staging so it is also good for the review process. http://www.apache.org/dev/publishing-maven-artifacts.html Yes binaries are not officially part of an ASF release even though they are effectively the main thing (our) users need. Allowing community without a fixed process in this critical part of the software chain looks dangerous to me. Gruss Bernd -- http://bernd.eckenfels.net From: Mukul Gandhi mailto:muk...@apache.org>> Sent: Tuesday, May 8, 2018 7:29:09 AM To: j-users@xerces.apache.org<mailto:j-users@xerces.apache.org> Subject: Re: [ANNOUNCEMENT]: Apache Xerces-J 2.12.0 now available Hi Dave, On Tue, May 8, 2018 at 6:19 AM, Dave Brosius mailto:dbros...@apache.org>> wrote: xercesImpl.jar has still yet to show up on maven central, was this an oversight? Michael Glavassevich, replied to a question on same topic on list j-...@xerces.apache.org<mailto:j-...@xerces.apache.org> a while ago as follows, "Maven has never been part of our release process. Other people from the community would have uploaded those previous releases." I hope that could answer the question. -- Regards, Mukul Gandhi Rocket Software, Inc. and subsidiaries ? 77 Fourth Avenue, Waltham MA 02451 ? Main Office Toll Free Number: +1 855.577.4323 Contact Customer Support: https://my.rocketsoftware.com/RocketCommunity/RCEmailSupport Unsubscribe from Marketing Messages/Manage Your Subscription Preferences - http://www.rocketsoftware.com/manage-your-email-preferences Privacy Policy - http://www.rocketsoftware.com/company/legal/privacy-policy This communication and any attachments may contain confidential information of Rocket Software, Inc. All unauthorized use, disclosure or distribution is prohibited. If you are not the intended recipient, please notify Rocket Software immediately and destroy all copies of this communication. Thank you.
Re: [ANNOUNCEMENT]: Apache Xerces-J 2.12.0 now available
On Tue, May 08, 2018 at 10:59:09AM +0530, Mukul Gandhi wrote: > On Tue, May 8, 2018 at 6:19 AM, Dave Brosius wrote: > > > > xercesImpl.jar has still yet to show up on maven central, was this an > > oversight? > > > Michael Glavassevich, replied to a question on same topic on list > j-...@xerces.apache.org a while ago as follows, > > "Maven has never been part of our release process. Other people from the > community would have uploaded those previous releases." > > I hope that could answer the question. Interesting that someone in the community has been sending up various artifacts under the groupId "xerces" since 2005. It certainly *looked* official. How disappointing. Was there a policy decision not to release Maven artifacts, or does it just need someone to do the work? I could do the work. But I don't want to perpetrate yet-another-confusing-unofficial-release. -- Mark H. Wood Lead Technology Analyst University Library Indiana University - Purdue University Indianapolis 755 W. Michigan Street Indianapolis, IN 46202 317-274-0749 www.ulib.iupui.edu signature.asc Description: PGP signature
Re: [ANNOUNCEMENT]: Apache Xerces-J 2.12.0 now available
Hello, Can this process be changed? What is not on central does virtually not exist and the ASF should have a interest in a clean Apache group repo. The official ASF repo is automatically synced to maven central, so it just needs publishing to the nexus repo. This is especially easy as it allows staging so it is also good for the review process. http://www.apache.org/dev/publishing-maven-artifacts.html Yes binaries are not officially part of an ASF release even though they are effectively the main thing (our) users need. Allowing community without a fixed process in this critical part of the software chain looks dangerous to me. Gruss Bernd -- http://bernd.eckenfels.net From: Mukul Gandhi Sent: Tuesday, May 8, 2018 7:29:09 AM To: j-users@xerces.apache.org Subject: Re: [ANNOUNCEMENT]: Apache Xerces-J 2.12.0 now available Hi Dave, On Tue, May 8, 2018 at 6:19 AM, Dave Brosius mailto:dbros...@apache.org>> wrote: xercesImpl.jar has still yet to show up on maven central, was this an oversight? Michael Glavassevich, replied to a question on same topic on list j-...@xerces.apache.org<mailto:j-...@xerces.apache.org> a while ago as follows, "Maven has never been part of our release process. Other people from the community would have uploaded those previous releases." I hope that could answer the question. -- Regards, Mukul Gandhi
Re: [ANNOUNCEMENT]: Apache Xerces-J 2.12.0 now available
Hi Dave, On Tue, May 8, 2018 at 6:19 AM, Dave Brosius wrote: > > xercesImpl.jar has still yet to show up on maven central, was this an > oversight? > Michael Glavassevich, replied to a question on same topic on list j-...@xerces.apache.org a while ago as follows, "Maven has never been part of our release process. Other people from the community would have uploaded those previous releases." I hope that could answer the question. -- Regards, Mukul Gandhi
Re: [ANNOUNCEMENT]: Apache Xerces-J 2.12.0 now available
Hi Folks, xercesImpl.jar has still yet to show up on maven central, was this an oversight? --dave On 05/02/2018 11:59 PM, Mukul Gandhi wrote: Hi all, The Apache Xerces project team is pleased to announce that version 2.12.0 of Apache Xerces-J is now available. Xerces-J 2.12.0 can be downloaded at: http://xerces.apache.org/mirrors.cgi. This release expands on Xerces-J's experimental support for XML Schema 1.1 by providing a fully compliant XML Schema 1.1 implementation. It fixes several bugs which were present in Xerces-J 2.11.0 and also includes a few other minor enhancements. Specifically, the changes introduced in this release are: * Report all id/idref problems when validating XML against DTD or XML Schema. [Michael Glavassevich] * Implemented improvements to XML Schema 1.1 CTA implementation and inheritable attributes. [Mukul Gandhi, Hiranya Jayathilaka] * Implemented improved error/warning message reporting for various XML Schema use cases. [Mukul Gandhi] * Implemented few performance enhancements (affecting parsing/validation latency and memory footprint) to the implementation. [Michael Glavassevich] * Fixed minor bugs in Xerces-J's regex support in XML Schema facet. [Michael Glavassevich, Khaled Noaman, Sandy Gao] * Implemented various fixes to XML Schema 1.1 assert/assertion implementation. [Mukul Gandhi] * Implemented minor and major fixes in certain areas, to XML Schema 1.0 and 1.1 implementations. [Michael Glavassevich, Khaled Noaman, Sandy Gao, Mukul Gandhi] * Fixed the issue related to, XIncludeTextReader doesn't handle null Content Types properly. [Michael Glavassevich] * Fixed minor problems in the DOM (Level 3 Core) implementation. [Michael Glavassevich] * Fixed few errors related to Xerces-J's build component. [Michael Glavassevich] * Solved a minor bug in SoftReferenceSymbolTable implementation component. [Michael Glavassevich] * Octavian and Radu, from Oxygen XML Editor team have contributed much by way of intimating numerous bugs and implementation ideas, for Xerces-J's XML Schema 1.0 and 1.1 implementations. [Octavian Nadolu, Radu Coravu] * The following security issues, raised by users were fixed: CVE-2012-0881 : https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2012-0881 CVE-2013-4002 : https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-4002 CVE-2018-2799 : https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-2799 A complete list of JIRA issues resolved in this release is available here: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10520&version=12336542 For more information please visit: http://xerces.apache.org/xerces2-j/ -- Regards, Mukul Gandhi
