Il sab 15 dic 2018, 18:56 Hervé BOUTEMY <herve.bout...@free.fr> ha scritto:
> Hi Enrico, > > you need the path relative to the basedir of it, not just the last > subdirectory name > > in this case, this is: > mvn verify -Dinvoker.test=projects/bugs/massembly-201 -Prun-its > > Welcome to the team :) > Thanks. As reported on slack that approach works but there is apparently a failure, not about the test but the dummy 'parent' [INFO] [INFO] --- maven-invoker-plugin:3.0.1:integration-test (integration-test) @ maven-assembly-plugin --- [INFO] Running Setup Jobs [INFO] Building: it-project-parent/pom.xml [INFO] it-project-parent/pom.xml ........................ FAILED (3.1 s) [INFO] The build exited with code 1. See /home/eolivelli/dev/maven-assembly-plugin/target/it/it-project-parent/build.log for details. [INFO] Building: projects/bugs/massembly-190/pom.xml [INFO] run post-build script verify.bsh [INFO] projects/bugs/massembly-190/pom.xml .............. SUCCESS (7.6 s) [INFO] Enrico > Regards, > > Hervé > > Le samedi 15 décembre 2018, 16:24:10 CET Enrico Olivelli a écrit : > > Robert, > > thanks for your quick reply > > it seems to me that it does not work > > > > I am trying with something link: > > mvn verify -Dinvoker.test=massembly-201 -Prun-its > > > > > > [INFO] --- maven-invoker-plugin:3.0.1:integration-test > > (integration-test) @ maven-assembly-plugin --- > > [INFO] No projects were selected for execution. > > [INFO] > > [INFO] --- maven-checkstyle-plugin:3.0.0:check (checkstyle-check) @ > > maven-assembly-plugin --- > > [INFO] > > [INFO] --- maven-invoker-plugin:3.0.1:verify (integration-test) @ > > maven-assembly-plugin --- > > [INFO] No invoker report files found, nothing to check. > > [INFO] > > ------------------------------------------------------------------------ > > [INFO] BUILD SUCCESS > > [INFO] > > ------------------------------------------------------------------------ > > [INFO] Total time: 37.178 s > > [INFO] Finished at: 2018-12-15T16:19:24+01:00 > > [INFO] Final Memory: 50M/787M > > > > > > without "run-its" profile invoker is not activated at all > > > > and anyway I see "surefire" is running unit tests > > > > (I am with mvn 3.6.0, but I guess it is not so important) > > > > Enrico > > > > > > Il giorno sab 15 dic 2018 alle ore 16:19 Robert Scholte > > > > <rfscho...@apache.org> ha scritto: > > > Assuming this IT is executed by the maven-invoker-plugin, try > > > invoker.test[1], i.e. : > > > > > > mvn verify -Dinvoker.test=MASSEMBLY-XXX* > > > > > > [1] > > > > https://maven.apache.org/plugins/maven-invoker-plugin/run-mojo.html#invoke > > > rTest > > > > > > On Sat, 15 Dec 2018 16:17:10 +0100, Enrico Olivelli < > eolive...@gmail.com> > > > > > > wrote: > > > > Hi, > > > > I am working on an issue on maven-assembly plugin. > > > > which is the better way to run only a single integration test ? > > > > > > > > Is there any standard practice across plugins ? > > > > > > > > Enrico > > > > > > > > --------------------------------------------------------------------- > > > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > > -- -- Enrico Olivelli
