Y.
On Wed, Jan 8, 2025 at 3:33 PM Dave Fisher wrote:
> So the “provided” issue could be configuration of the enforcer.
>
> > Filtering Dependency Errors
> > By default, all dependency convergence errors are reported, and any
> single error will fail the build. If you want to tune which dependenc
So the “provided” issue could be configuration of the enforcer.
> Filtering Dependency Errors
> By default, all dependency convergence errors are reported, and any single
> error will fail the build. If you want to tune which dependency errors are
> reported and fail the build, you can add the f
Y. Exactly.
On Wed, Jan 8, 2025 at 3:20 PM PJ Fanning wrote:
> The logs look like they come from Maven Enforcer and are based on the
> poms published to Maven Central.
>
> https://maven.apache.org/enforcer/enforcer-rules/dependencyConvergence.html
>
> On Wed, 8 Jan 2025 at 21:16, Dave Fisher wr
The logs look like they come from Maven Enforcer and are based on the
poms published to Maven Central.
https://maven.apache.org/enforcer/enforcer-rules/dependencyConvergence.html
On Wed, 8 Jan 2025 at 21:16, Dave Fisher wrote:
>
>
>
> > On Jan 8, 2025, at 11:13 AM, Tim Allison wrote:
> >
> > Th
> On Jan 8, 2025, at 11:13 AM, Tim Allison wrote:
>
> Thank you, all. I'm sorry for the noise.
>
> As you all point out, these are not a POI or even XMLBeans issue, and
> provided should be, ahem, provided.
>
> We added convergence checks in Tika after an irate downstream user
> complained.
If the Tika build is failing with a convergence issue, you can add an exclusion
block to the POI and/or XMLBean dependency to exclude maven-core which is an
optional dependency and unneeded here.
Example:
https://github.com/apache/hadoop/blob/trunk/hadoop-project/pom.xml#L245-L256
On 2025/01
Hi,
do I read this right that "maven-core" introduces this "convergence
problem", i.e. it depends on "plexus-classworlds" in two ways, once
directly on 2.8.0, and second transitively to a different version 2.6.0 via
"org.eclipse.sisu.plexus".
That would mean not something we should try to fix in
https://repo1.maven.org/maven2/org/apache/xmlbeans/xmlbeans/5.3.0/xmlbeans-5.3.0.pom
Just to link the xmlbeans pom. See almost all the dependencies are
scope=provided.
On Wednesday 8 January 2025 at 00:17:04 GMT+1, PJ Fanning
wrote:
The maven dependencies are 'provided' dependencie
The maven dependencies are 'provided' dependencies and are related to the
optional use of a Maven Plugin to run xmlbeans code generation.
POI users don't need these dependencies and any build tool worth its salt will
understand what a 'provided' dependency is.
I generally don't worry about conv
