|no build path [message #544883]
||Mon, 05 July 2010 16:46
| Tom Van Vleck
Registered: July 2009
On a test machine I am trying to convert software to use |
Eclipse 3.6 (Helios). The machine is running OSX 10.6.3.
I downloaded "Eclipse IDE for Java Developers" 64-bit Mac
package and installed it. Working on a copy of my 3.5
Installed Subclipse and javahl from open.collab.net.
Workspace showed up as empty so I imported everything from
the repo. One project of about 20 had build errors,
because it could not find classes provided by two other
projects. In "configure build path" on the failing project,
the needed projects do not appear as checkable in the "Add"
popup for the "required projects" window.
I looked at the supplying projects: I cannot configure
their build path because the "build path" menu item is not
provided when I right-click on these projects. "Properties"
for the projects to not have a build path item in the left
sidebar. Clicking on "Builders" shows none configured, and
the "Java Builder" is not offered as an option by the "New"
button. It looks like the designation of these projects as
"Java projects" has been lost in conversion to Helios, so
they don't supply classes to the project that needs them.
How can I make these supplying projects into Java projects
again, the way they are on 3.5?
|Re: no build path [message #545050 is a reply to message #544906]
||Tue, 06 July 2010 10:09
| David Wegener
Registered: July 2009
"Tom Van Vleck" <email@example.com> wrote in message |
> David Wegener <firstname.lastname@example.org> wrote:
>> On Mon, 2010-07-05 at 16:46 -0400, Tom Van Vleck wrote:
>> > How can I make these supplying projects into Java projects
>> > again, the way they are on 3.5?
>> I sounds like you are missing the .project file for the problem
>> projects. This file defines the Nature of the project (Java). Make
>> sure that you have include both the .project and the .classpath files
>> when you get the projects out of your repository.
> Thanks David, that was related to the problem.
> I did more web searching and found an answer: delete the
> project, leaving the files, and re-create it specifying
> that it is a Java project. This re-creates the .project
> correctly. (Checking in a .classpath file wouldn't work
> if different users of the repository have their storage
> laid out differently.)
Classpath Variables are provided to remove absolute path references in the
..classpath file so that you can check the .classpath files into your
repository. This file is an important piece of the project and should be
Powered by FUDForum
. Page generated in 2.43374 seconds