You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Tamas Cservenak (Jira)" <ji...@apache.org> on 2023/02/24 09:36:00 UTC
[jira] [Commented] (MNG-7654) Malformed POM in integration test data
[ https://issues.apache.org/jira/browse/MNG-7654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17693100#comment-17693100 ]
Tamas Cservenak commented on MNG-7654:
--------------------------------------
This POM is in "remote", so Maven on pulling this will:
* warn about POM not being parsable (no deps available)
* happily fetch the JAR and stick it to classpath w/o depsĀ
* BUT, as there are NO deps, the end result is 1 JAR on CP w/ or w/o POM
This is why it passes ok, but 100% there is a warning about this in build.log
> Malformed POM in integration test data
> --------------------------------------
>
> Key: MNG-7654
> URL: https://issues.apache.org/jira/browse/MNG-7654
> Project: Maven
> Issue Type: Bug
> Components: Core
> Reporter: Pavel Horal
> Priority: Minor
>
> I have stumbled on malformed POM in integration test data [maven-core/src/test/remote-repo/org/apache/maven/maven-plugin-api/2.0/maven-plugin-api-2.0.pom#L16|https://github.com/apache/maven/blob/master/maven-core/src/test/remote-repo/org/apache/maven/maven-plugin-api/2.0/maven-plugin-api-2.0.pom#L16]
> {code}
> <dependency>
> <groupId>junit</groupId>
> <artifactId>junit</artifactId>
> <version4.13.1</version>
> <scope>test</scope>
> </dependency>
> {code}
> This error was introduced in https://github.com/apache/maven/commit/449e6dc9db8152b1c67728a0fb8b16dc04e8976f when upgrading JUnit dependency.
> The reason I am creating this issue is that it is very strange that a malformed POM does not break any test. So either there is another issue in some test or that file is useless and can be (should be?) deleted.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)