| Eclipse JDT acts different on Windows than Linux with jUnit, debugging and Ant [message #8943] |
Tue, 29 April 2003 13:40  |
Eclipse User |
|
|
|
Help. Im having some problems with a JDT project that acts different on
Windows than on
Linux 2.1.
I have a set of unit tests running using jUnit view in Eclipse. These
tests work flawlessly
in my Ant build.xml script from both Linux and Windows command line, in
the Ant
plug-in on Windows and Eclipse 2.1 Motif version running on RedHat Linux
7.3. They
fail on Windows XP using the inside Eclipse 2.1 jUnit plug-in and on
Linux the tests fail
in the Ant plug-in.
Im trying to determine what is wrong with the scripts, so I set a break
point in the script
to debug the problem. When I try to step into my library, I cannot do
this on Windows. I
can do this on the Linux box. All the source code is in CVS. I have
verified that both
projects are identical to the CVS repositories by using Team |
Synchronize with
Repository
I then deleted the project and checked it out again from CVS on both
platforms. Linux
version worked as before, the Windows version failed as before. I then
deleted my
..metadata directory on Windows machine to no avail. My next drastic step
was to delete
and reinstall Eclipse on Windows XP. I recreated all the projects from
CVS. It still failed
to step into the library! Im at a total loss why this works on Linux
and not Windows. Is
there something else that I have missed? I really want to work on the
Window. I am
connecting to Linux via remote X-Window session and this is incredibly
slow at times.
Next, I when I try to run the test target in my build.xml file. It works
on Windows and
Fails on Linux. On the Linux box, I am getting loader constraints
violated when linking
/org/w3c/dom/Document error. Im obviously getting an XML library that
I dont want.
What perplexes me why this error doesnt also happen on Window?
|
|
|
|
| Re: Eclipse JDT acts different on Windows than Linux with jUnit, debugging and Ant [message #9069 is a reply to message #8964] |
Tue, 29 April 2003 15:23  |
| Eclipse User |
|
|
|
Olivier:
I thought this might be problem, so I double checked to make sure that I was
indeed using Java 1.4.0 on linux. I also double checked the property settings
for Ant. In particular, I made sure that I knew what the classpath was set in
the Ant properties dialog box. I don't get an error when I used the Ant
within Eclipse on Windows, which what doesn't make any sense. I'm running
Java 1.4.1 on Windows XP. I am getting other bizarre problems on Windows with
jUnit and debugging that don't happen on Linux.
Regards,
Jeff
Olivier Thomann wrote:
> On Tue, 29 Apr 2003 13:40:34 -0400, Jeff Duska <Jeff.Duska@noaa.gov>
> wrote:
> >Next, I when I try to run the test target in my build.xml file. It works
> >on Windows and
> >Fails on Linux. On the Linux box, I am getting loader constraints
> >violated when linking
> >/org/w3c/dom/Document error. Im obviously getting an XML library that
> >I dont want.
> >What perplexes me why this error doesnt also happen on Window?
> You might have a conflict with the xerces library on Windows (JDK1.4?)
> and not on Linux (JDK1.3?).
> What is the failure on Windows?
> --
> Olivier
|
|
|
| Re: Eclipse JDT acts different on Windows than Linux with jUnit, debugging and Ant [message #9089 is a reply to message #9069] |
Tue, 29 April 2003 15:47 |
| Eclipse User |
|
|
|
Originally posted by: Olivier_Thomann.ca.ibm.comNOSPAM
On Tue, 29 Apr 2003 15:23:37 -0400, Jeff Duska <Jeff.Duska@noaa.gov>
wrote:
>I thought this might be problem, so I double checked to make sure that I was
>indeed using Java 1.4.0 on linux. I also double checked the property settings
>for Ant. In particular, I made sure that I knew what the classpath was set in
>the Ant properties dialog box. I don't get an error when I used the Ant
>within Eclipse on Windows, which what doesn't make any sense. I'm running
>Java 1.4.1 on Windows XP. I am getting other bizarre problems on Windows with
>jUnit and debugging that don't happen on Linux.
You didn't say what kind of error you get when it fails.
If you could isolate a small test case, please enter a bug report and
we will investigate. Depending on the stack trace you can enter it
against JDT/Core ou JDT/UI.
--
Olivier
|
|
|
Powered by
FUDForum. Page generated in 0.27431 seconds
Home