• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Eclipse Project References Property Page

 
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi,

What is Eclipse's Project References Property Page used for? This prop page is shown when viewing the project properties.

I've searched via Google, the Eclipse help docs, and this forum trying to find out how this prop page is useful, but I still don't understand why it exists. Here's what I know so far:

1) If I go to the Project Reference prop page and checkmark a Java project that's listed on this prop page, then an entry is placed into the .project file. Why is this useful? I don't know.

2) Even if I go to the Project Reference prop page and checkmark a Java project that's listed on this prop page, then I still get compiler errors when I try to import a class from a dependent project.
Eg, if projB attempts to import a class from projA, then I get compiler errors even if I go to projB's Project Reference prop page and checkmark "projA". To resolve the compiler errors, I actually need to add projA to projB's build path. Which again leaves me wondering... what is the Project References prop page useful for? And when I do add projA to projB's build path, then (strangely enough) projB's Project Ref prop page shows that projB remains unchecked. Shouldn't an explicit build path dependency on a project count as a project reference, and so automatically checkmark the dependency, projA?

3) If I go to the Project Properties page of a generic, non-Java project, then naturally I don't see the Java Build Path prop page... But the Project References prop page is still there... Could this mean that this prop page is intended only for generic, non-Java projects? If so, then again.. for what reason?

4) I've seen the Project References prop page in the context of web apps in some places, but the reasons for mentioning/using it weren't clear.

Very confused. Seeking clarification, please. I would greatly appreciate any help.

Thank you.

Cheers,
Will
reply
    Bookmark Topic Watch Topic
  • New Topic