Am I missing something?
There seem to be a lot of people who try to incorporate jar projects
into master projects and deploy with the "Big Bang" Theory - Get
everything "all right" and deploy the whole mess.
They seem to generate a lot of problems for themselves.
Is it not a better idea to build projects for your libraries separately,
test them, deploy them on their own and then use them as dependencies in
the same way that one uses dependencies from third parties?
This leaves open the question of versions since your libraries can have
their own versions and you have to identify the version in the pom of
your WAR files but that is not a big issue.
You can use parent POMs with the version properties for all your
libraries that you share if you want to keep everyone on the same version.
We really need to look at a Best Practices document to reduce the amount
of traffic in this forum from people who are trying to reinvent the
software development lifecycle when it is completely unnecessary.
There are not that many ways to build applications.
I can think of :
1) Portals with portlets
2) Web application
3) Web Services
4) Standalone clients.
Have I missed anything?
It appears to me that Maven can build all of these in pretty much the
same way.
How many useful ways are there to build each one of these things?
Ron
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
