Hello Alexander, It sounds like your build does not set a version for xalan:xalan, in which case your build system might be choosing for you to use whatever is the latest version.
Gary On Sun, May 14, 2023, 08:38 Tarnopolsky, Alexander <alexander.tarnopol...@aspentech.com.invalid> wrote: > Dear xalan contributors, > > > > Our legacy code depends on xalan 2.7.2 and since the update on Maven > Central our builds fail: > > > > Anting /users/gdadmin/2022hf/project/src/library/Drilling/Interop/build > > /users/gdadmin/2022hf/project/toolworks/JDK/jdk-17.0.1/linux/bin/java \ > > > -Dant.home=/users/gdadmin/2022hf/project/toolworks/ANT/apache-ant-1.10.7 > -classpath \ > > > /users/gdadmin/2022hf/project/toolworks/ANT/apache-ant-1.10.7/lib/ant-launcher.jar > \ > > org.apache.tools.ant.launch.Launcher > > Buildfile: > /users/gdadmin/2022hf/project/src/library/Drilling/Interop/build/build.xml > > [resolver:resolve] Downloading > https://repo1.maven.org/maven2/commons-lang/commons-lang/maven-metadata.xml > > [resolver:resolve] Downloaded > https://repo1.maven.org/maven2/commons-lang/commons-lang/maven-metadata.xml > (646 B \ > > at 0.6 KB/sec) > > [resolver:resolve] Downloading > https://repo1.maven.org/maven2/com/toedter/jcalendar/maven-metadata.xml > > [resolver:resolve] Downloaded > https://repo1.maven.org/maven2/com/toedter/jcalendar/maven-metadata.xml > (435 B at \ > > 2.0 KB/sec) > > [resolver:resolve] Downloading > https://repo1.maven.org/maven2/com/miglayout/miglayout/maven-metadata.xml > > [resolver:resolve] Downloaded > https://repo1.maven.org/maven2/com/miglayout/miglayout/maven-metadata.xml > (689 B at \ > > 4.4 KB/sec) > > [resolver:resolve] Downloading > https://repo1.maven.org/maven2/xalan/xalan/maven-metadata.xml > > [resolver:resolve] Downloaded > https://repo1.maven.org/maven2/xalan/xalan/maven-metadata.xml (317 B at > 2.1 KB/sec) > > [resolver:resolve] Downloading \ > > > https://repo1.maven.org/maven2/commons-collections/commons-collections/maven-metadata.xml > > [resolver:resolve] Downloaded \ > > > https://repo1.maven.org/maven2/commons-collections/commons-collections/maven-metadata.xml > (934 B at 5.0 KB/sec) > > [resolver:resolve] Downloading > https://repo1.maven.org/maven2/commons-digester/commons-digester/maven-metadata.xml > > [resolver:resolve] Downloaded > https://repo1.maven.org/maven2/commons-digester/commons-digester/maven-metadata.xml > \ > > (619 B at 4.0 KB/sec) > > > > BUILD FAILED > > > > /users/gdadmin/2022hf/project/src/library/Drilling/Interop/build/build.xml:27: > The following error occurred while \ > > executing this line: > > /users/gdadmin/2022hf/project/src/library/Drilling/Interop/build/include.xml:14: > Could not collect dependencies: \ > > Failed to collect dependencies at xalan:xalan:jar:[2.7.2] > > Total time: 6 seconds > > > > > > > > The previous version of maven-metadata.xml contained declaration of > several versions, including 2.7.2. > > Now with the release of 2.7.3, olny the 2.7.3 appear in the > https://repo1.maven.org/maven2/xalan/xalan/maven-metadata.xml > > Also, the depencency on serializer and xerces is no longer listed in > https://repo1.maven.org/maven2/xalan/xalan/2.7.3/xalan-2.7.3.pom > > > > Are those changes intentional? > > Is there a way for us to keep using xalan 2.7.2 in our release branches? > > Thanks, > Alexander Tarnopolsky > GSS_Team Lead, Dev Ops | Aspen Technology, Inc. > work: +972 99709624 | www.aspentech.com > > > > >
