Package structure for a Java project?

Question

What is the best practice for setting up package structures in a Java web application?

How would you install the src code, unit test, etc.?

Answer 1

You can follow the maven project standard. You do not need to actually use maven, but it will facilitate the transition in the future (if necessary). In addition, other developers will use this layout, since many open source projects are laid out in such a way

Answer 2

There are several existing resources you can check:

• Package your java classes correctly
• Spring 2.5 Architecture
• Java Tutorial - Package Naming
• SUN Assignment Agreements

For what it's worth, my own personal recommendations that I usually use are as follows:

• Start with a reverse domain, for example. "Com.mycompany".
• Use a product name, for example. "MyProduct". In some cases, I tend to have generic packages that are not specific to a particular product. They will be classified according to the functionality of these general classes, for example. "io", "util", "ui" etc.
• After that, he becomes more free. Usually I group according to the project, area of ​​functionality, deployment, etc. For example, I can have "project1", "project2", "ui", "client", etc.

A few other points:

• This is quite common in projects that I worked on for package names that stem from project documentation. Typically, products are already divided into areas of functionality or purpose.
• Don't stress too much about immediately pushing the general functionality into higher packages. Wait until you need projects, products, etc., and then a refactor.
• See dependencies between packages. They are not all bad, but this can mean a tight connection between what can be separate units. There are tools that can help you keep track of this.

Answer 3

I would suggest creating the structure of your package by function, not by implementation level. Good entry on this Java practice: package by function, not layer

Answer 4

Here you can read about standard directory layouts and the directory / package structure for a java project.

Answer 5

I usually like the following:

• bin (binaries)
• doc (Documents)
• inf (Information)
• lib (Libraries)
• res (Resources)
• src (Source)
• tst (Test)

This can be considered unconventional, but I believe that this is a very good way to organize things.

Answer 6

Another very good article about Java package structure: Java classpath management

Answer 7

As usual, I have a folder hierarchy -

• the name of the project
  • CSI
  • Ben
  • Tests
  • libs
  • documents