On Jun 11, 2007, at 10:15, Matt Raible wrote:
On 6/11/07, Adam Sherman <[EMAIL PROTECTED]> wrote:
On Jun 8, 2007, at 14:50, Matt Raible wrote:
> What do you mean when you say "converted" - war:inplace or
> appfuse:full-source?
war:inplace, was I suppose to use appfuse:full-source instead? (All I
want is to be able to run Jetty on editable files.)
full-source is a bit more drastic than war:inplace but it has the same
effect. full-source makes your project more like AppFuse 1.x, where
you have all the sources in your project. With war:inplace, it's more
like a temporary copy, where you're expected to delete unmodified
files, but checkin modified ones.
I didn't like the idea of having to delete stuff on a regular basis. :-)
I actually solved the problem by removing src/main/webapp/WEB-INF/
classes/applicationContext-resources.xml. A lot of files got copied
into that classes directory that shouldn't have, I think. Same with
WEB-INF/lib.
Yeah, you should be able to delete all the files you already have in
src/main/resources (since there will be duplicates). You can also
delete WEB-INF/lib and WEB-INF/classes/your/package/name. You'll need
to retain WEB-INF/classes/org/appfuse because the jetty plugin is
unaware of the warpath plugin (which reads dependencies from war
files).
Indeed, this works perfectly. So now I have it both ways: I can run
jetty:run and upgrades to the next version of AppFuse will only
involve src/main/webapp/WEB-INF/classes/.
See any issues with this?
Thanks,
A.
--
Adam Sherman
Technologist
+1 (613) 797-6819 | http://www.sherman.ca/ | sip:[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
