3

After generating a project using seam-gen, what is the recommended ignore pattern for source control? What should the recommended .gitignore file (or svn:ignore, or equivalents) look like?

Hosam Aly
  • 41,555
  • 36
  • 141
  • 182

3 Answers3

5

We develop our Seam projects under Eclipse. Our current svn:ignore has the following entries:

classes                      # all class files
dist                         # contains generated war files for deployment
.settings                    # some Eclipse settings
exploded-archives            # war content generation during deploy (or explode)
test-output                  # test results
test-build                   # test compilation (ant target for Seam)
test-report                  # test report generation for, e.g., Hudson
temp-testng-customsuite.xml  # generated when running test cases under Eclipse

In addition, in our bootstrap folder we ignore data and tmp.

kraftan
  • 6,272
  • 2
  • 22
  • 24
3

I have no direct experience with seam, but if you start a project with seam-gen, then you need to:

  • exclude in your .gitignore file whatever will contain generated content (like the target directory, also *.sw files or test-output directories)
  • don't exclude IDE-related files (if they don't include absolute path), in order for others to get directly a project they can import in said IDE,
  • contribute back the content of the gitignore file in the GitHub gitignore project: they need a seam/seam-gen entry.
Community
  • 1
  • 1
VonC
  • 1,262,500
  • 529
  • 4,410
  • 5,250
1

Based on the entries above, I've merged the suggestions into an entry on the gitignore project: https://github.com/github/gitignore/blob/master/SeamGen.gitignore

Hosam Aly
  • 41,555
  • 36
  • 141
  • 182