Yeap. It's a know issue in windoze env with mvn 2.0.7 (http://jira.codehaus.org/browse/MNG-2685).
-- Olivier 2008/2/4, David Siefert <[EMAIL PROTECTED]>: > Okay, on one machine I am running maven-2.0.7 and when the i.t. project > fails, the main project still reports success. On another machine I am > using maven-2.0.8 and when the i.t. project fails, the main project build > correctly reports failure. I am mentioning it here for anyone who searches > the mailing lists with failing i.t. projects being reported as success--the > solution is to upgrade to maven-2.0.8 :) > > Thanks again Olivier for your help. > > -David > > On Feb 1, 2008 4:41 PM, Olivier Lamy <[EMAIL PROTECTED]> wrote: > > > If building your maven project failed, the invoker will report this > > (line starting with : ...FAILED) > > > > If not we have an issue here in the invoker plugin. > > > > -- > > Olivier > > > > 2008/2/1, David Siefert <[EMAIL PROTECTED]>: > > > Thank you very much Olivier, I am now able to invoke the integration > > test > > > projects from my main project just like the maven-jar-plugin does. I > > have > > > another issue: a beanshell script is required to report whether or not > > the > > > build has failed or succeeded. Why can't the build failure of the maven > > > project be reported to the invoker plugin so I do not have to do this? > > > > > > Thanks! > > > > > > -David > > > > > > On Jan 23, 2008 12:41 PM, Olivier Lamy <[EMAIL PROTECTED]> wrote: > > > > > > > Hi, > > > > You can have a look at the its in some maven plugins (jar plugin [1]) > > > > to see how we organize execution of the maven-invoker-plugin. > > > > Look at the pom and the profile called integration-tests. > > > > But IMHO the maven-invoker-plugin is for maven plugins not for jar > > > > artifacts. > > > > > > > > -- > > > > Olivier > > > > |1] > > https://svn.apache.org/repos/asf/maven/plugins/trunk/maven-jar-plugin/ > > > > > > > > 2008/1/23, David Siefert <[EMAIL PROTECTED]>: > > > > > Hi, > > > > > > > > > > I am trying to get my integration tests to run as part of the main > > > > project > > > > > build using the maven-invoker-plugin. However it is impossible (at > > > > least > > > > > without some hacking) to have the IT projects run because of the > > maven > > > > build > > > > > lifecycle. > > > > > > > > > > compile > > > > > package <-- JAR created > > > > > integration-test <-- invoke maven it projects [FAILS: Cannot load > > > > artifact > > > > > that was built during package phase] > > > > > verify <-- Reports success anyway even though build has failed due > > to > > > > above > > > > > artifact issue! > > > > > > > > > > I could see a possible solution: use ant task to copy the project > > > > artifact, > > > > > or use a systemPath dependency--however this could be error prone > > > > (location > > > > > of the artifact). > > > > > > > > > > Any suggestions? > > > > > > > > > > Thanks, > > > > > > > > > > David > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
