BorlandTalk.com Forum Index BorlandTalk.com
Borland discussion newsgroups
 
Archives   FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

Dev environment dir structure / reusing packages

 
Post new topic   Reply to topic    BorlandTalk.com Forum Index -> JBuilder IDE
View previous topic :: View next topic  
Author Message
Steve Kincer
Guest





PostPosted: Wed Jul 05, 2006 9:38 pm    Post subject: Dev environment dir structure / reusing packages Reply with quote



I've been using JBuilder for a while and always wondered about this. Let's
say I want to create a new project called MyProj. When you first create the
proj, JBuilder wants to put the project file (.jpx) in a directory called
MyProj under my root JBuilder dir. It then wants to put the source for this
project under MyProj/src. So, if I'm using packages, my source ends up
being in dirs like this:

C:/Documents and Settings/me/jbproject/MyProj/src/com/mycompany/appspecific/
C:/Documents and Settings/me/jbproject/MyProj/src/com/mycompany/common/

The thing I don't get about this, is that if I want to use certain packages
on many different projects, I'd have to copy the packages to every project.
The way I got around this is that I put all my project files in C:/Documents
and Settings/me/jbproject/ (one level up from what JBuilder defaults to), so
the source root for every project is C:/Documents and
Settings/me/jbproject/src. This means that I can reference shared packages
the same way in any project (in a dir like C:/Documents and
Settings/me/jbproject/src/com/mycompany/common). In other words, if you
look at my dir structure for all my jbuilder apps, it looks like this:

C:/Documents and Settings/me/jbproject/src/com/mycompany/app1specific/
C:/Documents and Settings/me/jbproject/src/com/mycompany/app2specific/
C:/Documents and Settings/me/jbproject/src/com/mycompany/common/

Do you get what I'm saying? Is this what everyone does? What am I missing?
Thanks.
Steve
Back to top
Lori M Olson [TeamB]
Guest





PostPosted: Thu Jul 06, 2006 6:08 am    Post subject: Re: Dev environment dir structure / reusing packages Reply with quote



Steve Kincer wrote:
Quote:
I've been using JBuilder for a while and always wondered about this. Let's
say I want to create a new project called MyProj. When you first create the
proj, JBuilder wants to put the project file (.jpx) in a directory called
MyProj under my root JBuilder dir. It then wants to put the source for this
project under MyProj/src. So, if I'm using packages, my source ends up
being in dirs like this:

C:/Documents and Settings/me/jbproject/MyProj/src/com/mycompany/appspecific/
C:/Documents and Settings/me/jbproject/MyProj/src/com/mycompany/common/

The thing I don't get about this, is that if I want to use certain packages
on many different projects, I'd have to copy the packages to every project.
The way I got around this is that I put all my project files in C:/Documents
and Settings/me/jbproject/ (one level up from what JBuilder defaults to), so
the source root for every project is C:/Documents and
Settings/me/jbproject/src. This means that I can reference shared packages
the same way in any project (in a dir like C:/Documents and
Settings/me/jbproject/src/com/mycompany/common). In other words, if you
look at my dir structure for all my jbuilder apps, it looks like this:

C:/Documents and Settings/me/jbproject/src/com/mycompany/app1specific/
C:/Documents and Settings/me/jbproject/src/com/mycompany/app2specific/
C:/Documents and Settings/me/jbproject/src/com/mycompany/common/

Do you get what I'm saying? Is this what everyone does? What am I missing?
Thanks.
Steve



That's why we make *libraries*. Make a project for the code that is
shared between projects (com.mycompany.common). If you are using JB
Enterprise, you can select that library project as a required library
for any other project. If you are using JB Foundation or Developer, you
can create a library in any project to point to the classes (output)
directory of your library project. Don't point at jars being generated
by your library project, because you'll run into problems.

--

Regards,

Lori Olson [TeamB]

------------

Save yourself, and everyone else, some time and search the
newsgroups and the FAQ-O-Matic before posting your next
question.

Google Advanced Newsgroup Search
http://www.google.ca/advanced_group_search
Other Newsgroup Searches:
http://www.borland.com/newsgroups/ngsearch.html
Joi Ellis's FAQ-O-Matic:
http://www.visi.com/~gyles19/fom-serve/cache/1.html
Back to top
Display posts from previous:   
Post new topic   Reply to topic    BorlandTalk.com Forum Index -> JBuilder IDE All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Powered by phpBB © 2001, 2006 phpBB Group
SEO toolkit © 2004-2006 webmedic.