Todd, You are of course correct. Sometimes it takes a more incremental approach. We start with Build Best Practices:
Establish Release Authority Establish Reproducibility Automate Processes Abstract Process and Metadata from the physical resource Optimize Process and supporting architecture Apply build acceleration techniques Centralize access and collaboration for all stakeholders Continuous Integration Link build process to deployment process Measure! And under *Automate the Process* we further require Scripted *Portable* (which is also abstract process and metadata from physical resource) Modular Positively ID Artifacts Versioning Fast (<10 Minutes) And in my experience a focus on portability yields the most benefit. Removing hard coded reference and such, using one directory for all output. Once we are oat that point, and we generally have to get here to support the Ant build in a CI system, then just about the only thing we run into is that test files are co-mingled with code and other little items like that. ________________________________ Curt Yanko | Continuous Integration Services | UnitedHealth Group IT Making IT Happen, one build at a time, 600 times a day > -----Original Message----- > From: Thiessen, Todd (Todd) [mailto:[email protected]] > Sent: Thursday, May 19, 2011 2:49 PM > To: Maven Users List > Subject: RE: Maven folder structure > > You may still indeed have problems. That depends on your > current ant structure. As Curtis mentioned, if your ant > folder structure is "reasonable" then instructing maven to > use this directory structure is doable. But how does one > define reasonable? > > For example, does your ant build copy .class files between > jars? Does your ant build generate more than one artifact? > If the answer is yes to either of these questions then you > will likely have to do some restructuring. And in that case, > you are better off using the default Maven structure to keep > things simple. In my experience, ant builds usually have > these kind of complexities which make reusing the ant > directory structure problematic. > > But if your ant build doesn't have these complexities, then > you should be fine. > > > -----Original Message----- > > From: uday shankar [mailto:[email protected]] > > Sent: Thursday, May 19, 2011 2:10 PM > > To: [email protected] > > Subject: RE: Maven folder structure > > > > After we override the default folder structure by making > the changes > > in the build tag of the pom.xml file. when we run any > command say mvn > > package doesn't it consider the folder structure mentioned in the > > <build> tag. > > If > > this is the case we should not have anyproblem even if we > are changing > > the folder structure because in that case the plugins like package > > will be considering the altered structure > > > > -- > > View this message in context: > http://maven.40175.n5.nabble.com/Maven- > > folder-structure-tp4409276p4410472.html > > Sent from the Maven - Users mailing list archive at Nabble.com. > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > This e-mail, including attachments, may include confidential and/or proprietary information, and may be used only by the person or entity to which it is addressed. If the reader of this e-mail is not the intended recipient or his or her authorized agent, the reader is hereby notified that any dissemination, distribution or copying of this e-mail is prohibited. If you have received this e-mail in error, please notify the sender by replying to this message and delete this e-mail immediately. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
