java ee - How to do fast deployment of multiple module EAR project using weblogic 12c? -

We are developing a product that uses many components of Eclipse to get it from the local GIT repository to import Is done and we are creating using EAR files. Ant script build.xml (which creates each command command called build.xml) and anti-script EAR after 1000 lines.
But I'm working in one component, but after every edit of the .java file

1. Weblogic server needs to be stopped (no more time)

2. Need to go to the repository folder

4. Weblogic Server (8++ min) Need to start

5. and here the IR file location is every time I over my work Because of all the places of the ant do not decide to run , Then decide. Is there any way to deploy immediately after each edit? ?

   Hi, we have come up with the ant script which have come up with * .eear redeploy, but it is taking 14 minutes through the ant script. What do I mean ant running the script manually? : Deployment is slower than I & Lt; Property Name = "wls.username" value = "weblogic" /> & Lt; Property Name = "wls.password" value = "Prima123Vera" /> & Lt; Property Name = "wls.hostname" value = "localhost" /> & Lt; Property Name = "wls.port" value = "7001" /> & Lt; Property Name = "admin.server.name" value = "AdminServer" /> & Lt ;! - & lt; Property Name = "deploy.target" value = "ClusterNameABC" /> - & gt; & Lt; Property Name = "deploy.target" value = "AdminServer" /> & Lt ;! - Here you can specify any cluster name, such as "personalized profile" such as "managed-on" or comma-managed admin / admin server - & gt; & Lt; Property Name = "deploy.name" value = "primavera" /> & Lt; Property Name = "deploy.source" value = "D: /work/rm/pgbu_platform-2.0/snapshots/primavera.ear" /> & Lt ;! - Settings setting - & gt; & Lt; Taskdef name = "wldeploy" classname = "weblogic.ant.taskdefs.management.WLDeploy" & gt; & Lt; Classpath & gt; & Lt; Pathelement = "C: / Oracle / Mildware / Oracle_Home / Waljar / Server / Lib / Web Blog." /> & Lt; / Classpath & gt; & Lt; / Taskdef> & Lt ;! - Deployment of applications - & gt; & Lt; Target name = "deployed" & gt; & Lt; Wldeploy action = "deployed" name = "$ {deploy.name}" source = "$ {deploy.source}" user = "$ {wls.username}" nostage = "true" password = "$ {wls} password} "Verbose =" true "adminurl =" t3: // $ {wls.hostname}: $ {wls.port} "target =" $ {deploy.target} "/> & Lt; / Target & gt; & Lt ;! - Re-deploy applications - & gt; & Lt; Target name = "recharge" & gt; & Lt; Wldeploy action = "redeploy" name = "$ {deploy.name}" user = "$ {wls.username}" password = "$ {wls.password}" verbose = "true" adminurl = "t3: // $ { Wls.hostname}: $ {wls.port} "target =" $ {deploy.target} "/> & Lt; / Target & gt; & Lt ;! - Unplugged applications - & gt; & Lt; Target name = "mutation" & gt; & Lt; Wldeploy action = "undeploy" name = "$ {deploy.name}" failure = "incorrect" user = "$ {wls.username}" password = "$ {wls.password}" verbose = "true" adminurl = "t 3: // $ {wls.hostname}: $ {wls.port} "target =" $ {deploy.target} "/> & Lt; / Target & gt; & Lt; / Project & gt;

   You can use or more specifically.

   The original process will be:

   1. Open the app ear for the auto deployment directory (explosion)
   2. Create a redipo file < Li> Work on your code
   3. Rebuilding a special jar that you modified
   4. Overwrite the old jar in the auto deployment directory
   5. Timestamp of the REDEPLOY file Change (for example, to recreate it) At this point, your weblogic app Will be re-deployed.
   6. Go to 3.

      You can also check and deploy the non-derivatives, if you can not get auto-deployment, to do these tasks, you will save some efforts during refinance.

      You must check to reduce the build time.