You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@buildr.apache.org by dynnamitt <kj...@gmail.com> on 2008/05/20 10:41:11 UTC
test/classes (1.3.0) VS test-classes (1.2.10)
What is the (1.3.0-) logic behind: "compiling tests into
target/test/classes and not target/test-classes" ?
This has given me some issues after an upgrade from 1.2.10 :
1) Eclipse will no longer run test after I do 'buildr clean install'.
2) buildr cannot find classes to run during Integration testing ( looks like
it's still searching in /test-classes ) ??
mvh
Dynnamitt
--
View this message in context: http://www.nabble.com/test-classes-%281.3.0%29-VS-test-classes-%281.2.10%29-tp17335865p17335865.html
Sent from the Buildr - User mailing list archive at Nabble.com.
Re: test/classes (1.3.0) VS test-classes (1.2.10)
Posted by dynnamitt <kj...@gmail.com>.
is
"compiling tests into target/test/classes and not target/test-classes"
compatible with maven2 then?
Assaf Arkin wrote:
>
> On Tue, May 20, 2008 at 1:41 AM, dynnamitt <kj...@gmail.com>
> wrote:
>>
>> What is the (1.3.0-) logic behind: "compiling tests into
>> target/test/classes and not target/test-classes" ?
>
> To separate everything under target more in line with everything under
> source, which would have less special cases when we add more things to
> target.
>
>> This has given me some issues after an upgrade from 1.2.10 :
>>
>> 1) Eclipse will no longer run test after I do 'buildr clean install'.
>
> You would need to regenerate the Eclipse files.
>
>> 2) buildr cannot find classes to run during Integration testing ( looks
>> like
>> it's still searching in /test-classes ) ??
>
> It's the same test framework/configuration, the only difference is
> running the tests after packaging, but it would look for files in the
> same directory.
>
> Assaf
>
>>
>>
>> mvh
>> Dynnamitt
>> --
>> View this message in context:
>> http://www.nabble.com/test-classes-%281.3.0%29-VS-test-classes-%281.2.10%29-tp17335865p17335865.html
>> Sent from the Buildr - User mailing list archive at Nabble.com.
>
>
--
View this message in context: http://www.nabble.com/test-classes-%281.3.0%29-VS-test-classes-%281.2.10%29-tp17335865p17551801.html
Sent from the Buildr - User mailing list archive at Nabble.com.
Re: test/classes (1.3.0) VS test-classes (1.2.10)
Posted by Assaf Arkin <ar...@intalio.com>.
On Tue, May 20, 2008 at 1:41 AM, dynnamitt <kj...@gmail.com> wrote:
>
> What is the (1.3.0-) logic behind: "compiling tests into
> target/test/classes and not target/test-classes" ?
To separate everything under target more in line with everything under
source, which would have less special cases when we add more things to
target.
> This has given me some issues after an upgrade from 1.2.10 :
>
> 1) Eclipse will no longer run test after I do 'buildr clean install'.
You would need to regenerate the Eclipse files.
> 2) buildr cannot find classes to run during Integration testing ( looks like
> it's still searching in /test-classes ) ??
It's the same test framework/configuration, the only difference is
running the tests after packaging, but it would look for files in the
same directory.
Assaf
>
>
> mvh
> Dynnamitt
> --
> View this message in context: http://www.nabble.com/test-classes-%281.3.0%29-VS-test-classes-%281.2.10%29-tp17335865p17335865.html
> Sent from the Buildr - User mailing list archive at Nabble.com.
Re: test/classes (1.3.0) VS test-classes (1.2.10)
Posted by Alex Boisvert <bo...@intalio.com>.
On Tue, May 20, 2008 at 1:41 AM, dynnamitt <kj...@gmail.com> wrote:
> This has given me some issues after an upgrade from 1.2.10 :
> 1) Eclipse will no longer run test after I do 'buildr clean install'.
I have the same problem with both ;) There's no substantive differences
between the Eclipse task in 1.2.10 and 1.3.x.
Eclipse is sensitive to any external changes to classes; it doesn't
automatically recognize outside change (other than on sources) so you have
to tell it to "Refresh" your project and often to a "Clean project" as well.
alex