css4j / css4j-dom4j Goto Github PK

If a requires xpp3 is put in the module-info for this project, the following error happens:

module io.sf.carte.css4j.dom4j reads package javax.xml.namespace from both xpp3 and java.xml

(and other similar ones).

Currently, the css4j-dom4j module ships with a workaround for this, but it may cause problems for users. One possibility would be to use an artifact from the xmlpull-xpp3 project which recently tagged a release but they did not deploy their artifact.

In case that the users of this library find that it would be better for them to depend on a more recent XPP3 artifact (even if it is not at a Maven repository), this issue is opened to receive that feedback.

Hi Carlos,

Thanks for the release.

I've tried to upgrade to CSS4J 3.5.0 (from v3.2.0) and it's failing because the xpp3_min dep has been moved from an optional dep to a runtime mandatory one.

See https://css4j.github.io/maven/io/sf/carte/css4j-dom4j/3.4.0/css4j-dom4j-3.4.0.pom vs https://css4j.github.io/maven/io/sf/carte/css4j-dom4j/3.5.0/css4j-dom4j-3.5.0.pom

The XWiki build is now complaining with:

[INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-upper-bounds) @ xwiki-platform-oldcore ---
[WARNING] Rule 0: org.apache.maven.plugins.enforcer.RequireUpperBoundDeps failed with message:
Failed while enforcing RequireUpperBoundDeps. The error(s) are [
Require upper bound dependencies error for xpp3:xpp3_min:1.1.4c paths to dependency are:
+-org.xwiki.platform:xwiki-platform-oldcore:13.5-SNAPSHOT
  +-io.sf.carte:css4j-dom4j:3.5.0
    +-xpp3:xpp3_min:1.1.4c (managed) <-- xpp3:xpp3_min:1.2.0
]

Note that there doesn't seem to be an official xpp3 1.2.0 release so we're a bit hesitant to upgrade. In addition so far we've not bundled xpp3 at all in our XWiki WAR and we prefer to avoid that as much as possible, if possible.

Could you tell me if that change in the pom is voluntary (and if so what forced you to do that) or if it's just a bug/side effect of moving to Gradle?

Thanks a lot
-Vincent