Bugzilla – Full Text Bug Listing
| Summary: | Could not find the main class: org.eclipse.ant.internal.launching.remote.InternalAntRunner. Program will exit. | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Beads Land-Trujillo <beads> | ||||||||
| Component: | Ant | Assignee: | Platform-Ant-Inbox <platform-ant-inbox> | ||||||||
| Status: | CLOSED DUPLICATE | QA Contact: | |||||||||
| Severity: | normal | ||||||||||
| Priority: | P3 | CC: | christian.meister, jpgariepy, Michael_Rennie, Olivier_Thomann, remy.suen | ||||||||
| Version: | 3.7 | ||||||||||
| Target Milestone: | --- | ||||||||||
| Hardware: | PC | ||||||||||
| OS: | Windows 7 | ||||||||||
| Whiteboard: | |||||||||||
| Attachments: |
|
||||||||||
|
Description
Beads Land-Trujillo
Move to Platform/Ant TY for moving to correct location. (In reply to comment #1) > Move to Platform/Ant (In reply to comment #0) > Fresh in stall of today's current Indigo release. What is the name of the file you downloaded? (In reply to comment #3) > (In reply to comment #0) > > Fresh in stall of today's current Indigo release. > > What is the name of the file you downloaded? eclipse-SDK-3.7-win32.zip (In reply to comment #0) > Steps to Reproduce: > 1. Configure Ant build.xml builder to run during clean operation. > 2. Run clean operation. Can you provide a test project that demonstrates the problem? I have many project builders set up in my workspace and cannot reproduce. Created attachment 199701 [details]
Build file
I assume this is what you mean by attaching a project.
The deploy task likewise throws the same error.
(In reply to comment #4) > (In reply to comment #3) > > (In reply to comment #0) > > > Fresh in stall of today's current Indigo release. > > > > What is the name of the file you downloaded? > > eclipse-SDK-3.7-win32.zip Rooting through the file system that came from said Zip file, I find org.apache.ant, but no org.eclipse.ant jars. Seems it wasn't part of the distribution. Where can obtain the correct file(s)? (In reply to comment #7) > (In reply to comment #4) > > (In reply to comment #3) > > > (In reply to comment #0) > > > > Fresh in stall of today's current Indigo release. > > > > > > What is the name of the file you downloaded? > > > > eclipse-SDK-3.7-win32.zip > > Rooting through the file system that came from said Zip file, I find > org.apache.ant, but no org.eclipse.ant jars. Seems it wasn't part of the > distribution. > > Where can obtain the correct file(s)? Correction, the files are there (just not as folders). So we're back to the error: "Could not find the main class" suggests an issue in the Manifest file. Marking as a dupe of bug 352131, same reported issue and that bug has an example project to reproduce the reported problem. *** This bug has been marked as a duplicate of bug 352131 *** (In reply to comment #9) > Marking as a dupe of bug 352131, same reported issue and that bug has an > example project to reproduce the reported problem. > > *** This bug has been marked as a duplicate of bug 352131 *** Bug 352131 (I have reported it) is a different issue. I don't have any problem "during a clean" but rather "after a clean". Consider remove "duplicate" field to avoid confusion or else explain how they are related. (In reply to comment #9) > Marking as a dupe of bug 352131, same reported issue and that bug has an > example project to reproduce the reported problem. > > *** This bug has been marked as a duplicate of bug 352131 *** Definitely not a duplicate. Issue is not that Ant fails to fire. Issue is that Ant consistently throws a Java exception when fired. The ultimate result (that Ant is unusable under Indigo) may be the same, but the behavior is different. Alright. Reopened. Can you provide the complete stack trace for the exception and an example project that produces the problem - not a build file but the complete Eclipse project with the configured builders. (In reply to comment #12) > Alright. Reopened. > > Can you provide the complete stack trace for the exception and an example > project that produces the problem - not a build file but the complete Eclipse > project with the configured builders. Happens in all projects, however the code from any of those projects is not something I'm going to upload. I'll create a new project with just the Ant file and the single file it is supposed to copy. Will upload shortly. Have no idea how to obtain stack trace. The error appears as a modal dialog box from the JVM. Created attachment 199858 [details]
Sample project that produces error
I attempted creating a project from scratch. However, in this case Ant tasks simply would not run, even from Ant view. No errors. Nothing.
So copied another project, ripped out all source code, just leaving file that "build" task is supposed to copy. Error still present.
Created attachment 199859 [details]
Error message
(In reply to comment #14) > Created attachment 199858 [details] > Sample project that produces error > > I attempted creating a project from scratch. However, in this case Ant tasks > simply would not run, even from Ant view. No errors. Nothing. > > So copied another project, ripped out all source code, just leaving file that > "build" task is supposed to copy. Error still present. So it appears this may be related to the other bug, insofar as I cannot get Ant to even run for new projects under Indigo, as opposed to getting an error when trying to use Ant in existing projects that ran without error in Helios. I had the same Issue Today but it wasnt an error. My Ant Home pointed to an old installation i deleted yesterday. A new Installation of the current indigo release did not solve the Problem. i went to preferences->ant->runtime klicked on the button 'ant home' and selected the folder eclipse->plugins->org.apache.ant* from my current eclipse installation. That solved this issue for me. (In reply to comment #17) > That solved this issue for me. This is sounding more and more like bug 101224. Beads, when you go to the Ant > Runtime (classpath tab) preference page what do you see under the Ant Home entry? (it should be Ant 1.8.2 given your build id). Christian, unless there is a specific need to explicitly point to a version of Ant, you can hit the Restore Defaults button on the page and Eclipse will automatically move to the latest version of Ant that comes bundled with your Eclipse install. (In reply to comment #18) > Beads, when you go to the Ant > > Runtime (classpath tab) preference page what do you see under the Ant Home > entry? (it should be Ant 1.8.2 given your build id). > I see 1.7.1. It's pointing to my old Eclipse Helios install's version of Ant. This would suggest that when I deleted Helios and installed Indigo, it was pointing at 1.7.1 jars that were no longer present. > Christian, unless there is a specific need to explicitly point to a version of > Ant, you can hit the Restore Defaults button on the page and Eclipse will > automatically move to the latest version of Ant that comes bundled with your > Eclipse install. So the issue is that Eclipse Indigo doesn't to do the "Restore Defaults" upgrade automatically when installed? (In reply to comment #18) > Christian, unless there is a specific need to explicitly point to a version of > Ant, you can hit the Restore Defaults button on the page and Eclipse will > automatically move to the latest version of Ant that comes bundled with your > Eclipse install. Well, yes and no. Restore Defaults does update Ant to use the current bundled install. However, all buttons but "Ant Home" remain greyed out (even after shutting down and restarting Eclipse). I realized this when, successfully running Ant (now that it was using the correct jar paths), I got an error that the scp component was not installed. I went back to Preference, and found that I couldn't "Add External Jar". At least, I couldn't until I explicitly reset "Ant Home" per Christian's instructions. Then the other buttons ungreyed and I was able to successfully get the jcraft plugin added. (Why again isn't this bundled in as an obvious must-have for server development?) (In reply to comment #20) > So the issue is that Eclipse Indigo doesn't to do the "Restore Defaults" > upgrade automatically when installed? No, when you set Ant home to be anything other than the default, you are, in effect telling us that you do not want to use the version of Ant that comes with Eclipse, so we never try to reset / modify the Ant Home preferences after that point. > Well, yes and no. Restore Defaults does update Ant to use the current bundled > install. However, all buttons but "Ant Home" remain greyed out (even after > shutting down and restarting Eclipse). > You have to select the part of the classpath you want to add the new entry to - keeping in mind that you cannot modify the 'Contributed Entries'. > (Why again isn't this bundled in as an obvious must-have for server > development?) You would have to take that up with Apache, Eclipse simply uses the release from them for our Ant support. I think to help people who forget that they have modified Ant Home, we should look at adding in some sanity checks - the main one being (and the cause of many dupe bugs) that Ant Home points to an invalid location after an upgrade. I am duping this bug against bug 101224 and will open a new bug to track the work for some sanity checks *** This bug has been marked as a duplicate of bug 101224 *** |