X-TagToolbar-Keys: D20110322235812145 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit
Hello Tony, I think that it would be better to ship everything in a new tomcat6-extras package. As this package requires to open the RMI ports to be useful remotely, it can pose a security risk, so it's better if the user takes the initiative to install it if he really needs it. BTW, there are other ways of accessing JMX remotely nowadays, I've found Jolokia (http://www.jolokia.org/) to be quite useful, it's pure JSON over HTTP. Ludovic On 22/03/11 05:16, tony mancill wrote: > Hello Marcus and other tomcat6 users, > > I have the Debian package building the catalina-jmx-remote.jar and am > considering how best to package it. Perhaps the easiest thing would be to let > the JAR ship with libtomcat6-java and the symlink for tomcat6/lib/ ship with > tomcat6-common. An alternative would be to ship the symlink (or the symlink > and > JAR both) in a new tomcat6-extras package. (This package would include the > other extras that are don't run afoul of licensing issues.) > > Thoughts one way or another on this topic? > > Thank you, > tony > > > > > __ > This is the maintainer address of Debian's Java team > <http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers>. > Please use > debian-j...@lists.debian.org for discussions and questions. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
