Matt RaibleMatt Raible is a Web Developer and Java Champion. Connect with him on LinkedIn.

The Angular Mini-Book The Angular Mini-Book is a guide to getting started with Angular. You'll learn how to develop a bare-bones application, test it, and deploy it. Then you'll move on to adding Bootstrap, Angular Material, continuous integration, and authentication.

Spring Boot is a popular framework for building REST APIs. You'll learn how to integrate Angular with Spring Boot and use security best practices like HTTPS and a content security policy.

For book updates, follow @angular_book on Twitter.

The JHipster Mini-Book The JHipster Mini-Book is a guide to getting started with hip technologies today: Angular, Bootstrap, and Spring Boot. All of these frameworks are wrapped up in an easy-to-use project called JHipster.

This book shows you how to build an app with JHipster, and guides you through the plethora of tools, techniques and options you can use. Furthermore, it explains the UI and API building blocks so you understand the underpinnings of your great application.

For book updates, follow @jhipster-book on Twitter.

10+ YEARS


Over 10 years ago, I wrote my first blog post. Since then, I've authored books, had kids, traveled the world, found Trish and blogged about it all.

RECENT ENTRIES


Tag Cloud


abbie appfuse birthday denver family grails gwt jack java javascript jhipster jsf linkedin maven roller skiing softwaresummit spring springmvc struts2 travel trish vacation webframeworks wicket
« Pictures from Florid... | Main | [ANNOUCEMENT] Common... »
Tuesday January 28, 2003

Enhancing the build process with CruiseControl and Maven

Now that we've passed the first milestone on my project, we're getting into "What's Next." I'm going to propose that we use Maven and CruiseControl to create a tighter continuous integration and testing process. I hope to continue to use our current Ant build.xml, just re-arrange some jars and such for Maven. Think it'll work? I'd love to hear any experiences or helpful hints with either of these tools. I have a start on Maven, and I think I'll be fine getting started with it, but I've never used CruiseControl. Luckily, I have Java Development with Ant on my desk to help me out.

Posted in Java at Jan 28 2003, 08:57:54 AM MST 3 Comments
Comments:

This last month I've been transitioning our company from ant based builds to maven based builds. The main reason for it was too much duplication between projects. Xml includes are really the only way to do reuse with ant and they have their own set of problems. Maven's jar based plugin's are a much more elegant solution. Maven has more files to keep track for each build (project.xml, maven.xml and project.properties, and all the plugins). The benefits you get are balanced with the additional indirection of splitting the logic into (potentially) four or more places. And the existing build.xml (while you can use it initially) isn't really how maven works, so you will end up moving your logic from ant into the format that maven likes eventually. This isn't to warn you off however, as Maven is perfect when you have multiple projects that need to be set up "about" the same. It definitely cuts down the copy and paste between projects. Shoot me an email if want some more info.

Posted by Patrick Peak on January 28, 2003 at 04:39 PM MST #

Might I suggest Anthill instead? Its much easier to configure than CruiseControl, and you'll likely find their e-mail list support much more responsive and proactive to your needs. I'm not sure how it interacts with Maven, but I suspect it'd work.

Posted by Erik Hatcher on January 28, 2003 at 07:24 PM MST #

I'll look into AntHill - I found a comparison of AntHill vs. CruiseControl - I'll have to read it this afternoon.

Posted by Matt Raible on January 28, 2003 at 07:44 PM MST #

Post a Comment:
  • HTML Syntax: Allowed