https://projects.ecoinformatics.org/ecoinfo/https://projects.ecoinformatics.org/ecoinfo/ecoinfo/favicon.ico?14691340362009-02-18T19:09:38ZEcoinformatics RedmineMetacat - Bug #3824: Normalize the app deploy dir in build.propertieshttps://projects.ecoinformatics.org/ecoinfo/issues/3824?journal_id=129442009-02-18T19:09:38ZMichael Daigledaigle@nceas.ucsb.edu
<ul></ul><p>My response:</p>
<p>The problem with 3 A is that the build.tomcat.dir is not necessarily the same as the app.deploy.dir. On knb (and other systems), we deploy to a completely different directory.</p>
<p>I think the build.tomcat.dir is only used to get some tomcat libraries. I have it on my list to include those libraries in metacat and remove the build.tomcat.dir property completely.</p> Metacat - Bug #3824: Normalize the app deploy dir in build.propertieshttps://projects.ecoinformatics.org/ecoinfo/issues/3824?journal_id=129452009-02-18T19:12:45ZMichael Daigledaigle@nceas.ucsb.edu
<ul></ul><p>Referencing ticket 3777 which moves tomcat libs into metacat project and eliminates build.tomcat.dir from build.properties.</p> Metacat - Bug #3824: Normalize the app deploy dir in build.propertieshttps://projects.ecoinformatics.org/ecoinfo/issues/3824?journal_id=129462009-02-18T19:19:42ZMatt Jonesjones@nceas.ucsb.edu
<ul></ul><p>We used to include those libs back in the Tomcat 3 days, but took them out as<br />the servlet library jars changed in Tomcat 3, 4, 5, and 6. So now we use the<br />locally installed version of the jar that comes with Tomcat to build. We<br />should consider whether adding these jars to Metacat is really an advantage --<br />we have to have Tomcat, and we have to differentiate which version of Tomcat is<br />being used in order to find the right jar file for servlet support. Having<br />those be in Metacat may not gain us much, and we'd have to differentiate which<br />to use in any given build. I'd opt for improving the build logic to discover<br />the jar files in the locally installed Tomcat. And I agree with Duane -- it<br />would be nice if the default app.deploy.dir used the standard webapps location,<br />as that is where most people will want to put it. So, I vote for changing back<br />to:<br /> app.deploy.dir=${build.tomcat.dir}/webapps<br />Then if we need a different location in our particular install we can change it<br />as needed when we build and install locally. But the default should be the<br />standard webapps location.</p> Metacat - Bug #3824: Normalize the app deploy dir in build.propertieshttps://projects.ecoinformatics.org/ecoinfo/issues/3824?journal_id=129472009-02-18T19:30:46ZMichael Daigledaigle@nceas.ucsb.edu
<ul></ul><p>Yeah, makes sense. Unfortunately, there is another domain specific issue (to be solved) which is that the knb website build can do an automated checkout and build of metacat. That means that metacat has to be configured to build exactly for the knb site. Thus the default hard coded</p>
<pre><code>/usr/local/devtools/jakarta-tomcat/webapps</code></pre>
<p>Directory.</p>
<p>I'll look into this further for the next release.</p> Metacat - Bug #3824: Normalize the app deploy dir in build.propertieshttps://projects.ecoinformatics.org/ecoinfo/issues/3824?journal_id=129482013-03-27T21:24:40ZRedmine Admin
<ul></ul><p>Original Bugzilla ID was 3824</p>