This week's giveaway is in the EJB and other Java EE Technologies forum. We're giving away four copies of EJB 3 in Action and have Debu Panda, Reza Rahman, Ryan Cuprak, and Michael Remijan on-line! See this thread for details.
I'll admit right off the bat that I haven't thoroughly browsed the Maven documentation so if the answer to my question is there, just link me to it and I'll be happy. When I start a new project I spend quite a bit of time going out and making sure I have the latest of all the libraries I need. It is my understanding that if I used Maven it pretty much does this for me if I add the dependencies to my pom.xml.
However, I really don't like the project structure that Maven creates. Can this be customized and if so how much?
I really don't like the Maven project structure. However there are 2 reasons - 3 reasons - for using Maven:
1. You want the automated library management 2. You want a diverse team to be able to hit the ground running, so you want a standardized project structure. 3. You want to have a really ugly project structure.
Yes, you can re-arrange the project structure, but they've made it fairly difficult. I just surrender to the inevitable. Maven's hard enough to debug as it is.
Of course, there's one thing uglier than the structure of a Maven project. The structure of a Maven project under Subversion.
Customer surveys are for companies who didn't pay proper attention to begin with.
I think appfuse is really just some custom Maven archetypes...
One non-Maven dependency management project I've heard of (though not used) is Ivy.
You can also use AntLib for Maven - use Maven through Ant to manage dependencies, but build through Ant rather than Maven. Since you're not doing the build through Maven, it doesn't matter what your directory structure is like. (I'm doing this currently - if you run into problems/want further information... just ask.) [ May 29, 2007: Message edited by: Nathan Pruett ]
Write once, run anywhere, because there's nowhere to hide! - /. A.C.