[ 
https://issues.apache.org/jira/browse/MNG-7654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17652475#comment-17652475
 ] 

Pavel Horal commented on MNG-7654:
----------------------------------

After deleting the malformed POM:


{code}
[ERROR] Failures: 
[ERROR]   MavenLifecycleParticipantTest.testDependencyInjection:112 
[org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal 
org.apache.maven.its.plugins:maven-it-plugin:0.1:it (test) on project simple: 
Execution test of goal org.apache.maven.its.plugins:maven-it-plugin:0.1:it 
failed: Plugin org.apache.maven.its.plugins:maven-it-plugin:0.1 or one of its 
dependencies could not be resolved: Could not find artifact 
org.apache.maven:maven-plugin-api:jar:2.0 in central 
(file:///srv/repo/maven/maven/maven-core/src/test/remote-repo/)] ==> expected: 
<false> but was: <true>
[ERROR]   LifecycleExecutorTest.testExecutionListeners:517->assertEventLog:521 
expected: <beforeProjectExecution project-basic
beforeProjectLifecycleExecution project-basic
beforeMojoExecution project-basic:default-resources
afterMojoExecutionSuccess project-basic:default-resources
beforeMojoExecution project-basic:default-compile
afterMojoExecutionSuccess project-basic:default-compile
beforeMojoExecution project-basic:default-testResources
afterMojoExecutionSuccess project-basic:default-testResources
beforeMojoExecution project-basic:default-testCompile
afterMojoExecutionSuccess project-basic:default-testCompile
beforeMojoExecution project-basic:default-test
afterMojoExecutionSuccess project-basic:default-test
beforeMojoExecution project-basic:default-jar
afterMojoExecutionSuccess project-basic:default-jar
afterProjectExecutionSuccess project-basic
> but was: <beforeProjectExecution project-basic
beforeProjectLifecycleExecution project-basic
afterProjectExecutionFailure project-basic
>
[ERROR] Errors: 
[ERROR]   PluginManagerTest.testBuildExtensionsPluginLoading:279 » IllegalState 
org.apache.maven.plugin.PluginManagerException: Plugin 
org.apache.maven.its.plugins:maven-it-plugin:0.1 or one of its dependencies 
could not be resolved: Could not find artifact 
org.apache.maven:maven-plugin-api:jar:2.0 in central 
(file:///srv/repo/maven/maven/maven-core/src/test/remote-repo/)
[ERROR]   PluginManagerTest.testPluginRealmCache:240 » PluginResolution Plugin 
org.apache.maven.its.plugins:maven-it-plugin:0.1 or one of its dependencies 
could not be resolved: Could not find artifact 
org.apache.maven:maven-plugin-api:jar:2.0 in central 
(file:///srv/repo/maven/maven/maven-core/src/test/remote-repo/)
[ERROR]   
PluginManagerTest.testThatPluginDependencyThatHasSystemScopeIsResolved:199 » 
PluginResolution Plugin org.apache.maven.its.plugins:maven-it-plugin:0.1 or one 
of its dependencies could not be resolved: Could not find artifact 
org.apache.maven:maven-plugin-api:jar:2.0 in central 
(file:///srv/repo/maven/maven/maven-core/src/test/remote-repo/)
{code}

So the file is being used. Strange that no parser is complaining about invalid 
XML.

> 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)

Reply via email to