What are our current obstacles which are keeping us from packaging as a WAR 
file?  Particularly a non-exploding WAR file.

I have ...

1. we still allow some older users to write resources inside the webapp, so we 
need access to the context path.  this can probably be removed pretty soon and 
we can force everyone to keep their uploads outside the webapp.

2. we still need the context path for reading theme files.  this is tricky, but 
maybe theme files should be outside the webapp as well?  if not, then maybe 
they should be in the WEB-INF/classes directory so we can access them through 
the classpath?


can anyone think of any others?

not deploying as a WAR is one of my pet peeves with Roller and I think it's 
something we should work on pretty soon.

-- Allen

Reply via email to