On 20 Jan 2003, Joe Phillips wrote: > I don't know what you mean by the default deployment. jboss-tomcat is > it's own, optional package. Note that jboss-server-all and > jboss-server-default depend on jboss-tomcat. The deployment that my > packages install is straight out of the binary release from sourceforge. > > <lightbulb> Are you saying that the non-tomcat binary releases are > configured for jetty? </lightbulb> If so, I was not aware of that. I > figured they were jboss without any web containers. I'll need to look > into this.
er, EEK! You're building from a binary release? BAD BAD > > Tomcat is an optional extra and really should be presented that > > way. Alternately you should have a jboss-jetty deb that is > > the default webcontainer for jboss, which may be replaced by > > jboss-tomcat. > > At some point I would like to clean up the way this is built. I > certainly want to have jetty packages and be flexible enough to > add/remove tomcat and jetty. I also had postgress/mysql/hsql packages, all could be deployed at once, and used alternatives to select the prefered one. > These things will grow and improve over time. Some of your comments are > leading me toward a re-organization of the jboss install directories > which I touched on in a previous email. /usr/share/jboss/.... /var/lib/jboss/.... /var/cache/jboss/.... Then, I had /var/lib/jboss/tomcat323 and /var/cache/jboss/tomcat323. The former directory was the *new* TOMCAT_HOME path. It had an auto-generated symlink tree into /usr/share/tomcat323, /etc/tomcat323, and /var/cache/jboss/tomcat323. To make my packages work in debian, I had to fork the old tomcat 3.2.3, as when I made them, tomcat 3.x had just come out, which didn't work with jboss. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
