Some comments inline... FWIW...
----- Original Message -----
1. It's 100% essential that we start marking releases with version
numbers. When you tar/gzip the package it should come out in a directory
such as roller-x.y.z.
I think this is good for the top-most level, but I expect that the top level
directory of the webapp is a stable name within that.
2. As we have been discussing there are certainly things that belong in
the downloadable package but not in the webapp itself.
Agree.
3. Eventually we should package as a .war file and not just a directory
tree for the app, and in that case it makes more sense to have an actual
bundle with the .war included, rather than making the .war the only
distribution.
I no longer rate this of high importance.
I think people typically still go editing files under WEB-INF prior to
installation, whether it is to extract a copy of or change roller.properties
or to add some JBoss or app-server-specific auxiliary web.xml stuff. For
the people that will just drop it into Tomcat and go, the .war is nice.
Otherwise, it just adds an extra unzip step before editing and repacking.
Also, with the current required-jars overlay, some repacking is also
required.
4. Using a bundle gives us much more flexibility to include other things
that may be useful to the user, but which shouldn't really be directly
included in the core webapp. themes? plugins? editors?
Agree here; we should have things outside the web app in the bundle.
I don't really think it's ideal to only package the webapp for the release
and then end up having to put things in the webapp which shouldn't be
there so that that they are in the download. It's not that hard to setup
a very simple structure for the download bundle and make it part of the
build process. I am more than willing to do this.
Overall, I agree.
-- Allen
- Dave
--Anil
