Skip to content
This repository has been archived by the owner on Jul 23, 2020. It is now read-only.

mvn build fails when following getting started guide #4139

Closed
dkranz opened this issue Aug 7, 2018 · 4 comments
Closed

mvn build fails when following getting started guide #4139

dkranz opened this issue Aug 7, 2018 · 4 comments

Comments

@dkranz
Copy link

dkranz commented Aug 7, 2018

I was following the guide. When I got to section 5.15 where you click the Run button in the new Che workspace I saw the following error:

scl enable rh-maven33 'mvn compile vertx:run -f -Dvertx.disableDnsResolver=true'https://routeyls1kykd-dkranz-che.9a6d.starter-us-east-1a.openshiftapps.com
Unable to parse command line options: Missing argument for option: f

usage: mvn [options] [<goal(s)>] [<phase(s)>]

Options:
-am,--also-make If project list is specified, also
build projects required by the
list
-amd,--also-make-dependents If project list is specified, also
build projects that depend on
projects on the list
-B,--batch-mode Run in non-interactive (batch)
mode
-b,--builder The id of the build strategy to
use.
-C,--strict-checksums Fail the build if checksums don't
match
-c,--lax-checksums Warn if checksums don't match
-cpu,--check-plugin-updates Ineffective, only kept for
backward compatibility
-D,--define Define a system property
-e,--errors Produce execution error messages
-emp,--encrypt-master-password Encrypt master security password
-ep,--encrypt-password Encrypt server password
-f,--file Force the use of an alternate POM
file (or directory with pom.xml).
-fae,--fail-at-end Only fail the build afterwards;
allow all non-impacted builds to
continue
-ff,--fail-fast Stop at first failure in
reactorized builds
-fn,--fail-never NEVER fail the build, regardless
of project result
-gs,--global-settings Alternate path for the global
settings file
-gt,--global-toolchains Alternate path for the global
toolchains file
-h,--help Display help information
-l,--log-file Log file where all build output
will go.
-llr,--legacy-local-repository Use Maven 2 Legacy Local
Repository behaviour, ie no use of
_remote.repositories. Can also be
activated by using
-Dmaven.legacyLocalRepo=true
-N,--non-recursive Do not recurse into sub-projects
-npr,--no-plugin-registry Ineffective, only kept for
backward compatibility
-npu,--no-plugin-updates Ineffective, only kept for
backward compatibility
-nsu,--no-snapshot-updates Suppress SNAPSHOT updates
-o,--offline Work offline
-P,--activate-profiles Comma-delimited list of profiles
to activate
-pl,--projects Comma-delimited list of specified
reactor projects to build instead
of all projects. A project can be
specified by [groupId]:artifactId
or by its relative path.
-q,--quiet Quiet output - only show errors
-rf,--resume-from Resume reactor from specified
project
-s,--settings Alternate path for the user
settings file
-T,--threads Thread count, for instance 2.0C
where C is core multiplied
-t,--toolchains Alternate path for the user
toolchains file
-U,--update-snapshots Forces a check for missing
releases and updated snapshots on
remote repositories
-up,--update-plugins Ineffective, only kept for
backward compatibility
-V,--show-version Display version information
WITHOUT stopping build
-v,--version Display version information
-X,--debug Produce execution debug output
[ERROR] Error executing Maven.
org.apache.commons.cli.MissingArgumentException: Missing argument for option: f
at org.apache.commons.cli.Parser.processArgs(Parser.java:343)
at org.apache.commons.cli.Parser.processOption(Parser.java:393)
at org.apache.commons.cli.Parser.parse(Parser.java:199)
at org.apache.commons.cli.Parser.parse(Parser.java:85)
at org.apache.maven.cli.CLIManager.parse(CLIManager.java:159)
at org.apache.maven.cli.MavenCli.cli(MavenCli.java:406)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:277)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
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:289)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)

@bartoszmajsak
Copy link
Contributor

Thanks for detailed report @dkranz! This seems to be a duplicate of #2152 - in such a case could you subscribe to that issue and close this one?

@dkranz dkranz closed this as completed Aug 7, 2018
@rhopp
Copy link
Collaborator

rhopp commented Aug 8, 2018

@bartoszmajsak, @dkranz To me it seems more like duplicate of #2856 (the macro ${current.project.path} sometimes returns empty string - and because of that the build fails... the option -f expects an argument)
This was also reported upstream (eclipse-che/che#9321), but unfortunately it was closed, even though I provided steps to reproduce on latest upstream. I'll try to get in contact with che-qe guys to reopen it.

@bartoszmajsak
Copy link
Contributor

@rhopp Well, then we have two cases where -f is causing trouble. For Vertx and it's what you described, for WF Swarm/Thorntail it's https://issues.jboss.org/browse/THORN-2049

Would be good to understand what is this "sometimes" you mention :)

@rhopp
Copy link
Collaborator

rhopp commented Aug 8, 2018

@bartoszmajsak One of the use-cases where it's 100% reproducible is described in this comment: eclipse-che/che#9321 (comment) and the screencast of that is in the comment below that ;-)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants