On 21/09/2010 6:07 AM, fhomasp wrote:
I've been hired to do the mavenizing of a project at a client. There I found
an interesting problem and I'm unsure how to proceed. I'll clarify.
There is a project which has 3 web folders with JSP pages in them and
there's one src package folder which contains the java classes, with JSP
controller classes as well.
Using ant and property files the developers create three wars with the same
java code and one of the JSP folders. This is because each JSP folder
represents a different application.
At first I suggested to put the src java code into a project which is then
built as a jar and include it in the three web modules but the developers
don't want that. They want to be able to deploy and test and remove
seperate classes on their own.
What does this mean?
Why can they not change a class in the library jar and rebuild the jar
and the war?
What do they think the difference will be?
You may also want to delve a bit deeper into the library jar and see if
it can be broken down into smaller libraries that are more robust,
stable and better tested.
Maven makes it easier to pull together many dependencies into a project.
Make sure that you get them a repository. This will make them much more
comfortable with Maven.
I could really use some advice on this one.
Thanks!
T
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
