I decided instead of publishing multiple artifacts, to set up profiles so that builds which use earlier versions generate and install artifacts with classifiers ‘jdk8’ or ‘jdk11’.
Steve On Jan 11, 2024 at 10:37 AM -0600, Steve Blackmon <sblack...@apache.org>, wrote: > Hi team, > > I'm getting starting on a release now and considering whether to change our > release process to publish jars for multiple jdk versions. We have profiles > now for building with JDK8, JDK11, and JDK17. > > I think its appropriate for a our primary artifact to be built with JDK17. > Although JDK8 is technically obsolete it is still widely used. Acknowledging > that these are convenience binaries and users are free to build the project > however they want, what do we think about publishing the primary artifact > built with JDK17 and also publishing jar artifacts built with JDK8 and JDK11 > with classifiers applied? > > Has anyone seen a better pattern for making it easy for cutting-edge and > legacy JVMs to import artifacts direct from central? > > Steve > >
