eclipse

Thread view:

Enable EMail Alerts

Start New Thread

Andersen - 24 Oct 2005 13:06 GMT

How does eclipse work. My projects seem to not be clearly separated.
Should I use one workspace per project?

Reply to this Message

Andrew Thompson - 24 Oct 2005 13:17 GMT

> How does eclipse work. ..

It might be best to ask the experts..
<http://www.eclipse.org/newsgroups/index.html>

Reply to this Message

Ingo R. Homann - 24 Oct 2005 14:07 GMT

Hi,

> How does eclipse work. My projects seem to not be clearly separated.
> Should I use one workspace per project?

No, that should not be necessary. Using "Project Properties | Project
References" you can configure, if a project depends on another project.

What exactly is your problem?

Ciao,
Ingo

Reply to this Message

Roedy Green - 24 Oct 2005 14:20 GMT

On Mon, 24 Oct 2005 14:06:57 +0200, Andersen
<andersen_800@hotmail.com> wrote, quoted or indirectly quoted someone
who said :

>How does eclipse work. My projects seem to not be clearly separated.
>Should I use one workspace per project?

I set mine with one project for 1.1 1.2 1.3 1.4 and 1.5 JVM
compatibility. You can set up compiler options on a per project
basis, so that seemed as good as any a way to catalog my projects.

Signature

Canadian Mind Products, Roedy Green.
http://mindprod.com Again taking new Java programming contracts.

Reply to this Message

Chris Smith - 24 Oct 2005 14:46 GMT

> How does eclipse work. My projects seem to not be clearly separated.
> Should I use one workspace per project?

Definitely not. Just work with the project that you want to work with.
If you need to classify your projects into groups, the most recent
versions allow you to ask Package Explorer to group by "working set",
which helps large numbers of projects remain manageable.

Signature

www.designacourse.com
The Easiest Way To Train Anyone... Anywhere.

Chris Smith - Lead Software Developer/Technical Trainer
MindIQ Corporation

Reply to this Message

Roedy Green - 25 Oct 2005 03:09 GMT

>Definitely not. Just work with the project that you want to work with.
>If you need to classify your projects into groups, the most recent
>versions allow you to ask Package Explorer to group by "working set",
>which helps large numbers of projects remain manageable.

Also it is relatively easy to move a package between projects and
classes between packages. So you don't have to get in right the first
time.

Signature

Canadian Mind Products, Roedy Green.
http://mindprod.com Again taking new Java programming contracts.

Reply to this Message

Monique Y. Mudama - 25 Oct 2005 18:37 GMT

>>Definitely not. Just work with the project that you want to work
>>with. If you need to classify your projects into groups, the most
[quoted text clipped - 5 lines]
> classes between packages. So you don't have to get in right the
> first time.

Although you will still run into at least minor issues trying to move
around files in most version control systems.

Signature

monique

Ask smart questions, get good answers:
http://www.catb.org/~esr/faqs/smart-questions.html

Reply to this Message

Roedy Green - 26 Oct 2005 00:43 GMT

On Tue, 25 Oct 2005 11:37:00 -0600, "Monique Y. Mudama"
<spam@bounceswoosh.org> wrote, quoted or indirectly quoted someone who
said :

>Although you will still run into at least minor issues trying to move
>around files in most version control systems.

I doubt he will be doing that yet, though when he does any sort of
renaming is a royal pain. Even fixing a spelling error in a method
name triggers a huge chain of not-really-changes in a version control
system.

My solution I call dynamic version control which is an offshoot of the
scid idea.

See http://mindprod.com/projects/dynamicversioncontrol.html
http://mindprod.com/projects/scid.html

Signature

Canadian Mind Products, Roedy Green.
http://mindprod.com Java custom programming, consulting and coaching.

Reply to this Message

eclipse

Free Magazines