Matt RaibleMatt Raible is a Java Champion and Developer Advocate at Okta.

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.


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.

Use Maven? Experience says no...

I've been wanting to upgrade struts-resume to use Maven, but after reading Patrick's post, I might just change my mind.

And after 2 years of using Ant, Maven (which uses Jelly and Werkz as the underlying engines) behaves differently enough from Ant to utterly frustrate me. So I'm back heading back to the drawing board for new ideas.

Of course, my hope is to integrate Maven without losing Ant and let them both live beside each other intimately. Someday it will be done...

Posted in Java at Feb 23 2003, 04:30:52 PM MST 1 Comment

Im using indirection with ant to avoid duplication. I wrote a dozen of entities, each one with related tasks: javadoc.ent, xdoclet.ent, etc. Then I call them from several files (more entities of build.xml) persistence.xtarget, web.xtarget, ..., using blocks like <antcall target="-javac.compile"> &nbsp;&nbsp;<param name="build.dir" value="${}"/> &nbsp;&nbsp;... (lot of params) </antcall> In short, I replaced ant code with antcall blocks. Maybe same number of lines, but I think is more legible, you see a target and its params. My wish for Ant2: a better way to define a contract between modules of ant code.

Posted by jano on February 23, 2003 at 06:50 PM MST #

Post a Comment:
  • HTML Syntax: Allowed