With our home-made build system (which we're probably going to replace with Maven in the near future) we can already do this. We have components ready for 4 application servers and 3 databases, which leads to an even bigger amount of combinations to test, but we're able to and that's handy!
In between point 2 and 3 mentioned below, we run the database scripts on the dbserver to make sure the database is empty and stuff... This in case the app.server cannot create the tables automatically. If you need help, I'll be there... alef -----Original Message----- From: Nathan Coast [mailto:[EMAIL PROTECTED]] Sent: Tuesday, 21 May 2002 15:09 To: maven dev Subject: j2ee component deployment Hi, looking at the build-j2ee.xml, there are targets to automate the assembly of war and ear files. Are there any plans to provide automation of the deployment / updating of these assembled components within j2ee containers? e.g. ear files to common j2ee servers - weblogic, websphere, jboss. similarly war files to tomcat etc. This would presumably require an extension of project.xml to describe which container was in use and properties specific to those containers - location, username, password etc. This could lead the way to automating the testing of new builds within the deployment environment. 1) build / assemble 2) unit test 3) deploy 4) tests against deployed environment. Might make sense to leverage the new support for j2ee deployment to common containers in available in ant 1.5. Cheers Nathan -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
