Eclipse Community Forums: Newcomers

Home » Newcomers » Newcomers » Managing projects

Wed, 31 August 2005 16:19

Eclipse User

Originally posted by: fgeck.optonline.net

What is the philosophy or design of how Eclipse uses/manages projects? I
have many packages that I developed using another IDE and wanted to start
using Eclipse. Been having a problem getting this to work and found
something that might make it difficult for me to do what I want to do
(i.e. Eclipse does not allow for project location overlaps). First what
does that really mean in plain English location overlap?

Any way this is what I currently have and have multiple projects using the
other IDE one for each package

codebase
codebase/subsystem1 also a package and a separate main (package name =
subsystem1)
codebase/subsystem2 also a package and a separate main
codebase/subsystem3 also a package and a separate main
codebase /common
codebase /common/util_package1 (package name =common.package1)
codebase /common/util_package2
codebase /common/util_package3

Basically say I have 3 stand alone executable systems that make use of a
number of common utility packages. How do I get eclipse to manage this
all for me? Do I make one over all project? Then how do I execute and
test each subsystem? If I create 1 per package what would be the values
for each given this directory structure as I can seem to get eclipe to do
what I want.

Project name=
Workspace=
Package name= that I think I know using current names but does not seem to
work

Thanks,

Frank

Re: Managing projects [message #98824 is a reply to message #98794]

Wed, 31 August 2005 22:06

Eclipse User

Originally posted by: wegener.cboenospam.com

Frank wrote:
> What is the philosophy or design of how Eclipse uses/manages projects?
> I have many packages that I developed using another IDE and wanted to
> start using Eclipse. Been having a problem getting this to work and
> found something that might make it difficult for me to do what I want to
> do (i.e. Eclipse does not allow for project location overlaps). First
> what does that really mean in plain English location overlap?
>
> Any way this is what I currently have and have multiple projects using
> the other IDE one for each package
>
> codebase
> codebase/subsystem1 also a package and a separate main (package name =
> subsystem1)
> codebase/subsystem2 also a package and a separate main
> codebase/subsystem3 also a package and a separate main
> codebase /common
> codebase /common/util_package1 (package name =common.package1)
> codebase /common/util_package2
> codebase /common/util_package3
>
> Basically say I have 3 stand alone executable systems that make use of a
> number of common utility packages. How do I get eclipse to manage this
> all for me? Do I make one over all project? Then how do I execute and
> test each subsystem? If I create 1 per package what would be the values
> for each given this directory structure as I can seem to get eclipe to
> do what I want.
>
> Project name=
> Workspace=
> Package name= that I think I know using current names but does not seem
> to work
>
> Thanks,
>
> Frank
>

In Eclipse, 2 projects overlap if they have any filesystem elements in
common. A project cannot be in the subdirectory of another project.
Using your sample directory hierarchy, you couldn't have projects
created at both codebase/common and codebase/common/uitl_package1.

Not knowing exactly how you use the various different projects/packages,
it's hard to give an exact way to lay them out. You could create a
single project rooted at codebase. You could create a separate project
for each project (codebase/subsystem1, codebase/subsystem2,
codebase/subsystem3) and one project for common at codebase/common. If
you wanted to keep each util package as a separate project, you could
create them at codebase/common/util_package1 etc.

Eclipse also has several advanced project layout using linked resources.
Have you looked at the Java Development Users Guide in Help? In the
Getting Started section, there is a Project Configuration Tutorial that
discusses different project layouts and how you can manage them.

Re: Managing projects [message #98854 is a reply to message #98824]

Thu, 01 September 2005 08:00

Eclipse User

Originally posted by: ns_dkerber.ns_WarrenRogersAssociates.com

In article <df5nne$qs1$1@news.eclipse.org>, wegener@cboenospam.com
says...
> Frank wrote:

....

> In Eclipse, 2 projects overlap if they have any filesystem elements in
> common.

This seems to me to be an unnecessary restriction.

> A project cannot be in the subdirectory of another project.
> Using your sample directory hierarchy, you couldn't have projects
> created at both codebase/common and codebase/common/uitl_package1.
>
> Not knowing exactly how you use the various different projects/packages,
> it's hard to give an exact way to lay them out. You could create a
> single project rooted at codebase. You could create a separate project
> for each project (codebase/subsystem1, codebase/subsystem2,
> codebase/subsystem3) and one project for common at codebase/common. If

This is the way I do mine: the common library is its own project (as an
"Other" project), and the others reference it in their project
properties; they are "Dynamic Web Projects".

....

> Eclipse also has several advanced project layout using linked resources.
> Have you looked at the Java Development Users Guide in Help? In the
> Getting Started section, there is a Project Configuration Tutorial that
> discusses different project layouts and how you can manage them.

--
Remove the ns_ from if replying by e-mail (but keep posts in the
newsgroups if possible).

Re: Managing projects [message #98911 is a reply to message #98824]

Thu, 01 September 2005 12:33

Eclipse User

Originally posted by: fgeck.optonline.net

That tutorial seems perfect if I could find it. Searched the net and the
Eclipse site and the articles section etc where did they hide it on me?

Thanks,

Frank

Re: Managing projects [message #98925 is a reply to message #98824]

Thu, 01 September 2005 12:50

Eclipse User

Originally posted by: fgeck.optonline.net

Well I thought I tried to lay out what I was trying to do/duplicated what
I had done in another IDE. I have 3 subsystems that should be totally
separate from one another i.e. their own packages and own mains etc.

Then I have a bunch of libraries/utilities. I have separate ones I do not
want 1 big one but smaller ones that are their own separate packages. But
would share a common package name like common.util_package1 ,
common.util_Package2 etc

But when you have a package path like I do and then want to use Eclipse
given its Project name, workspace etc having trouble getting it setup
correctly for an existing layout without it wanting to make another
common/Util_package1 under the existing codebase/common/util_package1 i.e.
been getting codebase/common/util_package1/common/util_package1

Its an issue of getting directories and projects/packages to line up with
an existing directory structure.

Frank

Re: Managing projects [message #99017 is a reply to message #98911]

Thu, 01 September 2005 18:20

Eclipse User

Originally posted by: wegener.cboenospam.com

Frank wrote:

> That tutorial seems perfect if I could find it. Searched the net and the
> Eclipse site and the articles section etc where did they hide it on me?

> Thanks,

> Frank

It is in the Help that ships with Eclipse. Help->Help Contents. In the
window that opens up, select Java Development User Guide. Click the + by
Getting Started. Click the + by Project Configuration Tutorial.

Re: Managing projects [message #99784 is a reply to message #99017]

Tue, 06 September 2005 11:58

Eclipse User

Originally posted by: eclipse3.rizzoweb.com

Dave Wegener wrote:
> Frank wrote:
>
>> That tutorial seems perfect if I could find it. Searched the net and
>> the Eclipse site and the articles section etc where did they hide it
>> on me?
>
>
>> Thanks,
>
>
>> Frank
>
>
> It is in the Help that ships with Eclipse. Help->Help Contents. In the
> window that opens up, select Java Development User Guide. Click the +
> by Getting Started. Click the + by Project Configuration Tutorial.
>

One other piece of advice - include some context (quote previous
messages) in your replies. There are 100+ messages every day on these
groups, and we can't always remember what was said in a particular thread.

Eric

Previous Topic:	[java] external libraries in .jar files
Next Topic:	Controls

Goto Forum:

-=] Back to Top [=-

Current Time: Fri Jul 18 23:45:11 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter