Chris, I agree that we really should support BOTH file:/// and / for pathing within the properties files. My goal in doing this exercise is to also update the pre-configured properties so they follow the file:/// convention. Guess I am just a little OCD about my properties files...especially when my filemanager will not restart properly because I was using a '/' instead of 'file:///'.
This is also something we came across in building out RADiX. -Cam On Wed, May 4, 2011 at 11:16 AM, Chris A. Mattmann (JIRA) <[email protected]>wrote: > > [ > https://issues.apache.org/jira/browse/OODT-187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13028872#comment-13028872] > > Chris A. Mattmann commented on OODT-187: > ---------------------------------------- > > Hi Cameron, > > I'm OK with the general principle of your issue -- however, I'd favor > either approach. That is, let's allow folks to use *either* file:// or just > plain absolute paths in each of the pathing parameters. > > Thoughts? > > > > Standardize File Pathing within filemgr.properties > > -------------------------------------------------- > > > > Key: OODT-187 > > URL: https://issues.apache.org/jira/browse/OODT-187 > > Project: OODT > > Issue Type: Improvement > > Components: file manager > > Affects Versions: 0.2 > > Reporter: Cameron Goodale > > Assignee: Cameron Goodale > > Priority: Minor > > Fix For: 0.3 > > > > > > At the moment some of the file manager properties are set with > > file:///path/to/file/or/directory > > others are set with > > /path/to/file/or/directory > > Excerpt from filemgr.properties (properties that need to be addressed) > > > org.apache.oodt.cas.filemgr.catalog.mappeddatasource.mapFile=/path/to/ops.catalog.typemap.properties > > > org.apache.oodt.cas.filemgr.catalog.lucene.idxPath=/path/to/your/lucene/index > > org.apache.oodt.cas.filemgr.mime.type.repository=/path/to/mime-types.xml > > It would really help to standardize on one. So I propose we stick with > the file:/// version since this is the URI syntax. Of course we will have > to fix this and remain backwards compatible so we will need to support both > versions. Once this issue has been addressed we also need to update the > default filemgr.properties file to reflect this change to file:/// moving > forward. > > This will help new OODT users follow a standard way to set properties. > Eventually I'd like to see this standard followed across all OODT > components. (crawler, workflow, etc....) > > -- > This message is automatically generated by JIRA. > For more information on JIRA, see: http://www.atlassian.com/software/jira > -- Sent from a Tin Can attached to a String
