Eclipse Community Forums: DSDP » migrate some existing projects from Sun ONE Studio to Eclipse?

Help

Home

Home » Archived » DSDP » migrate some existing projects from Sun ONE Studio to Eclipse?

Show: Today's Messages :: Show Polls :: Message Navigator

migrate some existing projects from Sun ONE Studio to Eclipse? [message #7834]

Tue, 20 December 2005 01:11

Eclipse User

Originally posted by: clibase-forum.yahoo.com

Hi, we want to migrate some existing projects from Sun ONE Studio to Eclipse. Our file structures are like:
com/domain/common,
com/domain/project1, and
com/domain/project2.

I tried to build project1 which (and project2 as well) uses the "common" package. If I put "com" directory under the Eclipse project source, it always compiles project2 as well which we do not need. I tried to exclue the "project2" manually but this may not be an ideal solution since the "com/domain" is shared by multiple developers and later on new irrelevant directories could be created there later on and I have to know that exclude them one by one in the configuration.

Anyone has a better idea how this can be organized? We'd better not change the existing source file structure if possible.

Thanks, -cli

Report message to a moderator

Re: migrate some existing projects from Sun ONE Studio to Eclipse? [message #7919 is a reply to message #7834]

Mon, 08 May 2006 19:48

Doug Gaff

Messages: 150
Registered: July 2009

Senior Member

Try the eclipse.platform newsgroup for this question.

"C Li" <clibase-forum@yahoo.com> wrote in message
news:12784804.1135041129009.JavaMail.root@cp1.javalobby.org:

> Hi, we want to migrate some existing projects from Sun ONE Studio to
> Eclipse. Our file structures are like:
> com/domain/common,
> com/domain/project1, and
> com/domain/project2.
>
> I tried to build project1 which (and project2 as well) uses the "common"
> package. If I put "com" directory under the Eclipse project source, it
> always compiles project2 as well which we do not need. I tried to exclue
> the "project2" manually but this may not be an ideal solution since the
> "com/domain" is shared by multiple developers and later on new
> irrelevant directories could be created there later on and I have to
> know that exclude them one by one in the configuration.
>
> Anyone has a better idea how this can be organized? We'd better not
> change the existing source file structure if possible.
>
> Thanks, -cli

Report message to a moderator