[snip]
>> -----Original Message-----
>> From: Trent Rosenbaum [mailto:
trent.j.rosenbaum@...]
>> Sent: mercredi 6 décembre 2006 10:05
>> To:
user@...
>> Subject: Re: [cargo-user] [mvn] - reloadable webapps
>>
>> Yes there seems to be many layers indeed! My first thoughts were to
>> hardcode this attribute value into the generate context element, (as
>> suggested in the previous emial) but then I started to think that
>> Cargo can be used outside of development and the default of not
>> including the reloadable attribute is really a good think. That does
>> not mean that we could not allow this to be turned on but I then did
>> not understand enough about the other containers to suggest a generic
>> method of doign this. I did think of allowing this through the
>> Deployable, but again after an initial browse I simply did not know
>> enough about Cargo, (more seraching I think).
>>
>
> Ok to parametrize it, we should introduce a development mode then though Cargo Properties. I suggest adding the following property "cargo.mode.development" to the GeneralPropertySet interface and then modify the Tomcat code to use it when it generates the server.xml.
>
> When you're using m2 you would have to write:
>
> <configuration>
> [...]
> <configuration>
> <properties>
> <cargo.mode.development>true</cargo.mode.development>
> [...]
>
> Alternatively we could set this mode to be the default in the m2 plugin.
[/snip]
How about having that property like this:
<cargo.mode>development</cargo.mode>
so, tomorrow if I need to have my own custom mode extensions and handle, I can do:
<cargo.mode>integration</cargo.mode>
<cargo.mode>production</cargo.mode>
Thoughts?
Cheers,
Rahul
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email