So it looks like we need to re-evaluate the future intent of hot-
deploy. Should it remain a "drop, pray & test" method of deployment
for development scenarios or should it be consider a full-fledged
primary method of deploying final version of apps?.
- sachin
On Apr 5, 2006, at 3:09 PM, Bruce Snyder wrote:
On 4/5/06, Sachin Patel <[EMAIL PROTECTED]> wrote:
Could we just provide a single status file for all archives with info
like... This way rather then a user having to traverse directories
all the info is available in the single file.
ARCHIVE, LAST PUBLISH TIME, LAST PUBLISH STATE, LAST PUBLISH MESSAGE
This is certainly an interesting idea and maybe a step toward
versioning of apps that are deployed in Geronimo. I like this idea a
lot, but I'm curious to discuss this in more detail. Based on the
proposed status above, how will this work when there are many copies
of a given app? Will the deployer subsystem need to rake all of these
files and then determine the version to actually deploy? I think we
need a richer model than that, especially when considering clustering.
Bruce
--
perl -e 'print unpack("u30","D0G)[EMAIL PROTECTED]&5R\"F)R=6-E+G-N>61E<D\!
G;6%I;\"YC;VT*"
);'
Apache Geronimo (http://geronimo.apache.org/)
Castor (http://castor.org/)
