On 28/10/2019 15:23, Christopher Schultz wrote: <snip/>
>> i. Modify files.catalina in build.xml to <exclude> the >> org.apache.catalina.ssi package ii. Modify the "package" target in >> build.xml to <jarIt jarfile="catalina-ssi.jar" .../> with the >> appropriate classes >> >> I think this is super simple to do and we should go ahead and do >> this, /now/. For embedded clients who don't care about SSI, this >> gives them a JAR today that they can simply remove from their >> bundled clients to save a little space. > > This part was easy, but the MANIFEST.MF file claims it is tomcat-trunk > and not e.g. org.apache.tomcat-ssi. I'm trying to figure out how we do > it for Tribes, but I haven't been able to find the mechanism. There > are Maven-y things in the source tree that contain the string > org.apache.tomcat-tribes but I don't think we are using them to > generate our JAR files at packaging-time. > > Can anyone point me to the place(s) where Tribes gets it's > META-INF/MANIFEST.MF values? > > Also... will this take care of OSGi, or is there something else I need > to do in addition to addOSGi="true" when building the JAR? It is res/bnd/catalina-tribes.jar.tmp.bnd It sets the various bundle properties which are what OSGi looks for when the add-osgi task runs. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
