First off, Maven may not be the right tool for every person/project. If you already have a good build process in Ant that you're happy with, its not always true that you should move to Maven.
In this case, I would "only" use Maven to build up a complete webapp when you are ready to deploy, or when your non-JSP code changes. There are ways to explode the WAR after packaging, I'm not using it so I can't tell you details. I believe the goal is war:explode... maybe someone else who is using exploded WARs will respond with more info?? I would write an Ant script to copy the JSPs into the exploded directory so when your JSPs change, you can just copy them with a quick "ant jsp" command. There are probably ways to do this with Maven as well (using Antrun or perhaps Assembly) but there's no particular reason why you must do it in Maven, so I'd just do it in plain old Ant as it is simpler. Point your app server at the exploded directory and run the webapp from there, jsps will be automatically picked up, etc. Wayne On 3/8/06, chetan mehrotra <[EMAIL PROTECTED]> wrote: > We are in the process of converting our project from Ant based built to > Maven one. Till now we were using weblogic split directory structure for the > devlopment. As in that we do not need to make the ear/war for every little > changes. How to do this with Maven. > > If split is not directly possible then can we have a exploded directory > structure.Or any other way to avoid making ear/war everytime. We also want > this option for working on JSP's . As we generally deploy from the > exploded/split directory so any changes done in the jsp are immediatly > reflected. > > Any suggestion on achieving this would be helpful. > > -- > Chetan Mehrotra > >
