I'm pretty sure I've seen a tomcat6 package too. I'll take a look at your links once I get my hands on my laptop.<br><br>--<br>On my phone,<br>Dridi<br><br>On Wednesday, October 23, 2013, Robert Rati <<a href="mailto:rrati@redhat.com">rrati@redhat.com</a>> wrote:<br>
> Here's a listing of the directory structure hadoop and similar bits produce in their builds:<br>><br>> <a href="http://paste.fedoraproject.org/48849/13825327">http://paste.fedoraproject.org/48849/13825327</a><br>
><br>> There's a some stuff in there that's can obviously be paired down. Here's the script used to start/stop the service:<br>><br>> <a href="http://paste.fedoraproject.org/48852/38253290">http://paste.fedoraproject.org/48852/38253290</a><br>
><br>> It should be noted that upstream hadoop, and its ecosystem, use tomcat 6.x and as part of packaging it we've moved forward to tomcat 7.x.<br>><br>> Rob<br>><br>> On 10/22/2013 12:27 PM, Dridi Boukelmoune wrote:<br>
>><br>>> I've installed tomcat 7 on my machine to take a quick look at how it's packaged:<br>>> - exploded FHS-compliant layout<br>>> - systemd-friendly equivalent to catalina.sh<br>>> - default configuration in /etc<br>
>><br>>> Now if you want to run a tomcat instance (by instance I mean<br>>> $CATALINA_BASE) /usr/sbin/tomcat seems to be the best candidate.<br>>> Unlike catalina.sh, it expects a value for all the CATALINA_* variables<br>
>> in its environment, while catalina.sh has fall-backs relative to<br>>> $CATALINA_HOME. Simply using /usr/sbin/tomcat as a substitute to<br>>> catalina.sh wouldn't work of course.<br>>><br>>> Could you please post an example of what maven produces ? This would<br>
>> help see what could be done with simple maven configuration (eg.<br>>> -Dsystem=properties) and what would require a patch (and help estimate<br>>> the amount of work).<br>>><br>>> Dridi<br>
>><br>>> On Tue, Oct 22, 2013 at 4:59 PM, Robert Rati <<a href="mailto:rrati@redhat.com">rrati@redhat.com</a>> wrote:<br>>>><br>>>> The lack of the tomcat shell scripts is causing issue with hadoop and some<br>
>>> of their ecosystem packages. Some are webapps with custom configuration.<br>>>> The maven builds all create a tomcat install area with their custom<br>>>> configurations. It's not too hard to take that and adapt to fedora's tomcat<br>
>>> if the schell scripts were packaged. Then these services could be<br>>>> stopped/started with systemd like other services.<br>>>><br>>>> That's assuming catalina.sh and friends are present and functional. :)<br>
>>><br>>>> Rob<br>>>><br>>>><br>>>> On 10/21/2013 04:42 PM, Dridi Boukelmoune wrote:<br>>>>><br>>>>> Hi,<br>>>>><br>>>>> The catalina.sh script work with the $CATALINA_HOME (tomcat binaries)<br>
>>>> and $CATALINA_BASE (tomcat instances) directories. My guess is that<br>>>>> tomcat is packaged as a native (previously sysvinit, and now systemd)<br>>>>> service, and that instances wouldn't make sense. Other scripts like<br>
>>>> startup.sh are just sugar wrappers to the catalina.sh script.<br>>>>><br>>>>> When I say it wouldn't make sense, I mean that it was probably<br>>>>> packaged to feel like any other server:<br>
>>>> sudo service tomcat start<br>>>>> or<br>>>>> sudo systemctl start tomcat<br>>>>><br>>>>> The package probably owns directories in /var (or somewhere else) that<br>
>>>> would make it multi-instance unfriendly.<br>>>>><br>>>>> The catalina.sh script also expects sub-directories in $CATALINA_HOME<br>>>>> and $CATALINA_BASE. I suspect that tomcat explodes the directory<br>
>>>> layout (in /usr, /var, maybe /etc) in order to be FHS compliant, which<br>>>>> would probably break catalina.sh and its friends.<br>>>>><br>>>>> I'll install tomcat and take a look at the package ASAP.<br>
>>>><br>>>>> Dridi<br>>>>><br>>>>> On Mon, Oct 21, 2013 at 9:07 PM, Robert Rati <<a href="mailto:rrati@redhat.com">rrati@redhat.com</a>> wrote:<br>>>>>><br>
>>>>> I logged a bz (<a href="https://bugzilla.redhat.com/show_bug.cgi?id=990588">https://bugzilla.redhat.com/show_bug.cgi?id=990588</a>) to<br>>>>>> request that the tomcat shell scripts (catalina.sh and the rest) be<br>
>>>>> packaged. I've had some discussions with the person the bz is assigned<br>>>>>> to<br>>>>>> and few others, but no one knows why the scripts were not packaged. Nor,<br>
>>>>> it<br>>>>>> seems, does anyone see a problem with them being packaged as far as I can<br>>>>>> tell.<br>>>>>><br>>>>>> Does anyone know some history here?<br>
>>>>><br>>>>>> Rob<br>>>>>> --<br>>>>>> java-devel mailing list<br>>>>>> <a href="mailto:java-devel@lists.fedoraproject.org">java-devel@lists.fedoraproject.org</a><br>
>>>>> <a href="https://admin.fedoraproject.org/mailman/listinfo/java-devel">https://admin.fedoraproject.org/mailman/listinfo/java-devel</a><br>>