[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [eclipselink-dev] Tests don't compile in branch 1.1.2, checkouttrunk is not enough?
|
See https://bugs.eclipse.org/bugs/show_bug.cgi?id=281519
-----Original Message-----
From: eclipselink-dev-bounces@xxxxxxxxxxx
[mailto:eclipselink-dev-bounces@xxxxxxxxxxx] On Behalf Of Tom Ware
Sent: Friday, May 22, 2009 9:55 AM
To: Dev mailing list for Eclipse Persistence Services
Subject: Re: [eclipselink-dev] Tests don't compile in branch
1.1.2,checkouttrunk is not enough?
It would be a good idea to do the check for JUnit and provide an
appropriate
error message.
Please file a bug and prefix the subject with [Build].
At the moment we do not have a maven-based build. We do, however,
provide a
maven repository for those that want to consume EclipseLink through
maven.
-Tom
Sebastien Tardif wrote:
> Looks like I was too tired to think...
>
> I end-up putting the JUnit jar in the lib directory of the ant
> installation.
>
> I guess, if I expect having nothing to setup I should be using maven
> instead of ant, what are the difference between the two in term of
> functionalities. I mean I see we defined a pom.xml, so maybe maven is
> setup to replace ant and more automatic?
>
> A thing that could be done in the ANT script is to verify if the JUnit
> class can be found and if not output error messages like: "JUnit
classes
> not found. See http://wiki.eclipse.org/EclipseLink/Building";
>
> ANT task "available" seems appropriate for the task ->
> http://ant.apache.org/manual/CoreTasks/available.html
>
> Then can use fail ant task, which will use the property value
resulting
> of the available check.
>
> -----Original Message-----
> From: eclipselink-dev-bounces@xxxxxxxxxxx
> [mailto:eclipselink-dev-bounces@xxxxxxxxxxx] On Behalf Of Tom Ware
> Sent: Friday, May 22, 2009 8:47 AM
> To: Dev mailing list for Eclipse Persistence Services
> Subject: Re: [eclipselink-dev] Tests don't compile in branch 1.1.2,
> checkouttrunk is not enough?
>
> You will need a junit.lib variable. See "Build" on this page:
>
> http://wiki.eclipse.org/EclipseLink/Building
>
> Sebastien Tardif wrote:
>> Tests don't compile in branch 1.1.2
>>
>> Do I need something else than checkout trunk and run ant?
>>
>> C:\EclipseLinkSrc\br1.1.0\trunk\foundation\eclipselink.core.test\src
>> \org\eclipse\persistence\testing\framework\JUnitTestCase.java:102:
>> package junit
>> .framework does not exist
>> [javac] if
>> (!(junit.framework.TestCase.class.isAssignableFrom(junitT
>> estCaseClass))) {
>> [javac] ^
>> [javac] Note: Some input files use or override a deprecated API.
>> [javac] Note: Recompile with -Xlint:deprecation for details.
>> [javac] Note: Some input files use unchecked or unsafe
operations.
>> [javac] Note: Recompile with -Xlint:unchecked for details.
>> [javac] 100 errors
>>
>> BUILD FAILED
>> C:\EclipseLinkSrc\br1.1.0\trunk\build.xml:227: The following error
>> occurred whil
>> e executing this line:
>>
>
C:\EclipseLinkSrc\br1.1.0\trunk\foundation\eclipselink.core.test\build.x
>> ml:79: C
>> ompile failed; see the compiler error output for details.
>>
>> Total time: 49 seconds
>> C:\EclipseLinkSrc\br1.1.0\trunk>
>> _______________________________________________
>> eclipselink-dev mailing list
>> eclipselink-dev@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/eclipselink-dev
> _______________________________________________
> eclipselink-dev mailing list
> eclipselink-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/eclipselink-dev
> _______________________________________________
> eclipselink-dev mailing list
> eclipselink-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/eclipselink-dev
_______________________________________________
eclipselink-dev mailing list
eclipselink-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipselink-dev
