Well actually i think it's worse than that. Eclipse still generates a
.class file even if a corresponding .java file has a compilation error (
maybe it uses an old one or something, i'm not sure ). So if buildr
thinks that .class is up to date, it won't recompile, and it will run
test/package whatever else depends on compile, with bogus .class.
Sergey
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
