Hi Martin, On Sat, Dec 6, 2025 at 7:24 PM Martin Honnen <[email protected]> wrote: > It seems in the recent commits there has been a change in the main POM's > dependencies, namely from > > <dependency> > <groupId>org.apache.xsl</groupId> > <artifactId>xpath31_types</artifactId> > <version>1.0</version> > </dependency> > > to > > <dependency> > <groupId>xerces</groupId> > <artifactId>xalanj_xpath31_types</artifactId> > <version>0.1</version> > </dependency> > > With that change my attempt to do a Maven clean install I get an > unresolved dependency for that xalanj_xpath31_types
There were few changes to Xalan-J's XSL 3 xpath31_types project, within previous few days. This project was also converted to a Maven build. The project xalan-j_xslt3.0_mvn was also modified accordingly. I think, a simple git pull would have fixed everything for anyone fetching code from Xalan-J's code branch xalan-j_xslt3.0_mvn. You may try removing the previous org.apache.xsl xpath31_types Maven artifact on your local, manually (I think, it'll be available somewhere within the local Maven .m2 folder), and then do Maven clean install. That should fix these issues on local, I think. -- Regards, Mukul Gandhi
