Skip to Content.
Sympa Menu

grouper-dev - Re: [grouper-dev] standardizing build procedures

Subject: Grouper Developers Forum

List archive

Re: [grouper-dev] standardizing build procedures

Chronological Thread 
  • From: "Tom Zeller" <>
  • To: "Chris Hyzer" <>
  • Cc: "Grouper Dev" <>
  • Subject: Re: [grouper-dev] standardizing build procedures
  • Date: Mon, 15 Sep 2008 16:20:59 -0500
  • Domainkey-signature: a=rsa-sha1; c=nofws;; s=gamma; h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version :content-type:references:x-google-sender-auth; b=YbuHI38d1i8hQxL7km/10ik5JJnxFPMgXLVTfkNDNJDQ89MrarW4c3nz/U1GTsR418 +Fc8DyQdmw20GIQrD8N4zdCblxIAB7XbzyZpyqOTapPN8Nz5xvhIfGGqJiTmink8sgr9 9XvNPWPRkAu1FXEKO8Qf+JOm6vsndbCf/JdcA=

Thanks for being patient with me, I forgot we had /src/conf and /conf, yes only one please.

On Mon, Sep 15, 2008 at 3:59 PM, Chris Hyzer <> wrote:

We have /conf, and /src/conf… I think we only need one, and it should be the maven convention (if this is the maven convention J )…    /conf    (though I don't know how /conf differs from /src/main/resources)…


When I said "get rid of /src/conf", I meant delete it, and move any non redundant files to /conf


I wasn't suggesting collocating grouper and ldappc or signet.


As far as relocating the hsql configs, if we want the binary to work when it starts, maybe they should be in the /conf dir… hmm






From: [mailto:] On Behalf Of Tom Zeller
Sent: Monday, September 15, 2008 4:54 PM
To: Chris Hyzer
Cc: Grouper Dev

Subject: Re: [grouper-dev] standardizing build procedures


Agreed, we (of course) shouldn't need a build tool (ant, maven, whatever) to run a binary release.


I wasn't sure what you meant by "get rid of" src/conf, and I think I'll understand that as "remove src/conf from the build process" :)


I also thought maybe you were suggesting colocating ldappc and grouper conf directories, maybe even signet. I'll admit to not being a grouper-expert, but I have spent some time there, and I often become confused running grouper+ui+ldappc and making sure all the various configs are correct and consistent when working with different test setups, database backends, and code versions. I'm not sure what magic can correct my confusion, though.


It would be nice to relocate the hsql configs (, sqltool.rc) out of the way, maybe to a 'quickstart' or 'test' directory.




On Mon, Sep 15, 2008 at 3:26 PM, Chris Hyzer <> wrote:

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…




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?




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  ?


Archive powered by MHonArc 2.6.16.

Top of Page