On 06/12/2025 15:58, Mukul Gandhi wrote:
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.

I don't get it work, I wonder whether the directory structure is correct, the https://github.com/apache/xalan-java/blob/xalan-j_xslt3.0_mvn/pom.xml#L53 looks for xalanj_xpath31_types under group xerces, yet the library structure with the artifact is https://github.com/apache/xalan-java/tree/xalan-j_xslt3.0_mvn/libs/xerces/xpath31_types and not https://github.com/apache/xalan-java/tree/xalan-j_xslt3.0_mvn/libs/xerces/xalanj_xpath31_types.

My Maven installation that way doesn't find the pom or the jar to install it locally.

I have not much experience with the Maven directory structure, I have made various attempts to rename folders and/or files to all say xpath31_types or all say xalanj_xpath31_types but that is all doomed it appears as the checksum on the jar then fails.

Not sure how I can fix that, please let me know whether the inconsistency of having "xalan_xpath31_types" in the POM and a directory structure of libs/xerces/xpath31_types is intended and should work with Maven.


Reply via email to