: initial commit
I've been told that if you're already using maven 1, and it
works, there's not much value in switching, but if you're
starting a new project, you might as well use maven 2. by
the maven mavens.
So I'd probably be in favor of maven 2 since we're starting
from scratch
Maven is pretty good at building, testing, and packaging for release
without a lot of manual intervention. I think we would need to create
a separate maven goal to repackage the jars into the final jar
distribution but maven allows you do create pre- and post-goals to do
just what you need
Would it be ok to build three different jar files based on whether
the target was 1.3, 1.4, or 1.5? Packaging the different jar files
into one could be a post-build exercise.
Or a specific build target that combined the three jar files.
How is the source code structured today?
I've been told that if you're already using maven 1, and it works,
there's not much value in switching, but if you're starting a new
project, you might as well use maven 2. by the maven mavens.
So I'd probably be in favor of maven 2 since we're starting from
scratch.
The question has
