Eclipse Community Forums: Java Development Tools (JDT) » Replace version of JUnit in Galileo with previous version from Ganymede?

Home » Language IDEs » Java Development Tools (JDT) » Replace version of JUnit in Galileo with previous version from Ganymede?

Show: Today's Messages :: Show Polls :: Message Navigator

Replace version of JUnit in Galileo with previous version from Ganymede? [message #375274]

Wed, 29 July 2009 18:54

Mike Norman

Messages: 35
Registered: July 2009

Member

Is there a way to 'downgrade' the version of JUnit4 shipped in Galileo?

Our internal use hasn't gone past JUnit 4.3.1 and the new
Galileo release has 4.5.0, which includes references to
'org.hamcrest.*', causing some problems Sad

Report message to a moderator

Re: Replace version of JUnit in Galileo with previous version from Ganymede? [message #407509 is a reply to message #375274]

Thu, 30 July 2009 06:57

Mauro Molinari

Messages: 285
Registered: July 2009

Senior Member

Mike Norman ha scritto:
> Is there a way to 'downgrade' the version of JUnit4 shipped in Galileo?
>
> Our internal use hasn't gone past JUnit 4.3.1 and the new
> Galileo release has 4.5.0, which includes references to
> 'org.hamcrest.*', causing some problems :(

Couldn't you simply replace the JUnit library from Eclipse 3.5 with your
JUnit 4.3.1 JAR in the project buildpath configuration?

Mauro.

Report message to a moderator

Re: Replace version of JUnit in Galileo with previous version from Ganymede? [message #412548 is a reply to message #375274]

Thu, 30 July 2009 09:08

Dani Megert

Messages: 3802
Registered: July 2009

Senior Member

Mike Norman wrote:
> Is there a way to 'downgrade' the version of JUnit4 shipped in Galileo?
>
> Our internal use hasn't gone past JUnit 4.3.1 and the new
> Galileo release has 4.5.0, which includes references to
> 'org.hamcrest.*', causing some problems :(
What problems?

Dani

Report message to a moderator

Re: Replace version of JUnit in Galileo with previous version from Ganymede? [message #424652 is a reply to message #412548]

Thu, 30 July 2009 13:28

Mike Norman

Messages: 35
Registered: July 2009

Member

Well. we have Ant build scripts that operate across all the project's modules - and these scripts don't 'know' anything about JUnit 4.5 (which includes references to the classes in org.hamcrest.*).
So, if you re-compile the classes external to the Eclipse IDE, then JUnit 4.3.1 references are compiled in; if the classes are re-compiled internal to Eclipse, then 4.5 references are compiled in.

In addition to org.hamcrest references, it appears that some assert APIs are not backwards-compatible (class linkage errors - different method signature)

Report message to a moderator

Re: Replace version of JUnit in Galileo with previous version from Ganymede? [message #430120 is a reply to message #424652]

Thu, 30 July 2009 15:30

Mauro Molinari

Messages: 285
Registered: July 2009

Senior Member

Mike Norman ha scritto:
> In addition to org.hamcrest references, it appears that some assert APIs
> are not backwards-compatible (class linkage errors - different method
> signature)

I think that your only problem is the latter one. There should be no
problems to compile against JUnit 4.3.1 or JUnit 4.5 and run using one
another if you don't use org.hamcrest.* classes.

For instance, for a long time we internally wrote tests using Eclipse
3.3/3.4 (so JUnit 4.3.1) while having configured our Ant script to use
JUnit 4.4.0. The only problem was to avoid the use of boxing/unboxing in
some cases, otherwise some code did compile against JUnit 4.3.1 but not
against JUnit 4.4.0, because of the introduction of new overloadings for
some assert methods.

Mauro.

Report message to a moderator

Previous Topic:	Ecliple copying plugins into project directory
Next Topic:	Strange message hover Enums

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Fri Apr 19 05:18:51 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter