> I think your overall approch is on target. One of the things I have found > easier when deploying to containers is to have Tomcat as part of CVS.. It > gives you a lot more control over what the Tomcat environment looks like, > isn't too large, and reduces variables.
I agree in principle. The problem is it's not practical to put WebSphere or Oracle in CVS. So what I was thinking was to divide the containers into two categories: - versioned in CVS - for unstable, lightweight containers only. For example tomcat. - an install procedure using official releases. This would be for Oracle, MySQL, WebSphere. Tomcat can fall into either category, and I prefer the second. But I'm open to suggestions. > Also, as far as the merging of jars, anything you can do in Ant, > you can do > in Maven, as Maven supports all ant tasks. Here is an article > that gives a > simple example of calling the <echo/> task from Ant in Maven: > http://www.onjava.com/pub/a/onjava/2004/03/17/maven.html. This is a worst case, call the ANT target. But with Maven's Jelly scripts I wasn't sure if it'd be better to do something with ANT or Jelly. Thanks, Michael -- This E-mail is confidential. It may also be legally privileged. If you are not the addressee you may not copy, forward, disclose or use any part of it. If you have received this message in error, please delete it and all copies from your system and notify the sender immediately by return E-mail. Internet communications cannot be guaranteed to be timely, secure, error or virus-free. The sender does not accept liability for any errors or omissions. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
