Grouper Developers Forum

[Chris Hyzer <>]

Yeah, I was considering that also, though it is a separate instance… the binary is good to have separate since people who aren’t installing the main grouper system might download that (e.g. people in not the central IT dept), and the non binary is good since there is a build script for the client so people can generate a .tar.gz for their department people…   make sense?

 

Chris

 

From: [mailto:] On Behalf Of Tom Zeller
Sent: Thursday, December 11, 2008 2:04 PM
To: Chris Hyzer
Cc: Grouper Dev
Subject: Re: [grouper-dev] Action Items: Grouper Call 10-Dec-08

 

I'm thinking perhaps we should avoid another distinct package (as you said or like I heard on the call, we've done a good job rolling gsh, usdu, findbadmemberships into the API to avoid versioning snafus).

 

How about providing grouperClient.jar and grouper.client.properties in the API in lib/ and conf/ ?

 

On Thu, Dec 11, 2008 at 12:03 PM, Chris Hyzer <> wrote:

My vote is core, I think it is very useful and should be easily accessible… and that is my understanding of our discussing during the call.   I have a tar.gz and a binary.tar.gz for it…  if we can have two links.

 

Thanks,

Chris

 

From: [mailto:] On Behalf Of Tom Zeller
Sent: Thursday, December 11, 2008 12:59 PM
To: Grouper Dev
Subject: Re: [grouper-dev] Action Items: Grouper Call 10-Dec-08

 

On Thu, Dec 11, 2008 at 8:52 AM, Emily Eisbruch <> wrote:

*New Action Items*  

 

[AI] (TomZ) will modify the software download page to reflect the new Grouper client.

 

Is the Grouper client considered a 'core' package just like the API, UI, and WS ? If so, we need a grouper-client.tar.gz, right ? 

 

Or should the Grouper client be linked under Contributed Software and left as a source download via cvs ?

 

Guidance please ...