This week's giveaway is in the Spring forum.
We're giving away four copies of REST with Spring (video course) and have Eugen Paraschiv on-line!
See this thread for details.
The moose likes Ant, Maven and Other Build Tools and the fly likes QA v/s dev build Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

Win a copy of REST with Spring (video course) this week in the Spring forum!
JavaRanch » Java Forums » Engineering » Ant, Maven and Other Build Tools
Bookmark "QA v/s dev build" Watch "QA v/s dev build" New topic

QA v/s dev build

aakash bhatt
Ranch Hand

Joined: Jan 09, 2003
Posts: 182
What is the difference between and QA and Dev build and when should we do QA or dev
Greg Charles

Joined: Oct 01, 2001
Posts: 2963

Is there some particular context in which you see these defined? In general, you should give to QA exactly what you intend to deliver as a product. For example, the debug flag to the compiler should be off. Also, paths, classpaths, and libraries should be the same as will be used by the customer.
On the other hand, a dev build can be a bit looser. You can (and probably should) keep debugging and assertions enabled. The paths can be set up to take advantage of the development environment, rather than putting together a full installation package.
I agree. Here's the link:
subject: QA v/s dev build
It's not a secret anymore!