Eclipse Community Forums: Java Development Tools (JDT)

Home » Language IDEs » Java Development Tools (JDT) » Opinions on Project Structuring

Opinions on Project Structuring [message #50158]

Thu, 05 June 2003 09:13

Eclipse User

Originally posted by: ahumphr.ZAPgmx.net

I would like to benefit from your experience structuring large projects in
the workspace. I have inherited a tar ball of a large Java/JSP/shell-script
system which consists of many individual programs, pages, modules and 3rd
party libraries.

How should one go about structuring this tangeled mess?

Should each program become a project in it own right? Or should I create one
project and many package trees?

How would I structure the build/ouput directories? Is there a way to make
projects contain sub-projects?

A

Re: Opinions on Project Structuring [message #50445 is a reply to message #50158]

Thu, 05 June 2003 11:28

Eclipse User

Aidan Mark wrote:
> I would like to benefit from your experience structuring large projects in
> the workspace. I have inherited a tar ball of a large Java/JSP/shell-script
> system which consists of many individual programs, pages, modules and 3rd
> party libraries.
>
> How should one go about structuring this tangeled mess?
>
> Should each program become a project in it own right? Or should I create one
> project and many package trees?
>
> How would I structure the build/ouput directories? Is there a way to make
> projects contain sub-projects?

Without seeing your ball of code, it's hard to make concrete
recommendations. However, I've found that having a large number of
smaller projects (with interdepencies) works well for me. Then I can
use the filtering options inside the Package Explorer to view only the
projects I want to see at any given time.

Best,

Dave Orme

--
Dave Orme
Advanced Systems Concepts
http://www.swtworkbench.com

Re: Opinions on Project Structuring [message #51377 is a reply to message #50445]

Fri, 06 June 2003 04:56

Eclipse User

> > I would like to benefit from your experience structuring large projects
in
> > the workspace. I have inherited a tar ball of a large
Java/JSP/shell-script
> > system which consists of many individual programs, pages, modules and
3rd
> > party libraries.
> >
> > How should one go about structuring this tangeled mess?
> >
> > Should each program become a project in it own right? Or should I create
one
> > project and many package trees?
> >
> > How would I structure the build/ouput directories? Is there a way to
make
> > projects contain sub-projects?
>
> Without seeing your ball of code, it's hard to make concrete
> recommendations. However, I've found that having a large number of
> smaller projects (with interdepencies) works well for me. Then I can
> use the filtering options inside the Package Explorer to view only the
> projects I want to see at any given time.

One think I do is using seperated projects for unit tests and the product
code.
Then I open at least three windows. One for the product, one for the tests
and one
for the debugger. To dont get crazy about many packages I use the package
view
in tree view mode and a type view (package view upper-left, type view
lower-left).

This works well for me.

Bye

Martin (Kersten)

Re: Opinions on Project Structuring [message #51667 is a reply to message #51377]

Fri, 06 June 2003 10:50

Eclipse User

Originally posted by: bob.news.gmx.net

"Martin Kersten" <Martin.Kersten@student.uni-magdeburg.de> schrieb im
Newsbeitrag news:bbpksu$lvr$1@rogue.oti.com...
> One think I do is using seperated projects for unit tests and the
product
> code.

What's the benefit of separating tests from the source they should test?
IMHO it is better to have two different source roots for production and
unit test code. This gives you enough control with regard to jar
packaging, searching etc. I would not separate the test code since IMHO
it belongs to the same project.

> Then I open at least three windows. One for the product, one for the
tests
> and one
> for the debugger. To dont get crazy about many packages I use the
package
> view
> in tree view mode and a type view (package view upper-left, type view
> lower-left).

Yup.

robert

Re: Opinions on Project Structuring [message #51739 is a reply to message #50158]

Fri, 06 June 2003 10:53

Eclipse User

Originally posted by: bob.news.gmx.net

"Aidan Mark" <ahumphr@ZAPgmx.net> schrieb im Newsbeitrag
news:bbnfgg$u7v$1@rogue.oti.com...
> I would like to benefit from your experience structuring large projects
in
> the workspace. I have inherited a tar ball of a large
Java/JSP/shell-script
> system which consists of many individual programs, pages, modules and
3rd
> party libraries.
>
> How should one go about structuring this tangeled mess?
>
> Should each program become a project in it own right? Or should I create
one
> project and many package trees?
>
> How would I structure the build/ouput directories? Is there a way to
make
> projects contain sub-projects?

I'd try to identify the components you have and create a project for each
of them. Of course identifying the components might not be easy if they
are not already well structured. For Java I'd try to identify classes
that belong together and are used by several parts. These classes likely
form a lib I would want to package into a jar. A web application is a
component of its own so that would go into another project. Helper tools
(shell scripts etc.) might go together in some kind support project. If
you have a lot of 3rd party libs it might be reasonable to put them all
into a project which then is used by others. This way you could version
this and ensure that all others use the same version of the libs.

That's some ideas, I hope you can pick something useful from them.

robert

Previous Topic:	Project with both C and Java -- how to organize it?
Next Topic:	No more handles

Goto Forum:

-=] Back to Top [=-

Current Time: Fri May 09 01:02:20 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter