[WARNING] The POM for org.apache.jmeter:ApacheJMeter_http:jar:5.6.1 is invalid #6041

jloisel · 2023-07-11T07:42:41Z

Expected behavior

When trying to depend on Apache JMeter http dependency:

[WARNING] The POM for org.apache.jmeter:ApacheJMeter_http:jar:5.6.1 is invalid, transitive dependencies (if any) will not be available, enable debug logging for more details

java: package org.apache.jmeter.testelement does not exist

Actual behavior

No response

Steps to reproduce the problem

  <dependencies>
    <dependency>
      <groupId>org.apache.jmeter</groupId>
      <artifactId>ApacheJMeter_http</artifactId>
      <version>5.6.1</version>
    </dependency>
  </dependencies>

JMeter Version

5.6.1

Java Version

openjdk version "17.0.7" 2023-04-18

OS Version

Ubuntu 22.04 LTS

vlsi · 2023-07-11T07:51:54Z

[WARNING] The POM for org.apache.jmeter:ApacheJMeter_http:jar:5.6.1 is invalid, transitive dependencies (if any) will not be available: 1 problem was encountered while building the effective model for org.apache.jmeter:ApacheJMeter_http:5.6.1
[ERROR] 'dependencies.dependency.version' for com.google.auto.service:auto-service-annotations:jar is missing. @

vlsi · 2023-07-11T08:28:36Z

Frankly speaking, I agree it might look confusing for a pom to miss <version>, however, a missing version is in line with XSD.
So I think it would make sense to follow-up with Maven developers, and request that Maven should not discard all the transitive dependencies once it faces a single one without a version.

milamberspace · 2023-07-11T09:27:59Z

org.apache.jmeter.samplers.SampleListener is in ApacheJMeter_core not _http?

milamberspace · 2023-07-11T09:29:05Z

Works with this pom

<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0"
         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
         xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
    <modelVersion>4.0.0</modelVersion>

    <groupId>org.example</groupId>
    <artifactId>TestBugMaven</artifactId>
    <version>1.0-SNAPSHOT</version>

    <properties>
        <maven.compiler.source>17</maven.compiler.source>
        <maven.compiler.target>17</maven.compiler.target>
        <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
    </properties>

    <dependencies>
        <dependency>
            <groupId>org.apache.jmeter</groupId>
            <artifactId>ApacheJMeter_core</artifactId>
            <version>5.6.1</version>
        </dependency>
    </dependencies>
</project>

vlsi · 2023-07-11T09:37:44Z

@milamberspace , try running mvn dependency:tree with that pom. it will not show transitive dependencies.

[WARNING] The POM for org.apache.jmeter:ApacheJMeter_core:jar:5.6.1 is invalid, transitive dependencies (if any) will not be available, enable debug logging for more details
[INFO]
[INFO] --- maven-dependency-plugin:2.8:tree (default-cli) @ TestBugMaven ---
[INFO] org.example:TestBugMaven:jar:1.0-SNAPSHOT
[INFO] \- org.apache.jmeter:ApacheJMeter_core:jar:5.6.1:compile

Then, if you patch ~/.m2/repository/org/apache/jmeter/ApacheJMeter_core/5.6.1 by adding <version>1.1.1</version> to auto-service-annotations, you'll get a dramatic difference:

[INFO] --- maven-dependency-plugin:2.8:tree (default-cli) @ TestBugMaven ---
[INFO] org.example:TestBugMaven:jar:1.0-SNAPSHOT
[INFO] \- org.apache.jmeter:ApacheJMeter_core:jar:5.6.1:compile
[INFO]    +- org.apache.jmeter:ApacheJMeter:jar:5.6.1:compile
[INFO]    +- org.apache.jmeter:jorphan:jar:5.6.1:compile
[INFO]    +- bsf:bsf:jar:2.4.0:compile
[INFO]    |  \- commons-logging:commons-logging:jar:1.0.4:compile
[INFO]    +- com.fifesoft:rsyntaxtextarea:jar:3.3.3:compile
[INFO]    +- net.sf.jtidy:jtidy:jar:r938:compile
[INFO]    +- com.thoughtworks.xstream:xstream:jar:1.4.20:compile
[INFO]    |  \- io.github.x-stream:mxparser:jar:1.2.2:compile
[INFO]    |     \- xmlpull:xmlpull:jar:1.1.3.1:compile
[INFO]    +- org.apache.logging.log4j:log4j-1.2-api:jar:2.20.0:compile
[INFO]    +- org.apache.logging.log4j:log4j-api:jar:2.20.0:compile
[INFO]    +- org.apache.logging.log4j:log4j-core:jar:2.20.0:compile
[INFO]    +- org.apache.logging.log4j:log4j-slf4j-impl:jar:2.20.0:compile
[INFO]    |  \- org.slf4j:slf4j-api:jar:1.7.25:compile
[INFO]    +- org.apiguardian:apiguardian-api:jar:1.1.2:compile
[INFO]    +- oro:oro:jar:2.0.8:compile
[INFO]    +- xalan:xalan:jar:2.7.3:compile
[INFO]    +- xalan:serializer:jar:2.7.3:compile
[INFO]    +- xml-apis:xml-apis:jar:1.4.01:compile
[INFO]    +- net.sf.saxon:Saxon-HE:jar:11.5:compile
[INFO]    |  +- org.xmlresolver:xmlresolver:jar:4.6.4:compile
[INFO]    |  |  +- org.apache.httpcomponents.client5:httpclient5:jar:5.1.3:runtime
[INFO]    |  |  |  \- org.apache.httpcomponents.core5:httpcore5-h2:jar:5.1.3:runtime
[INFO]    |  |  \- org.apache.httpcomponents.core5:httpcore5:jar:5.1.3:runtime
[INFO]    |  \- org.xmlresolver:xmlresolver:jar:data:4.6.4:compile
[INFO]    +- org.jetbrains.kotlin:kotlin-stdlib-jdk8:jar:1.8.22:compile
[INFO]    |  +- org.jetbrains.kotlin:kotlin-stdlib:jar:1.8.22:compile
[INFO]    |  \- org.jetbrains.kotlin:kotlin-stdlib-jdk7:jar:1.8.22:compile
[INFO]    +- com.google.auto.service:auto-service-annotations:jar:1.1.1:compile
[INFO]    +- org.jetbrains.kotlinx:kotlinx-coroutines-core:jar:1.7.1:runtime
...

Apparently, Maven discards ALL transitive dependency in case it detects a single issue. I think it is something to be fixed in Maven. In this case, only com.google.auto.service:auto-service-annotations was missing a version, and it is not essential overall. If Maven discarded a single problematic dependency or failed the build, then it would be way better.

vlsi · 2023-07-11T09:44:06Z

I've filed an issue for the Maven team: https://issues.apache.org/jira/browse/MNG-7842
I believe Maven's behavior is not really consistent as dependencyManagement does not help.

Ardesco · 2023-07-11T09:51:33Z

I would suggest this still needs a fix. Even if Maven does fix this issue it would require all Maven users to upgrade to the latest version of Maven which can be problematic for many corp environments.

For the sake of backwards compatibility I think it would make sense to release a 5.6.2 with the version number specified. You can then deprecate old versions of Maven supported in the future if/when Maven changes the behaviour and start not specifying versions at that point.

Personally I would suggest it's good practice to specify versions, overall it makes it clearer.

Ardesco · 2023-07-11T10:22:46Z

Works with this pom

<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0"
         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
         xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
    <modelVersion>4.0.0</modelVersion>

    <groupId>org.example</groupId>
    <artifactId>TestBugMaven</artifactId>
    <version>1.0-SNAPSHOT</version>

    <properties>
        <maven.compiler.source>17</maven.compiler.source>
        <maven.compiler.target>17</maven.compiler.target>
        <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
    </properties>

    <dependencies>
        <dependency>
            <groupId>org.apache.jmeter</groupId>
            <artifactId>ApacheJMeter_core</artifactId>
            <version>5.6.1</version>
        </dependency>
    </dependencies>
</project>

This only fixes the problem if JMeter is a direct dependency. If it's a transitive dependency you are still getting error messages saying that the POM is invalid and that transitive dependencies will not be available.

hennidk · 2023-07-11T10:41:36Z

In my case I am unable to compile my project, getting the error:

... 
Compilation failure
[ERROR]   reason: class file for org.apiguardian.api.API$Status not found
[ERROR] warning: unknown enum constant Status.EXPERIMENTAL
...
error: cannot access Function0
  class file for kotlin.jvm.functions.Function0 not found

Appears to be the same problem as mentioned where Maven discards everything - surely fixing the invalid POM error as suggested is the best way forward?

jloisel · 2023-07-11T11:29:42Z

I also believe versions should always be specified, otherwise it might lead to inconsistencies (which version is it supposed to take then?).

vlsi · 2023-07-11T12:01:50Z

I also believe versions should always be specified, otherwise it might lead to inconsistencies (which version is it supposed to take then?).

The version might be taken from a dependencyManagement block.

jloisel · 2023-07-11T12:39:45Z

Of course, most people manage them centrally doing so. That being said, the effective pom should include dependency version.

vlsi · 2023-07-11T13:21:16Z

This seems to be resolved in 5.6.2-rc1:

<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0"
         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
         xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
    <modelVersion>4.0.0</modelVersion>

    <groupId>org.example</groupId>
    <artifactId>TestBugMaven</artifactId>
    <version>1.0-SNAPSHOT</version>

    <dependencies>
        <dependency>
            <groupId>org.apache.jmeter</groupId>
            <artifactId>ApacheJMeter_http</artifactId>
            <version>5.6.2</version>
        </dependency>
    </dependencies>

    <repositories>
      <repository>
        <id>jmeter-5.6.2-rc1</id>
        <url>https://repository.apache.org/content/repositories/orgapachejmeter-1087</url>
      </repository>
    </repositories>
</project>

Please try it.

Ardesco · 2023-07-11T13:55:09Z

That version looks good to me, thanks for the quick turnaround.

jloisel added defect to-triage labels Jul 11, 2023

vlsi mentioned this issue Jul 11, 2023

Add verifications for the generated pom.xml (e.g. verify if the set of published poms can be resolved) gradle/gradle#25705

Open

vlsi mentioned this issue Jul 11, 2023

chore: Fix compatibility with Maven's pom.xml parser by adding explicit versions for com.google.auto.service:auto-service-annotations #6042

Merged

vlsi added this to the 5.6.2 milestone Jul 11, 2023

vlsi removed the to-triage label Jul 11, 2023

vlsi pinned this issue Jul 11, 2023

vlsi closed this as completed in e424b5f Jul 11, 2023

asfgit pushed a commit that referenced this issue Jul 11, 2023

Add PR number and mention regression since JMeter 5.6. See #6041

f99eb5e

vlsi unpinned this issue Jan 9, 2024

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[WARNING] The POM for org.apache.jmeter:ApacheJMeter_http:jar:5.6.1 is invalid #6041

[WARNING] The POM for org.apache.jmeter:ApacheJMeter_http:jar:5.6.1 is invalid #6041

jloisel commented Jul 11, 2023

vlsi commented Jul 11, 2023

vlsi commented Jul 11, 2023

milamberspace commented Jul 11, 2023

milamberspace commented Jul 11, 2023 •

edited

Loading

vlsi commented Jul 11, 2023

vlsi commented Jul 11, 2023

Ardesco commented Jul 11, 2023

Ardesco commented Jul 11, 2023

hennidk commented Jul 11, 2023

jloisel commented Jul 11, 2023

vlsi commented Jul 11, 2023

jloisel commented Jul 11, 2023

vlsi commented Jul 11, 2023

Ardesco commented Jul 11, 2023

[WARNING] The POM for org.apache.jmeter:ApacheJMeter_http:jar:5.6.1 is invalid #6041

[WARNING] The POM for org.apache.jmeter:ApacheJMeter_http:jar:5.6.1 is invalid #6041

Comments

jloisel commented Jul 11, 2023

Expected behavior

Actual behavior

Steps to reproduce the problem

JMeter Version

Java Version

OS Version

vlsi commented Jul 11, 2023

vlsi commented Jul 11, 2023

milamberspace commented Jul 11, 2023

milamberspace commented Jul 11, 2023 • edited Loading

vlsi commented Jul 11, 2023

vlsi commented Jul 11, 2023

Ardesco commented Jul 11, 2023

Ardesco commented Jul 11, 2023

hennidk commented Jul 11, 2023

jloisel commented Jul 11, 2023

vlsi commented Jul 11, 2023

jloisel commented Jul 11, 2023

vlsi commented Jul 11, 2023

Ardesco commented Jul 11, 2023

milamberspace commented Jul 11, 2023 •

edited

Loading