Thanx for your response! For now we're using the test=all workaround. I still hope we find a working solution to specify different output directory for the eclipse .classpath file -- it's somehow related to the eclipse M2_REPO-var-thread, where I still try to figure out how to tweak the eclipse extension so that I can set some property...
Cheers, Martin On Tue, 2009-07-07 at 15:35 -0700, Assaf Arkin wrote: > On Tue, Jul 7, 2009 at 3:09 PM, Alex Boisvert <[email protected]> wrote: > > > I'm not sure if "test=all" was designed this way on purpose... Assaf? > > > > Maybe we should consider "test=force" as a more intentioned command. > > > > Buildr uses a timestamp to figure out if > there's a code change and only execute tests if it needs to: > https://issues.apache.org/jira/browse/BUILDR-139 > > Look for the file reports/last_successful_run -- if you delete it, the tests > will run again. Also if any of the test dependencies are newer than that > file, but test dependency would be the target directory, I don't think it > checks every single .class file (expensive). > > > The test=all flag is for CI, where you want to force all the tests to run > regardless of errors (or other conditions). Another option is to run test:* > which will forcefully run all the test that match *. > > Assaf > > > > > > > alex > > > > > > On Tue, Jul 7, 2009 at 2:50 PM, Martin Grotzke < > > [email protected] > > > wrote: > > > > > Hi, > > > > > > I just tested this and it seems fine (in the buildfile I added > > > options.test = :all) - great! > > > > > > However, I don't understand exactly why this does the trick. The website > > > says: > > > > > > "As you probably noticed, Buildr will stop your build at the first test > > > that fails. We think it’s a good idea, except when it’s not. If you’re > > > using a continuous build system, you’ll want a report of all the failed > > > tests without stopping at the first failure. To make that happen, set > > > the environment variable test to “all”, or the Buildr options.test > > > option to :all." > > > > > > To me this does not explain, why it also solves our issue... Can you > > > give some more explanation? > > > > > > Thanx && cheers, > > > Martin > > > > > > > > > On Tue, 2009-07-07 at 14:22 -0700, Alex Boisvert wrote: > > > > One idea: You can force testing with "buidlr test=all" if that's what > > > you > > > > want. > > > > > > > > alex > > > > > > > > > > > > On Tue, Jul 7, 2009 at 1:56 PM, Martin Grotzke < > > > [email protected] > > > > > wrote: > > > > > > > > > Hi Alex, > > > > > > > > > > sorry I was not specific enough. What I meant is that we want to have > > > > > different output folders for eclipse and buildr. > > > > > > > > > > So that buildr builds to what it does, and the output of eclipse goes > > > to > > > > > e.g. "eclipse-bin" (both for classes, tests and resources). It just > > > must > > > > > not build to the target dir(s) that buildr uses for the check, if > > tests > > > > > must be executed. > > > > > > > > > > Again our original issue: > > > > > > > > > > 1 Write a test (that is ok) with eclipse, execute tests with buildr > > > > > -> test fails > > > > > 2 Change the test with eclipse (having "build automatically" set) so > > > > > that it fails, execute tests with buildr > > > > > -> tests are not executed > > > > > > > > > > If eclipse does not have the "build automatically" set this issue > > does > > > > > not occur, but buildr executes the tests. I asume, that (in 2) the > > > > > compiled classes (by eclipse) are just up to date with the sources > > and > > > > > that is the reason why buildr does not run the tests. > > > > > > > > > > Thanx && cheers, > > > > > Martin > > > > > > > > > > > > > > > On Tue, 2009-07-07 at 10:50 -0700, Alex Boisvert wrote: > > > > > > Hi Martin, > > > > > > > > > > > > I'm not sure I'm following.... the Eclipse task already generates > > > > > different > > > > > > output folders for classes/tests. > > > > > > > > > > > > e.g. > > > > > > > > > > > > <classpathentry kind="output" path="target/classes"/> > > > > > > <classpathentry excluding="**/.svn/|**/CVS/" > > > output="target/resources" > > > > > > kind="src" path="src/main/resources"/> > > > > > > <classpathentry excluding="**/.svn/|**/CVS/" > > > > > output="target/test/classes" > > > > > > kind="src" path="src/test/java"/> > > > > > > <classpathentry excluding="**/.svn/|**/CVS/" > > > > > > output="target/test/resources" kind="src" > > path="src/test/resources"/> > > > > > > > > > > > > You could explain with a example highlighting current vs desired > > > > > behavior? > > > > > > > > > > > > alex > > > > > > > > > > > > > > > > > > On Tue, Jul 7, 2009 at 10:10 AM, Martin Grotzke < > > > > > > [email protected]> wrote: > > > > > > > > > > > > > Hi, > > > > > > > > > > > > > > at first: we're just starting a new project here and it's the > > first > > > for > > > > > > > our company we're building with buildr - I'm very happy! :) > > > > > > > > > > > > > > Now my question: is it possible to specify a different output > > > folder > > > > > for > > > > > > > eclipse? > > > > > > > > > > > > > > We need this as we're using eclipse with "Build automatically". > > > This > > > > > > > causes the effect, that tests that once ran successfully are not > > > > > > > executed again, even if classes files or tests are changed. > > Turning > > > off > > > > > > > "build automatically" or a "clean" resolves this issue. However, > > we > > > > > > > still want to have an automatic build in eclipse, so this is not > > > the > > > > > > > preferred solution. > > > > > > > > > > > > > > Is there another solution for this (e.g. specifying different > > > output > > > > > > > folder for eclipse)? > > > > > > > > > > > > > > Thx && cheers, > > > > > > > Martin > > > > > > > > > > > > > > > > > > > > > > -- > > > Martin Grotzke > > > http://www.javakaffee.de/blog/ > > > > >
signature.asc
Description: This is a digitally signed message part
