Two Laptop Bag
The moose likes Spring and the fly likes Should Roo artifacts end at the SCM? Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

Win a copy of Java Interview Guide this week in the Jobs Discussion forum!
JavaRanch » Java Forums » Frameworks » Spring
Bookmark "Should Roo artifacts end at the SCM?" Watch "Should Roo artifacts end at the SCM?" New topic

Should Roo artifacts end at the SCM?

Hussein Baghdadi
clojure forum advocate

Joined: Nov 08, 2003
Posts: 3479

Spring Roo generates a lot of AOP artifacts, should those artifacts end at the SCM?
Ken Rimple
Ranch Hand

Joined: Jul 20, 2010
Posts: 63

Good question. You mean the .aj files, I am assuming...

Two schools of thought on this, and originally I was on the "don't check 'em in" side.

If you don't check them in, then everyone who wants to build has to run the Roo shell to generate them. That includes continuous integration tools. While it's boilerplate code, and can be annoying to have to check in, the advantage is that you don't need the tool to build it later.

I'm now on that side. I had that angle explained to me by someone from the Roo team and it made good sense.

Just remember to do a svn status or git status to see what changed recently before updating your SCM files.


Ken Rimple
Co-author, Manning Spring Roo in Action
I teach for Chariot Solutions (Spring, Maven, Hibernate, other courses). Schedule here
I agree. Here's the link:
subject: Should Roo artifacts end at the SCM?
It's not a secret anymore!