Win a copy of Re-engineering Legacy Software this week in the Refactoring forum
or Docker in Action in the Cloud/Virtualization forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Folder Structure in a large project

 
Varun Chopra
Ranch Hand
Posts: 213
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I was pondering over what will be the folder structure in a large project? Suppose there are 3 departments in an enterprise for which a project is being developed. Is that better folder structure?

com.department.organization.pojo
com.department.organization.dao
com.department.organization.utility
com.department.common

or is below a better one:

com.organization.pojo
com.organization.dao
com.organization.utility
com.organization.common

I guess first one is better because then we can build and deploy independent department's code. What is your opinion?
 
Campbell Ritchie
Sheriff
Posts: 48441
56
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
The second; there is a customary format for package names. It's in the Java Tutorials.
[ October 01, 2008: Message edited by: Campbell Ritchie ]
 
Campbell Ritchie
Sheriff
Posts: 48441
56
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Sorry, I got it the wrong way round at first and had to change first to second

It says in the link I quoted that you use local conventions to disambiguate projects, so com.company.department.project is the customary naming format, but your company might prefer com.company.room1.project.
 
Varun Chopra
Ranch Hand
Posts: 213
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
No Problem, Thanks Campbell.
 
Campbell Ritchie
Sheriff
Posts: 48441
56
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
You're welcome
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic