setup-customarchiver-maven-plugin failure on master when running a single IT

Stephanie Wang

unread,

May 7, 2020, 12:26:42 PM5/7/20

to mojohaus-dev

Hi,

On the latest master branch, when we try to run any single IT in the project root by running:

mvn verify -Dinvoker.test=bom-flattenMode

We see the following build failure:

[ERROR] The following builds failed:

[ERROR] * setup-customarchive-maven-plugin/pom.xml

build.log shows:

[ERROR] The goal you specified requires a project to execute but there is no POM in this directory (/usr/local/google/home/stephwang/Desktop/stephdev/flatten-maven-plugin/target/it/setup-customarchive-maven-plugin). Please verify you invoked Maven from the correct directory. -> [Help 1]

org.apache.maven.lifecycle.MissingProjectException: The goal you specified requires a project to execute but there is no POM in this directory (/usr/local/google/home/stephwang/Desktop/stephdev/flatten-maven-plugin/target/it/setup-customarchive-maven-plugin). Please verify you invoked Maven from the correct directory.

at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:85)

at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)

at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)

at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)

at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)

at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288)

at org.apache.maven.cli.MavenCli.main (MavenCli.java:192)

at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)

at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)

at java.lang.reflect.Method.invoke (Method.java:498)

at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:282)

at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225)

at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:406)

at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347)

[ERROR]

[ERROR] For more information about the errors and possible solutions, please read the following articles:

[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MissingProjectException

Has anyone else seen this? Any idea how to fix?

My local env is:

Maven home: /usr/local/google/home/stephwang/opt/maven/latest

Java version: 1.8.0_181-google-v7, vendor: Google Inc., runtime: /usr/local/buildtools/java/jdk8-google-v7-64/jre

Default locale: en_US, platform encoding: UTF-8

OS name: "linux", version: "5.2.17-1rodete3-amd64", arch: "amd64", family: "unix"

Thanks!

Stephanie Wang

unread,

May 13, 2020, 11:48:04 AM5/13/20

to mojohaus-dev

I have been working on this with an engineer at Google, Nuoyu Yang. He discovered that this happens only if we do not explicitly run setup-customarchive-maven-plugin test first before running another IT.

Below command always works without failure:

`mvn verify -Dinvoker.test=setup-customarchive-maven-plugin, [another test]`

We conclude that we do not need to make any fixes here. However, could anyone chime in on why this is required? It would help us understand better.

Thank you.

Olivier Lamy

unread,

May 17, 2020, 5:59:35 PM5/17/20

to mojoha...@googlegroups.com

This vaguely remember me a bug in invoker plugin..

because looking at https://maven.apache.org/plugins/maven-invoker-plugin/integration-test-mojo.html#setupIncludes

default value is setup*/pom.xml so in this case

not sure if we use last version of maven-invoker-plugin or maybe the bug hasn't been fixed yet.

--
You received this message because you are subscribed to the Google Groups "mojohaus-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mojohaus-dev...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/mojohaus-dev/e45363fb-1614-4aba-9816-14ea7bedbc9b%40googlegroups.com.