gnodet commented on PR #117: URL: https://github.com/apache/maven-plugin-tools/pull/117#issuecomment-1315559536
> Trying: > > ``` > mvn org.apache.maven.its:v4api:1.0-SNAPSHOT:first > > Apache Maven 4.0.0-alpha-2 (c07700ffc97d3967a8de77d5a1065f5e6115c00e) > > [ERROR] Failed to parse plugin descriptor for org.apache.maven.its:v4api:1.0-SNAPSHOT (/Users/.../.m2/repository/org/apache/maven/its/v4api/1.0-SNAPSHOT/v4api-1.0-SNAPSHOT.jar): JAR entry META-INF/maven/lifecycle.xml not found in /Users/.../.m2/repository/org/apache/maven/its/v4api/1.0-SNAPSHOT/v4api-1.0-SNAPSHOT.jar > ``` > > ``` > mvn org.apache.maven.its:v4api:1.0-SNAPSHOT:first > > Apache Maven 3.8.6 (84538c9988a25aec085021c365c560670ad80f63) > > [ERROR] Failed to parse plugin descriptor for org.apache.maven.its:v4api:1.0-SNAPSHOT (/Users/.../.m2/repository/org/apache/maven/its/v4api/1.0-SNAPSHOT/v4api-1.0-SNAPSHOT.jar): JAR entry META-INF/maven/lifecycle.xml not found in /Users/.../.m2/repository/org/apache/maven/its/v4api/1.0-SNAPSHOT/v4api-1.0-SNAPSHOT.jar -> [Help 1] > ``` Do we need the plugin to actually run ? I can either remove the `@Execute` or add a `lifecycle.xml` After that, another error happens because the plugin is being injected with a custom `@Component`, but there's no such public component in the v4 api. I can also remove the custom component injection. But the IT is testing the `plugin.xml` generation and not the plugin itself. Another option is to document that this plugin does not actually work. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
