Sure, it's possible to use Ant for enterprise builds, but here's the thing: You'll coax so much more mileage out of your EJB 3 and Seam-based projects by building them with Maven 2.
Al final del log (lo podemos ver por consola o en <JBOSS_HOME>/server/default/log) dará un mensaje del estilo: 18:32:35,822 INFO [Server] JBoss (MX MicroKernel) [4.2.1.GA (build: SVNTag=JBoss_4_2_1_GA date=200707131605)] Started in 14s:854ms
Al final del log (lo podemos ver por consola o en <JBOSS_HOME>/server/default/log) dará un mensaje del estilo: 18:32:35,822 INFO [Server] JBoss (MX MicroKernel) [4.2.1.GA (build: SVNTag=JBoss_4_2_1_GA date=200707131605)] Started in 14s:854ms
Our Java EE project will have the following structure: an EJB project consisting of a simple EJB 3 Session bean, a WAR containing presentation files as JSPs, and an EAR containing the modules and dependencies. We will then go over the task of using Maven