Should I use Maven for struts-xdoclet?. James Strachan has encouraged me to use Maven for my struts-xdoclet project. I should give Dave some credit too, as he has also suggested this through e-mail. Here's my delimma, it'll probably take me anywhere from 2-4 hours to figure it out and integrate it. Does it buy me that much functionality to make it worth it? And my biggest fear is that it seems to help you produce a "project website" - that has a Jakarta look to it. I'll end up spending hours and hours tweaking the look and feel of that sucker - which provides no real value at all. But I'll do it because that's how I am. So to answer your suggestion James, I'm afraid to integrate with Maven, as I'm scared to create too much more work for myself with my already tight deadlines. Volunteers are welcome ;-) [Raible Designs :: We Build Web Apps]
Actually I was suggesting that once your struts-xdoclet work was complete, it'd be cool if it could be packaged up as a Maven plugin. Then any project thats already using Maven would automatically get your plugin. Maven uses a plugin mechanism so that you can package up tasks, tools or scripts once and they become available to any other Maven user.
e.g. Maven has plugins for JBuilder, IDEA and eclipse which auto-generate the IDE's project descriptors for your Maven project. There are plugins for JavaCC, Antlr, Clover and many other things, automatically available to Maven users. So having a struts-xdoclet plugin would sound like a great idea.
If you're afraid though don't worry about it! :-). Just get your struts-xdoclet project complete and I'm sure someone else could package it up as a Maven plugin.
4:08:22 PM 
|
