Re: Building Continuum - Minimal Actions?
On 12/22/06, Jesse McConnell [EMAIL PROTECTED] wrote: if you are running with the continuum-plexus-runtime then your only interaction with the jsps is through the continuum-webapp artifact...which would need to be regenerated and then reloaded in the runtime. Yes, that all makes sense; that's what I was expecting. Your only option here would be an underhanded modification of the jsps where they are unpacked and then cut and paste them back into the jsp's in the webapp for longer lasting changes...*icky* Ouch! So there's no way to have the c-p-r reload the WAR? Even if it means restarting the c-p-r? mvn jetty:run - in continuum-webapp Yes, I know about this (it's what I tried first, several days ago) but as you mentioned this is broken. Last night while working on adding a new page to Continuum I noticed that things now suddenly worked (after mvn clean install in the Continuum root) that didn't work before when I was just rebuilding and redeploying the WAR (in JBoss). (I'm new to WebWork so I've had to do a lot of trial and error.) I find this all a bit scary, the build appears rather fragile? I had expected the exact opposite because from what little time I have spent with Continuum it seems to be designed quite cleanly. Or is it just me? Maybe I'm doing weird things? All I did was add a new JSP... :-( Cheers, Hilco
Re: Building Continuum - Minimal Actions?
if you are running with the continuum-plexus-runtime then your only interaction with the jsps is through the continuum-webapp artifact...which would need to be regenerated and then reloaded in the runtime. Your only option here would be an underhanded modification of the jsps where they are unpacked and then cut and paste them back into the jsp's in the webapp for longer lasting changes...*icky* The way I have done this in the past is by using the jetty plugin in the -webapp module itself. With this I was able to make changes in the jsp's and have them show accordingly in the browser. Also it detects changes in the underlying project jars so if you build a new continuum-core jar it would automatically reload the continuum webapp in jetty. mvn jetty:run - in continuum-webapp however it looks that recently the wagon update has broken that functionality which needs to be fixed asap... for reference see http://jira.codehaus.org/browse/CONTINUUM-1073 jesse On 12/22/06, Hilco Wijbenga [EMAIL PROTECTED] wrote: On 12/21/06, Hilco Wijbenga [EMAIL PROTECTED] wrote: Not only is this quite slow but I also lose my Derby database. :-( I just found out I can set the location of my Derby database in continuum-plexus-runtime/src/conf/plexus.xml so that fixes at least part of the problem. :-) -- jesse mcconnell [EMAIL PROTECTED]
Building Continuum - Minimal Actions?
Hi, Just to reassure everyone: Continuum is building just fine. :-) My problem is that the only way I seem to be able to get changes in for example a JSP in continuum-webapp to actually show up in a browser (when using continuum-plexus-runtime) is when I run mvn clean install from the continuum root. Not only is this quite slow but I also lose my Derby database. :-( (For the record: running just mvn install [so no clean] doesn't do the trick.) Surely, there is a faster way to propagate a change in continuum-webapp? When one uses Jetty/Tomcat/JBoss all one has to do is rebuild continuum-webapp (mvn install) and redeploy the generated WAR. (Deploying a WAR isn't particularly fast either so I'd like to use continuum-plexus-runtime.) I tried running mvn install (with and without clean) in continuum-plexus-runtime and continuum-plexus-application but that doesn't seem to accomplish anything. :-( So after I make a change in continuum-webapp, what's the minimum I need to do to allow continuum-plexus-runtime to run the new webapp? Cheers, Hilco
Re: Building Continuum - Minimal Actions?
On 12/21/06, Hilco Wijbenga [EMAIL PROTECTED] wrote: Not only is this quite slow but I also lose my Derby database. :-( I just found out I can set the location of my Derby database in continuum-plexus-runtime/src/conf/plexus.xml so that fixes at least part of the problem. :-)
