Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Newcomers » Newcomers » no build path
no build path [message #544883] Mon, 05 July 2010 20:46 Go to next message
Tom Van Vleck is currently offline Tom Van VleckFriend
Messages: 16
Registered: July 2009
Junior Member
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
workspace.

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 #544899 is a reply to message #544883] Mon, 05 July 2010 23:17 Go to previous messageGo to next message
David Wegener is currently offline David WegenerFriend
Messages: 1348
Registered: July 2009
Senior Member
On Mon, 2010-07-05 at 16:46 -0400, Tom Van Vleck wrote:
> 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
> workspace.
>
> 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?
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.
Re: no build path [message #544906 is a reply to message #544899] Tue, 06 July 2010 02:35 Go to previous messageGo to next message
Tom Van Vleck is currently offline Tom Van VleckFriend
Messages: 16
Registered: July 2009
Junior Member
David Wegener <dpwegener@gmail.com> 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.)
Re: no build path [message #545050 is a reply to message #544906] Tue, 06 July 2010 14:09 Go to previous message
David Wegener is currently offline David WegenerFriend
Messages: 1348
Registered: July 2009
Senior Member
"Tom Van Vleck" <thvv@multicians.org> wrote in message
news:thvv-3D9B49.22354205072010@news.eclipse.org...
> David Wegener <dpwegener@gmail.com> 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
checked in.
Previous Topic:Install visual editor
Next Topic:obfuscate4e help
Goto Forum:
  


Current Time: Sat Nov 22 21:40:50 GMT 2014

Powered by FUDForum. Page generated in 0.03046 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software