On 15/12/2010 12:32 PM, ginni wrote:
We are just now using Maven and love the benefits thus far. Would anyone
please advise on the best setup for a production environment, as in: should
we/should we not use Hudson, Maven to do production application development
(is that possible?)? We are a small group of developers building our first
Tomcat servers and preparing to go live with an application we've just
developed for in-house use only. I've been tasked with coming up with a
formal 'process' to manage our releases. We set up an internal repository
and are using Nexus to manage it, which is working nicely. But how is it
best to handle pushing out our production application for our users?
Thanks!
Ginni
Use JNDI to manage the site specific aspects of your configuration. This
will make deploying to test machines and production less painful.
There seems to be a lot of support here for Hudson but there are also a
lot of messes related to Hudson.
I am either ignorant or old fashioned, but I would stay away from Hudson
until you have a smooth deployment setup working without it.
I am also not completely convinced that testing that does not include
the user interface and usability issues is really a big benefit for most
web applications.
You can increase the stability of your applications and make unit
testing stronger by being thoughtful about how you architect your
application.
Look for ways to break out functions into services that can are simple
and and can be tested without relation to the View.
Think about how to convert MVC to MV-SOA.
Look for ways to make standalone libraries instead of packages inside a
webapp.
Criteria:
- Might be reusable,
- Might survive changes in application functionality without being changed
- Might encapsulate mutable functionality so that a changes in
functionality of the application can be achieved by changes only in the
library.
Yes you will still use packages in the library.
If you are not using Spring, start to use Spring.
#1 rule. Do not try to bend Maven.
Ron
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
