I'll review these documents, as this should no longer be necessary.
- Brett
On 01/03/2007, at 1:44 AM, Thierry Lach wrote:
I'm very much in favor of being able to download a war or an ear
and drop it
in place.
But...
So far some of the instructions that I've seen make a "download-and-
install"
approach difficult.
For example, changing the application name and email subject line
require
editing a plexus configuration file under the WEB-INF/classes
directory (
http://docs.codehaus.org/display/CONTINUUMUSER/Deploying).
I don't see such modifications as removing a jar file from the lib
directory
(as suggested for the derby jar in
http://docs.codehaus.org/display/CONTINUUMUSER/Continuum+on+Tomcat)
as being
a problem, given the graphical zip file editors that are available,
but
editing and replacing a configuration file inside a war or an ear is a
little more complicated (and therefor error prone). Also, such
manual edits
cannot be easily automated.
On 2/28/07, Brett Porter <[EMAIL PROTECTED]> wrote:
We should be able support anything people can test and document.
The best tested will probably remain the plexus app server and/or
jetty, using derby.
- Brett
On 01/03/2007, at 12:41 AM, Hilco Wijbenga wrote:
> On 2/28/07, Emmanuel Venisse <[EMAIL PROTECTED]> wrote:
>> users download the war file and deploy it, they can use the
>> standalone app too.
>
> Is the WAR expected to run on any app server? Or are we going to
> support a specific app server? Or a few?
>
> What about databases? Are we going to assume Derby? I'd be fine
with
> that, just checking.