Home » Eclipse Projects » Eclipse Platform » Strange problem running ant
| Strange problem running ant [message #273480] |
Wed, 06 October 2004 15:05  |
Eclipse User |
|
|
|
Originally posted by: mike.metadata.com
Hi,
I'm hoping someone recognizes these symptoms and recalls what they did to
fix it. I have a workspace with 5 projects in it. I am running on
Windows XP SP2, Sun JDK 1.4.2_05, and Eclipse 3.0.1.
Each project has a build.xml that compiles and builds a jar file. There
is virtually no difference between the 5 build files. 4 of the projects
build fine. The 5th yields:
BUILD FAILED: C:\JavaDev\project5\build.xml:15: Unable to find a javac
compiler;
com.sun.tools.javac.Main is not on the classpath.
Perhaps JAVA_HOME does not point to the JDK
Of course, JAVA_HOME is set properly, by direct inspection, the fact that
the other 4 work, and building from the command line for the 5th project
works fine.
I've been through the Ant Build.. properties and the JRE is set for the
same JRE as the workspace. As near as I can tell, each project is using
identical Ant settings.
I've tried completely uninstalling and reinstalling the JDK and Eclipse,
as well as the .project file, to no avail.
Has anyone run across this? While it's not a showstopper, it certainly is
annoying, and could seriously hurt the acceptance of Eclipse and Java in
our workplace.
Thanks,
Mike
|
|
|
| Re: Strange problem running ant [message #273482 is a reply to message #273480] |
Wed, 06 October 2004 16:30  |
| Eclipse User |
|
|
|
When an Ant build cannot find a compiler this means it does not have a
tools.jar on the Ant runtime classpath.
I agree it is strange that 4 out of your 5 projects build successfully.
If JAVA_HOME points to a JDK install and a user has not removed the
tools.jar then we have a bug.
As well if Eclipse has been started with a JDK install and a user has not
explicitly removed the tools.jar, then we have a bug.
I have done quite a bit of testing in this area and believe we do not have a
bug in this area but I am happy to be shown incorrect :-) and will fix as
soon as possible.
You can add the tools.jar yourself to correct the problem.
An interesting test would be to delete the Ant launch configuration for the
buildfile and then recreate it to see if the tools.jar is found.
Thanks
Darins
"Mike" <mike@metadata.com> wrote in message news:ck1fln$8cu$1@eclipse.org...
> Hi,
>
> I'm hoping someone recognizes these symptoms and recalls what they did to
> fix it. I have a workspace with 5 projects in it. I am running on
> Windows XP SP2, Sun JDK 1.4.2_05, and Eclipse 3.0.1.
>
> Each project has a build.xml that compiles and builds a jar file. There
> is virtually no difference between the 5 build files. 4 of the projects
> build fine. The 5th yields:
>
> BUILD FAILED: C:\JavaDev\project5\build.xml:15: Unable to find a javac
> compiler;
> com.sun.tools.javac.Main is not on the classpath.
> Perhaps JAVA_HOME does not point to the JDK
>
> Of course, JAVA_HOME is set properly, by direct inspection, the fact that
> the other 4 work, and building from the command line for the 5th project
> works fine.
>
> I've been through the Ant Build.. properties and the JRE is set for the
> same JRE as the workspace. As near as I can tell, each project is using
> identical Ant settings.
>
> I've tried completely uninstalling and reinstalling the JDK and Eclipse,
> as well as the .project file, to no avail.
>
> Has anyone run across this? While it's not a showstopper, it certainly is
> annoying, and could seriously hurt the acceptance of Eclipse and Java in
> our workplace.
>
> Thanks,
> Mike
>
|
|
|
| Re: Strange problem running ant [message #273492 is a reply to message #273480] |
Wed, 06 October 2004 17:41 |
| Eclipse User |
|
|
|
Originally posted by: bandrews.NO_SPAM_bphnx.com
"and the JRE is set for the same JRE as the workspace."
This may not have anything to do with your problem, but I would not do
this because Ant has memory leaks. Notice how the memory continues to grow
everytime you do a build and is never released. Try setting it to
"Separate JRE", but you will have to change javaw to java to get it work.
Why? I don't know, but that is what I had to do.
Again, I don't know if this will help, but maybe try it anyway.
Barry
Mike wrote:
> Hi,
> I'm hoping someone recognizes these symptoms and recalls what they did to
> fix it. I have a workspace with 5 projects in it. I am running on
> Windows XP SP2, Sun JDK 1.4.2_05, and Eclipse 3.0.1.
> Each project has a build.xml that compiles and builds a jar file. There
> is virtually no difference between the 5 build files. 4 of the projects
> build fine. The 5th yields:
> BUILD FAILED: C:JavaDevproject5build.xml:15: Unable to find a javac
> compiler;
> com.sun.tools.javac.Main is not on the classpath.
> Perhaps JAVA_HOME does not point to the JDK
> Of course, JAVA_HOME is set properly, by direct inspection, the fact that
> the other 4 work, and building from the command line for the 5th project
> works fine.
> I've been through the Ant Build.. properties and the JRE is set for the
> same JRE as the workspace. As near as I can tell, each project is using
> identical Ant settings.
> I've tried completely uninstalling and reinstalling the JDK and Eclipse,
> as well as the .project file, to no avail.
> Has anyone run across this? While it's not a showstopper, it certainly is
> annoying, and could seriously hurt the acceptance of Eclipse and Java in
> our workplace.
> Thanks,
> Mike
|
|
|
| Re: Strange problem running ant [message #273498 is a reply to message #273482] |
Wed, 06 October 2004 18:44 |
| Eclipse User |
|
|
|
Originally posted by: mike.metadata.com
In the workbench preferences under "Java > Installed JREs" both the
default JRE found during Eclipses initial startup and the JDK which was
added using the "Search" button have the following libraries: rt,
sunrsasign, jsse, jce, charsets, dnsns, ldapsec, localedata,
sunjce_provider. Unchecking the "Use default system libraries" option and
adding tools.jar to either results in the same message.
YES! The second idea worked. I didn't think of deleting the the "Ant
Build" Configurations from the "External Tools.." option. Worked like a
charm!
Thanks! Breathing much easier now.
Darin Swanson wrote:
> When an Ant build cannot find a compiler this means it does not have a
> tools.jar on the Ant runtime classpath.
> I agree it is strange that 4 out of your 5 projects build successfully.
> If JAVA_HOME points to a JDK install and a user has not removed the
> tools.jar then we have a bug.
> As well if Eclipse has been started with a JDK install and a user has not
> explicitly removed the tools.jar, then we have a bug.
> I have done quite a bit of testing in this area and believe we do not have a
> bug in this area but I am happy to be shown incorrect :-) and will fix as
> soon as possible.
> You can add the tools.jar yourself to correct the problem.
> An interesting test would be to delete the Ant launch configuration for the
> buildfile and then recreate it to see if the tools.jar is found.
> Thanks
> Darins
|
|
|
| Re: Strange problem running ant [message #273500 is a reply to message #273492] |
Wed, 06 October 2004 18:46 |
| Eclipse User |
|
|
|
Originally posted by: mike.metadata.com
Thanks for info Barry. This did work for me, and I'll switch my
configurations over to get rid of the memory leaks.
bandrews wrote:
> "and the JRE is set for the same JRE as the workspace."
> This may not have anything to do with your problem, but I would not do
> this because Ant has memory leaks. Notice how the memory continues to grow
> everytime you do a build and is never released. Try setting it to
> "Separate JRE", but you will have to change javaw to java to get it work.
> Why? I don't know, but that is what I had to do.
> Again, I don't know if this will help, but maybe try it anyway.
> Barry
> Mike wrote:
> > Hi,
> > I'm hoping someone recognizes these symptoms and recalls what they did to
> > fix it. I have a workspace with 5 projects in it. I am running on
> > Windows XP SP2, Sun JDK 1.4.2_05, and Eclipse 3.0.1.
> > Each project has a build.xml that compiles and builds a jar file. There
> > is virtually no difference between the 5 build files. 4 of the projects
> > build fine. The 5th yields:
> > BUILD FAILED: C:JavaDevproject5build.xml:15: Unable to find a javac
> > compiler;
> > com.sun.tools.javac.Main is not on the classpath.
> > Perhaps JAVA_HOME does not point to the JDK
> > Of course, JAVA_HOME is set properly, by direct inspection, the fact that
> > the other 4 work, and building from the command line for the 5th project
> > works fine.
> > I've been through the Ant Build.. properties and the JRE is set for the
> > same JRE as the workspace. As near as I can tell, each project is using
> > identical Ant settings.
> > I've tried completely uninstalling and reinstalling the JDK and Eclipse,
> > as well as the .project file, to no avail.
> > Has anyone run across this? While it's not a showstopper, it certainly is
> > annoying, and could seriously hurt the acceptance of Eclipse and Java in
> > our workplace.
> > Thanks,
> > Mike
|
|
|
| Re: Strange problem running ant [message #273508 is a reply to message #273500] |
Wed, 06 October 2004 21:30 |
| Eclipse User |
|
|
|
Futher note: new Ant launch configurations created in 3.0 and on have the
"Separate JRE" set as the default.
Darins
"Mike" <mike@metadata.com> wrote in message news:ck1sks$v9h$1@eclipse.org...
> Thanks for info Barry. This did work for me, and I'll switch my
> configurations over to get rid of the memory leaks.
>
> bandrews wrote:
>
>> "and the JRE is set for the same JRE as the workspace."
>
>> This may not have anything to do with your problem, but I would not do
>> this because Ant has memory leaks. Notice how the memory continues to
>> grow
>> everytime you do a build and is never released. Try setting it to
>> "Separate JRE", but you will have to change javaw to java to get it work.
>> Why? I don't know, but that is what I had to do.
>
>> Again, I don't know if this will help, but maybe try it anyway.
>
>> Barry
>
>
>
>
>
>> Mike wrote:
>
>> > Hi,
>
>> > I'm hoping someone recognizes these symptoms and recalls what they did
>> > to
>> > fix it. I have a workspace with 5 projects in it. I am running on
>> > Windows XP SP2, Sun JDK 1.4.2_05, and Eclipse 3.0.1.
>
>> > Each project has a build.xml that compiles and builds a jar file.
>> > There
>> > is virtually no difference between the 5 build files. 4 of the
>> > projects
>> > build fine. The 5th yields:
>
>> > BUILD FAILED: C:JavaDevproject5build.xml:15: Unable to find a javac
>> > compiler;
>> > com.sun.tools.javac.Main is not on the classpath.
>> > Perhaps JAVA_HOME does not point to the JDK
>
>> > Of course, JAVA_HOME is set properly, by direct inspection, the fact
>> > that
>> > the other 4 work, and building from the command line for the 5th
>> > project
>> > works fine.
>
>> > I've been through the Ant Build.. properties and the JRE is set for the
>> > same JRE as the workspace. As near as I can tell, each project is
>> > using
>> > identical Ant settings.
>
>> > I've tried completely uninstalling and reinstalling the JDK and
>> > Eclipse,
>> > as well as the .project file, to no avail.
>
>> > Has anyone run across this? While it's not a showstopper, it certainly
>> > is
>> > annoying, and could seriously hurt the acceptance of Eclipse and Java
>> > in
>> > our workplace.
>
>> > Thanks,
>> > Mike
>
>
|
|
|
| Re: Strange problem running ant [message #273548 is a reply to message #273508] |
Thu, 07 October 2004 09:14 |
| Eclipse User |
|
|
|
Originally posted by: bandrews.NO_SPAM_bphnx.com
I don't think so. I have 3.0 and it was not the default. Maybe 3.0.1?
Darin Swanson wrote:
> Futher note: new Ant launch configurations created in 3.0 and on have the
> "Separate JRE" set as the default.
> Darins
> "Mike" <mike@metadata.com> wrote in message news:ck1sks$v9h$1@eclipse.org...
> > Thanks for info Barry. This did work for me, and I'll switch my
> > configurations over to get rid of the memory leaks.
> >
> > bandrews wrote:
> >
> >> "and the JRE is set for the same JRE as the workspace."
> >
> >> This may not have anything to do with your problem, but I would not do
> >> this because Ant has memory leaks. Notice how the memory continues to
> >> grow
> >> everytime you do a build and is never released. Try setting it to
> >> "Separate JRE", but you will have to change javaw to java to get it work.
> >> Why? I don't know, but that is what I had to do.
> >
> >> Again, I don't know if this will help, but maybe try it anyway.
> >
> >> Barry
> >
> >
> >
> >
> >
> >> Mike wrote:
> >
> >> > Hi,
> >
> >> > I'm hoping someone recognizes these symptoms and recalls what they did
> >> > to
> >> > fix it. I have a workspace with 5 projects in it. I am running on
> >> > Windows XP SP2, Sun JDK 1.4.2_05, and Eclipse 3.0.1.
> >
> >> > Each project has a build.xml that compiles and builds a jar file.
> >> > There
> >> > is virtually no difference between the 5 build files. 4 of the
> >> > projects
> >> > build fine. The 5th yields:
> >
> >> > BUILD FAILED: C:JavaDevproject5build.xml:15: Unable to find a javac
> >> > compiler;
> >> > com.sun.tools.javac.Main is not on the classpath.
> >> > Perhaps JAVA_HOME does not point to the JDK
> >
> >> > Of course, JAVA_HOME is set properly, by direct inspection, the fact
> >> > that
> >> > the other 4 work, and building from the command line for the 5th
> >> > project
> >> > works fine.
> >
> >> > I've been through the Ant Build.. properties and the JRE is set for the
> >> > same JRE as the workspace. As near as I can tell, each project is
> >> > using
> >> > identical Ant settings.
> >
> >> > I've tried completely uninstalling and reinstalling the JDK and
> >> > Eclipse,
> >> > as well as the .project file, to no avail.
> >
> >> > Has anyone run across this? While it's not a showstopper, it certainly
> >> > is
> >> > annoying, and could seriously hurt the acceptance of Eclipse and Java
> >> > in
> >> > our workplace.
> >
> >> > Thanks,
> >> > Mike
> >
> >
|
|
|
| Re: Strange problem running ant [message #273561 is a reply to message #273548] |
Thu, 07 October 2004 12:36 |
| Eclipse User |
|
|
|
No 3.0
Are you sure you are not confusing External tool builders that launch an Ant
build and a "normal" Ant build?
External tool builders by default still run in the same JRE
Normal Ant builds by default run in a separate JRE
Darins
"bandrews" <bandrews@NO_SPAM_bphnx.com> wrote in message
news:ck3fer$icp$1@eclipse.org...
>I don't think so. I have 3.0 and it was not the default. Maybe 3.0.1?
>
>
> Darin Swanson wrote:
>
>> Futher note: new Ant launch configurations created in 3.0 and on have the
>> "Separate JRE" set as the default.
>
>> Darins
>
>> "Mike" <mike@metadata.com> wrote in message
>> news:ck1sks$v9h$1@eclipse.org...
>> > Thanks for info Barry. This did work for me, and I'll switch my
>> > configurations over to get rid of the memory leaks.
>> >
>> > bandrews wrote:
>> >
>> >> "and the JRE is set for the same JRE as the workspace."
>> >
>> >> This may not have anything to do with your problem, but I would not do
>> >> this because Ant has memory leaks. Notice how the memory continues to
>> >> grow
>> >> everytime you do a build and is never released. Try setting it to
>> >> "Separate JRE", but you will have to change javaw to java to get it
>> >> work.
>> >> Why? I don't know, but that is what I had to do.
>> >
>> >> Again, I don't know if this will help, but maybe try it anyway.
>> >
>> >> Barry
>> >
>> >
>> >
>> >
>> >
>> >> Mike wrote:
>> >
>> >> > Hi,
>> >
>> >> > I'm hoping someone recognizes these symptoms and recalls what they
>> >> > did
>> >> > to
>> >> > fix it. I have a workspace with 5 projects in it. I am running on
>> >> > Windows XP SP2, Sun JDK 1.4.2_05, and Eclipse 3.0.1.
>> >
>> >> > Each project has a build.xml that compiles and builds a jar file.
>> >> > There
>> >> > is virtually no difference between the 5 build files. 4 of the
>> >> > projects
>> >> > build fine. The 5th yields:
>> >
>> >> > BUILD FAILED: C:JavaDevproject5build.xml:15: Unable to find a javac
>> >> > compiler;
>> >> > com.sun.tools.javac.Main is not on the classpath.
>> >> > Perhaps JAVA_HOME does not point to the JDK
>> >
>> >> > Of course, JAVA_HOME is set properly, by direct inspection, the fact
>> >> > that
>> >> > the other 4 work, and building from the command line for the 5th
>> >> > project
>> >> > works fine.
>> >
>> >> > I've been through the Ant Build.. properties and the JRE is set for
>> >> > the
>> >> > same JRE as the workspace. As near as I can tell, each project is
>> >> > using
>> >> > identical Ant settings.
>> >
>> >> > I've tried completely uninstalling and reinstalling the JDK and
>> >> > Eclipse,
>> >> > as well as the .project file, to no avail.
>> >
>> >> > Has anyone run across this? While it's not a showstopper, it
>> >> > certainly
>> >> > is
>> >> > annoying, and could seriously hurt the acceptance of Eclipse and
>> >> > Java
>> >> > in
>> >> > our workplace.
>> >
>> >> > Thanks,
>> >> > Mike
>> >
>> >
>
>
|
|
|
| Re: Strange problem running ant [message #273568 is a reply to message #273561] |
Thu, 07 October 2004 11:45 |
| Eclipse User |
|
|
|
Originally posted by: bandrews.NO_SPAM_bphnx.com
Hmmm... Could be. Not sure what you mean by a "normal" Ant build. Yes, I
have a builder defined for a project which launches Ant. This is different
than the normal way?
thanks,
B
Darin Swanson wrote:
> No 3.0
> Are you sure you are not confusing External tool builders that launch an Ant
> build and a "normal" Ant build?
> External tool builders by default still run in the same JRE
> Normal Ant builds by default run in a separate JRE
> Darins
> "bandrews" <bandrews@NO_SPAM_bphnx.com> wrote in message
> news:ck3fer$icp$1@eclipse.org...
> >I don't think so. I have 3.0 and it was not the default. Maybe 3.0.1?
> >
> >
> > Darin Swanson wrote:
> >
> >> Futher note: new Ant launch configurations created in 3.0 and on have the
> >> "Separate JRE" set as the default.
> >
> >> Darins
> >
> >> "Mike" <mike@metadata.com> wrote in message
> >> news:ck1sks$v9h$1@eclipse.org...
> >> > Thanks for info Barry. This did work for me, and I'll switch my
> >> > configurations over to get rid of the memory leaks.
> >> >
> >> > bandrews wrote:
> >> >
> >> >> "and the JRE is set for the same JRE as the workspace."
> >> >
> >> >> This may not have anything to do with your problem, but I would not do
> >> >> this because Ant has memory leaks. Notice how the memory continues to
> >> >> grow
> >> >> everytime you do a build and is never released. Try setting it to
> >> >> "Separate JRE", but you will have to change javaw to java to get it
> >> >> work.
> >> >> Why? I don't know, but that is what I had to do.
> >> >
> >> >> Again, I don't know if this will help, but maybe try it anyway.
> >> >
> >> >> Barry
> >> >
> >> >
> >> >
> >> >
> >> >
> >> >> Mike wrote:
> >> >
> >> >> > Hi,
> >> >
> >> >> > I'm hoping someone recognizes these symptoms and recalls what they
> >> >> > did
> >> >> > to
> >> >> > fix it. I have a workspace with 5 projects in it. I am running on
> >> >> > Windows XP SP2, Sun JDK 1.4.2_05, and Eclipse 3.0.1.
> >> >
> >> >> > Each project has a build.xml that compiles and builds a jar file.
> >> >> > There
> >> >> > is virtually no difference between the 5 build files. 4 of the
> >> >> > projects
> >> >> > build fine. The 5th yields:
> >> >
> >> >> > BUILD FAILED: C:JavaDevproject5build.xml:15: Unable to find a javac
> >> >> > compiler;
> >> >> > com.sun.tools.javac.Main is not on the classpath.
> >> >> > Perhaps JAVA_HOME does not point to the JDK
> >> >
> >> >> > Of course, JAVA_HOME is set properly, by direct inspection, the fact
> >> >> > that
> >> >> > the other 4 work, and building from the command line for the 5th
> >> >> > project
> >> >> > works fine.
> >> >
> >> >> > I've been through the Ant Build.. properties and the JRE is set for
> >> >> > the
> >> >> > same JRE as the workspace. As near as I can tell, each project is
> >> >> > using
> >> >> > identical Ant settings.
> >> >
> >> >> > I've tried completely uninstalling and reinstalling the JDK and
> >> >> > Eclipse,
> >> >> > as well as the .project file, to no avail.
> >> >
> >> >> > Has anyone run across this? While it's not a showstopper, it
> >> >> > certainly
> >> >> > is
> >> >> > annoying, and could seriously hurt the acceptance of Eclipse and
> >> >> > Java
> >> >> > in
> >> >> > our workplace.
> >> >
> >> >> > Thanks,
> >> >> > Mike
> >> >
> >> >
> >
> >
|
|
|
| Re: Strange problem running ant [message #273581 is a reply to message #273568] |
Thu, 07 October 2004 13:22 |
| Eclipse User |
|
|
|
Only in that the default settings when the launch configuration is first
created are different.
"normal" just means an Ant build that is not triggered as the result of an
external tool builder.
Darins
"bandrews" <bandrews@NO_SPAM_bphnx.com> wrote in message
news:ck3o9u$6qs$1@eclipse.org...
> Hmmm... Could be. Not sure what you mean by a "normal" Ant build. Yes, I
> have a builder defined for a project which launches Ant. This is different
> than the normal way?
>
>
> thanks,
>
> B
>
> Darin Swanson wrote:
>
>> No 3.0
>> Are you sure you are not confusing External tool builders that launch an
>> Ant
>> build and a "normal" Ant build?
>
>> External tool builders by default still run in the same JRE
>> Normal Ant builds by default run in a separate JRE
>
>> Darins
>
>> "bandrews" <bandrews@NO_SPAM_bphnx.com> wrote in message
>> news:ck3fer$icp$1@eclipse.org...
>> >I don't think so. I have 3.0 and it was not the default. Maybe 3.0.1?
>> >
>> >
>> > Darin Swanson wrote:
>> >
>> >> Futher note: new Ant launch configurations created in 3.0 and on have
>> >> the
>> >> "Separate JRE" set as the default.
>> >
>> >> Darins
>> >
>> >> "Mike" <mike@metadata.com> wrote in message
>> >> news:ck1sks$v9h$1@eclipse.org...
>> >> > Thanks for info Barry. This did work for me, and I'll switch my
>> >> > configurations over to get rid of the memory leaks.
>> >> >
>> >> > bandrews wrote:
>> >> >
>> >> >> "and the JRE is set for the same JRE as the workspace."
>> >> >
>> >> >> This may not have anything to do with your problem, but I would not
>> >> >> do
>> >> >> this because Ant has memory leaks. Notice how the memory continues
>> >> >> to
>> >> >> grow
>> >> >> everytime you do a build and is never released. Try setting it to
>> >> >> "Separate JRE", but you will have to change javaw to java to get it
>> >> >> work.
>> >> >> Why? I don't know, but that is what I had to do.
>> >> >
>> >> >> Again, I don't know if this will help, but maybe try it anyway.
>> >> >
>> >> >> Barry
>> >> >
>> >> >
>> >> >
>> >> >
>> >> >
>> >> >> Mike wrote:
>> >> >
>> >> >> > Hi,
>> >> >
>> >> >> > I'm hoping someone recognizes these symptoms and recalls what
>> >> >> > they
>> >> >> > did
>> >> >> > to
>> >> >> > fix it. I have a workspace with 5 projects in it. I am running
>> >> >> > on
>> >> >> > Windows XP SP2, Sun JDK 1.4.2_05, and Eclipse 3.0.1.
>> >> >
>> >> >> > Each project has a build.xml that compiles and builds a jar file.
>> >> >> > There
>> >> >> > is virtually no difference between the 5 build files. 4 of the
>> >> >> > projects
>> >> >> > build fine. The 5th yields:
>> >> >
>> >> >> > BUILD FAILED: C:JavaDevproject5build.xml:15: Unable to find a
>> >> >> > javac
>> >> >> > compiler;
>> >> >> > com.sun.tools.javac.Main is not on the classpath.
>> >> >> > Perhaps JAVA_HOME does not point to the JDK
>> >> >
>> >> >> > Of course, JAVA_HOME is set properly, by direct inspection, the
>> >> >> > fact
>> >> >> > that
>> >> >> > the other 4 work, and building from the command line for the 5th
>> >> >> > project
>> >> >> > works fine.
>> >> >
>> >> >> > I've been through the Ant Build.. properties and the JRE is set
>> >> >> > for
>> >> >> > the
>> >> >> > same JRE as the workspace. As near as I can tell, each project
>> >> >> > is
>> >> >> > using
>> >> >> > identical Ant settings.
>> >> >
>> >> >> > I've tried completely uninstalling and reinstalling the JDK and
>> >> >> > Eclipse,
>> >> >> > as well as the .project file, to no avail.
>> >> >
>> >> >> > Has anyone run across this? While it's not a showstopper, it
>> >> >> > certainly
>> >> >> > is
>> >> >> > annoying, and could seriously hurt the acceptance of Eclipse and
>> >> >> > Java
>> >> >> > in
>> >> >> > our workplace.
>> >> >
>> >> >> > Thanks,
>> >> >> > Mike
>> >> >
>> >> >
>> >
>> >
>
>
|
|
|
Goto Forum:
Current Time: Sat May 10 17:10:53 EDT 2025
Powered by FUDForum. Page generated in 0.04708 seconds |
Home