| Referencing a project [message #148485] |
Thu, 23 October 2003 15:10  |
Eclipse User |
|
|
|
Originally posted by: Lamont_Gilbert.Rigidsoftware.com
On the projects page, their are 2 ways to choose an external project. 1
is adding it to your projects build path. I can figure what that does.
The other though is the last page called "Project References." What does
that do? Why does it list all projects in eclipse, while the build path
page only shows 1 available to be checked in my current project?
Thanks,
CL
|
|
|
| Re: Referencing a project [message #148496 is a reply to message #148485] |
Thu, 23 October 2003 15:19  |
| Eclipse User |
|
|
|
Originally posted by: Lamont_Gilbert.Rigidsoftware.com
On Thu, 23 Oct 2003 11:10:00 -0400, CL [dnoyeB] Gilbert wrote:
> On the projects page, their are 2 ways to choose an external project. 1
> is adding it to your projects build path. I can figure what that does.
> The other though is the last page called "Project References." What does
> that do? Why does it list all projects in eclipse, while the build path
> page only shows 1 available to be checked in my current project?
>
> Thanks,
>
>
> CL
I think I got it. First page is for compile time references. Last page is
for runtime references. So if you launch a runtime workbench, projects on
the last page that are checked will be launched into the workbench as
well.
Can anyone verify ths is true?
CL
|
|
|
| Re: Referencing a project [message #150443 is a reply to message #148496] |
Wed, 29 October 2003 00:02 |
| Eclipse User |
|
|
|
Originally posted by: John_Arthorne.oti.com_
Nope... unfortunately you're seeing a bit of an ugly side-effect of the
plug-in layering in Eclipse. The "Project References" is a generic
platform concept. It actually isn't used for much, other than computing
the default project build order. It was intended to have further uses
(such as automatically checking out referenced projects when you
checkout a project), but to make a long story short, the concept was too
generic to be useful in this way. The "Java Build Path" is a java
tooling concept, and it is used to specify build-time references.
Neither of these are used at runtime. When you add projects in the
"java build path", it will automatically update the "project references"
for you. In short, don't touch the "project references" preference page.
--
CL [dnoyeB] Gilbert wrote:
> On Thu, 23 Oct 2003 11:10:00 -0400, CL [dnoyeB] Gilbert wrote:
>
> I think I got it. First page is for compile time references. Last page is
> for runtime references. So if you launch a runtime workbench, projects on
> the last page that are checked will be launched into the workbench as
> well.
|
|
|
Powered by
FUDForum. Page generated in 0.05067 seconds
] 
Search
Help
Register
Login
Home
