I have the the Better Builds with Maven book on my desk here opened to “Developing your first Mojo.” EVERYONE that has walked in has commented something clever regarding their mojo.
This afternoon this happened:
dev1: I wish I had developed my first mojo in college.
dev2: You wish you had mojo now! (BURN!)
The main problem I am trying to resolve is the situation where you want to prevent two projects from running at the same time. Why would you want to do that? Perhaps you have resource constraints like a file system directory or a database the unit tests run against. For instance we have separate projects for continuous and daily builds - without a locking mechanism we likely get a failed build if they both run at the same time (one may do a “clean” while the other is trying to “build” etc).
http://www.kiwidude.com/blog/2006/10/cruisecontrolnet-serialised-build_29.html
I was reading this article about Maven 2.0 the other day and wondered why they’d name a config file porn.xml.
pom.xml Fig. A.
FYI, it’s P-O-M.xml. Times New Roman blends makes the m look like r + n on my screen, not sure about yours.
r + n = rn Fig. B.
Work has been twisting my mind lately, I should sleep more.
Current mood: Velociraptors!