Here are some of the negatives: Testing time increases if more files are
grouped, bugs can take longer to be found if alot of files are compiled
together, and the possibility of the whole application not working because
the code can't find the correct files/jars.
The reason why the 1 jar/module
Hi guys,
I have been working with maven for about a week or so, and ive been doing
good progress with it, but now im stuck at a point where I dont know how to
compile files in a module into different Jars. What I mean by that is lets
say I have files A, B and C, and I would like to compile files
are new, is how many artifacts (WAR, EAR, whatever)
your current build produces. You may have to do a lot of refactoring due
to this as Maven wants one artifact per project. This often leads into
more modules/projects than one may think.
Cheers,
Manos
Quoting Quakky [EMAIL PROTECTED
PM, Quakky wrote:
Hello,
I am currently in need of some advice concerning Maven. I am a new
user,
trying to get maven to work with a project that is pretty complex
(doesn't
follow the default tree structure of maven, has to be packaged in a
certain
way, etc) . I didn't work
Hello,
I am currently in need of some advice concerning Maven. I am a new user,
trying to get maven to work with a project that is pretty complex (doesn't
follow the default tree structure of maven, has to be packaged in a certain
way, etc) . I didn't work on the project, I dont know how to code
