Le mar. 7 mars 2017 12:49, Tushar Kapila <tgkp...@gmail.com> a écrit :
> So is my best bet to make a OS Process, collect the output and parse > the text to get files created like the following maven run snippet: > > > > Tests run: 3, Failures: 0, Errors: 0, Skipped: 0 > > [INFO] > [INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ CmdLineCalc --- > [INFO] Building jar: > > /Users/dev1/u/w/github/tgkprog/mavenSampleCalcCmdLineProject/CmdLineCalc/target/CmdLineCalc-1.jar > [INFO] META-INF/maven/s2n.sample.calc.cmdLine/CmdLineCalc/pom.xml > already added, skipping > [INFO] META-INF/maven/s2n.sample.calc.cmdLine/CmdLineCalc/pom.properties > already added, skipping > [INFO] > ------------------------------------------------------------------------ > [INFO] BUILD SUCCESS > [INFO] > ------------------------------------------------------------------------ > [INFO] Total time: 1.659 s > [INFO] Finished at: 2017-03-07T15:46:32+05:30 > [INFO] Final Memory: 16M/212M > [INFO] > ------------------------------------------------------------------------ > > --- > > if I see a BUILD SUCCESS, then work back a few lines to find jars, wars, > etc? > No, you should use Maven's API to get that information accurately. What I meant is that you can't know it without running the build.
