[Building Sakai] catalina.properties and -Dsakai.app.server=tomcat7

[Steve Swinsburg]

Once 2.10 lands and 2.8 is no longer supported, thus ending Tomcat 5.5, if we still have indies, we can adjust them to make their packaging conform to the new layout.

Though there was a discussion a while back about whether having everything in /lib was a good idea since the Tomcat jars are in there and cleaning tomcat becomes non trivial. It was suggested we have a sakai-lib dir for Sakai jars to live(same as shared/lib now essentially), but IMO that achieves nothing and you still need to adjust tomcat classloader layout which we should avoid. 

I would like everything in /lib and just have an undeploy maven mojo so that we can properly undeploy Sakai if we need to clean tomcat. Work has been started in this area, not sure of its current status though. 

Cheers
Steve



Sent from my iPhone

On 28/04/2013, at 8:53, David Adams <da1 at vt.edu> wrote:

> Well, there are lots of ways to handle setting properties. At VT, on our dev and production boxes, we have a wrapper script that calls maven with all the appropriate flags depending on what we're trying to do and which instance we are working with, so we set a local repository, tomcat path, and this setting via command line flags. For projects on my workstation, I've been inspired by python's virtualenv and ruby tools like rvm and I've worked up a small script that sets up a complete jdk/maven environment within a given project directory for me to work from, and I specify the appropriate local settings via the virtual environment's maven's settings.xml file, and just source the setup file to switch into that context. Or you could just set up an alias for mvn that adds all the flags you want in your .bashrc or .bash_aliases file. It should also work to add it to, say, master/pom.xml.
> 
> It really just depends on your personal needs. I'm not familiar with the appserver.id, appserver.home, or sakai.appserver.home settings from your settings.xml. But if you want to specify this setting in settings.xml, just add <sakai.app.server>tomcat7</sakai.app.server> to your settings.xml inside the <properties> block.
> 
> 
> 
> David Adams
> Director, Systems Integration and Support
> Virginia Tech Learning Technologies
> 
> 
> On Sat, Apr 27, 2013 at 4:56 PM, Steve Swinsburg <steve.swinsburg at gmail.com> wrote:
>> You could, but you don't actually need settings.xml, just specify the path to tomcat when you build. 
>> 
>> Cheers
>> S
>> 
>> Sent from my iPhone
>> 
>> On 28/04/2013, at 7:51, Mustansar Mehmood <mustansar at rice.edu> wrote:
>> 
>>>  Great!
>>>   
>>> I wonder if we could move this information to settings.xml. I am just trying to revisit this file 
>>> 
>>> <settings
>>>         xmlns="http://maven.apache.org/POM/4.0.0"
>>> 
>>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>>> 
>>> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
>>> 
>>> http://maven.apache.org/xsd/settings-1.0.0.xsd">
>>> 
>>> <profiles>
>>> 
>>> <profile>
>>> 
>>> <id>tomcat5x</id>
>>>           <!-- I doubt if this setting plays any role in sakai -->
>>> 
>>> <activation>
>>> 
>>> <activeByDefault>true</activeByDefault>
>>> 
>>> </activation>
>>> 
>>> <properties>
>>> 
>>> <appserver.id>tomcat5x</appserver.id>
>>>         <!--
>>>           how is this related to <id>tomcat5x</id>
>>>           -->
>>> 
>>> <appserver.home>/opt/tomcat</appserver.home>
>>> 
>>> <maven.tomcat.home>/opt/tomcat</maven.tomcat.home>
>>> 
>>> <sakai.appserver.home>/opt/tomcat</sakai.appserver.home>
>>> 
>>> <surefire.reportFormat>plain</surefire.reportFormat>
>>> 
>>> <surefire.useFile>false</surefire.useFile>
>>> 
>>> </properties>
>>> 
>>> </profile>
>>> 
>>> </profiles>
>>> 
>>> </settings>
>>> 
>>>  On 4/27/2013 1:50 PM, David Adams wrote:
>>>> Just figured this out a couple of weeks ago and wanted to let everyone know, in regards to deploying 2.9+ on Tomcat 7.
>>>> 
>>>> If you add "-Dsakai.app.server=tomcat7" to your maven command line, the sakai:deploy goal will put all your jar files in the right place--namely tomcat/lib--and the catalina.properties hack is no longer required.
>>>> 
>>>> One caveat: you have to be using the sakai-2.9.x-all branch or equivalent, since the preconstructed assembly zip files deployed by the "normal" branch obviously won't respect this setting.
>>>> 
>>>> David Adams
>>>> Director, Systems Integration and Support
>>>> Virginia Tech Learning Technologies
>>>> 
>>>> 
>>>> _______________________________________________
>>>> sakai-dev mailing list
>>>> sakai-dev at collab.sakaiproject.org
>>>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>>>> 
>>>> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"
>>> 
>>> _______________________________________________
>>> sakai-dev mailing list
>>> sakai-dev at collab.sakaiproject.org
>>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>>> 
>>> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"
>> 
>> _______________________________________________
>> sakai-dev mailing list
>> sakai-dev at collab.sakaiproject.org
>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>> 
>> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20130428/3d2573f2/attachment.html