Ignore:
Timestamp:
2018-08-14T15:50:12+12:00 (6 years ago)
Author:
ak19
Message:

All the changes (still preliminary) that use tomcat.https.port and tomcat.http.port to determine tomcat.port and write it out to build.xml. Now the server application won't quite work: it can't change the port numbers as its code only knows to write out the tomcat.port, and the actual tomcat port (https or http) will remain unaffected. But I'll fix this later, as there may be a better way to do this.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • main/trunk/greenstone3/build.properties.svn

    r32309 r32334  
    1111# but not remotely
    1212tomcat.server=localhost
    13 # The port number that tomcat is/will be run on
    14 tomcat.port=8383
     13tomcat.http.port=8383
     14tomcat.https.port=8443
    1515# Tomcat's shutdown port - this may need to be changed if you are running two or more Tomcats
    1616tomcat.shutdown.port=8305
     
    161161##listing and description of all the web services deployable on GS3##
    162162web.services.list=${base.webservice.name} for Greenstone3's core web services, QBR${base.webservice.name} for Query, Browse and Retrieve services
     163
     164## ------------------------------------------------------ ##
     165## Do not modify any properties that appear after this
     166## as they are automatically generated.
     167## ------------------------------------------------------ ##
     168
     169## The port number that tomcat is/will run on by default (i.e. for the default server.protocol value set)
Note: See TracChangeset for help on using the changeset viewer.