This week's giveaway is in the EJB and other Java EE Technologies forum. We're giving away four copies of EJB 3 in Action and have Debu Panda, Reza Rahman, Ryan Cuprak, and Michael Remijan on-line! See this thread for details.
We are using maven to build the ear. But, we want to simplify the deployment process for weblogic as we have to deploy the application many frequently during the development.
Presently we build the ear using the maven and then use a batch file to explode the ear. We then manually copy this exploded ear to the weblogic autodeploy directory and also create a blank REDEPLOY file into the <exploded ear>/META-INF to trigger the auto-deploy by manually touching it. For the changes that don't require a redeployment (jsp, html etc.), we change the file in the source directory and manually copy to the autodeploy/exploded_archive/web. For the changes that require redeployment (java, property files, config xmls etc), we make the change in source directory, run 'mvn compile' on java source directory and then manually copy generated class file of the java package heirarchy to replace the same from auto deploy directory. And then we touch the REDEPLOY file to trigger the auto-deploy.
Many of the steps above are manaul (exploding the archive, copying) and we feel there might be easier and better way to do achieve this.
I am thinking of to create a ant wrapper with below tasks:
1. explode: just explodes the ear. This can be used in task 3.
2. deployJava: This is for java file changes. This will mvn compile on java source, copy to the weblogic autodeploy
3. deployWeb: This is for jsp/html file changes. This will copy to the weblogic autodeploy
4. deployApp: This will compile the entire app, explode, copy to autodeploy, create a REDEPLOY file, touch it.
Any suggestions on if there are better ways to do this using maven and without using Ant etc. will be very helpful.
Each one of us, teach(at least) one. <br />-Mahatma Gandhi