Grouper Developers Forum

[Chris Hyzer <>]

Btw, it’s a less valuable binary release if we have to search and replace config files, right?  Would be better if they were just ready…

 

Chris

 

From: Chris Hyzer
Sent: Monday, September 15, 2008 1:51 PM
To: 'Tom Zeller'
Cc: Emily Eisbruch; Grouper Dev
Subject: RE: [grouper-dev] standardizing build procedures

 

I was hoping we could just get rid of that process, and for things that did need replacing, finding workarounds.  Like for absolute paths in files, just use relative paths.  It will work for logs, but will this work for the hsqldb url?  Anything else in there that is replaced that prevents us from getting rid of it?

 

Chris

 

From: [mailto:] On Behalf Of Tom Zeller
Sent: Monday, September 15, 2008 12:49 PM
To: Chris Hyzer
Cc: Emily Eisbruch; Grouper Dev
Subject: Re: [grouper-dev] standardizing build procedures

 

On Sun, Sep 14, 2008 at 10:28 PM, Chris Hyzer <> wrote:

- config resources should be like ldappc (maven) in the "conf" dir, or the resources dir for that src listing, e.g. src/main/resources.  Note, is "conf" a maven standard, why is conf != resources

- there are too many config files out there, lets get rid of the Grouper src/conf config files, and not have build process which substitutes stuff.  Too many things to keep up to date 

Do you have a proposal for replacing the src/conf configs ? What do you have in mind  ?