Ken,
I'm a little confused on a couple of your points. What is "maven -o"? I
never mentioned it in my email, the instructions tell us to use "maven
build". What I really wanted to know was if just doing the maven build for
the module I'm changing is sufficient or if the whole project needs to be
rebuilt.
Your last paragraph has me totally perplexed. Put the "docroot" directory in
what source? Where are the jar files you mentioned supposed to be copied to?
What does "deploying your source" have to do with any of this?
Mike
On 6/2/07, Ken Paulsen <Ken.Paulsen_at_sun.com> wrote:
>
>
> After that you can do a maven -o build like you mentioned, you may also
> want to do a "clean" to start fresh. After a build you'll have to restart
> the server.... however, if you just change .jsf files (after the debug flag
> is turned on), then you can see the changes immediately. However, if these
> files are in a jar file (they are by default), then you won't be able to
> change them. You can look at the deployed version of the files in
> AS_HOME/lib/install/applications/admingui/adminGUI_war/.
>
> Optionally, you can deploy the "docroot" directory in the source.... but
> you need to copy in a few jar files (see the
> lib/install/applications/.../WEB-INF/lib/*.jar to see what jar files should
> be there. The advantage of deploying your src directory is that you can
> modify the changes in the source and see them in the browser instantly (for
> .jsf-type changes). Also, I think a simple "ant clean build" will rebuild
> the admin gui when setup this way vs. using maven.
>
> Ken
>
>