Skip to Content.
Sympa Menu

grouper-dev - Re: [grouper-dev] grouper binary build proposal

Subject: Grouper Developers Forum

List archive

Re: [grouper-dev] grouper binary build proposal

Chronological Thread 
  • From: "Tom Zeller" <>
  • To: "Chris Hyzer" <>
  • Cc: "Emily Eisbruch" <>, "Grouper Dev" <>
  • Subject: Re: [grouper-dev] grouper binary build proposal
  • Date: Mon, 15 Sep 2008 16:05:44 -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=HBTDYF078ikZWp+wiYAP98PXxaQ59wSWyzVMSA7OgmPssnUS0UXI2X0rcSxuvSWwN6 /gExdJrMAykkCbbhkIvl8fr7r3GL0QSU2sx8IiA27BLp/dSuFJRr5XjUHsGQZZg5Iy3A MBGlT0bjdgMbutVui5ZE68dtYbDA9yc1kcJq8=

Please see my votes inline.


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

My proposal for a binary build is:


Gzip file: grouper.1.4.tar.gz:

/lib/grouper: all jars that grouper needs, including grouper.jar

/lib/jdbcSamples: some drivers that the user can choose from… e.g. the ones we test with.  Note, the user can use these or get their own, explained in readme

Nice. That would save me a step. Mabye we could include and sources.xml snippets for the various drivers as well (having forgotten one or the other more than once).

/conf: all resources and all config example files, and the same files with the real name.  So there would be ==

/bin: all the example scripts, and the non-examples ones: gsh.example.bat == gsh.bat (note, all line endings need to be right… note, permissions might not be right [e.g. executable in unix], should be in readme).

/ext: any extensions (note, currently there are none to bundle in… should we include this or wait until there are extensions?  )

Seems silly to include an empty directory, but I suggest keeping it for any grouper-extension-lurkers.

Should we package javadoc or other docs (or keep in cvs?)

I think web-based documentation is fine, so a link to the wiki seems sufficient. 

Should logs go to base dir, or should we auto-create dirs for logs and keep in /logs dir?

I like the logs directory rather than base dir, since if the binary grouper release is included in another project there might not be a grouper base dir. 

Anything else?






From: Emily Eisbruch [mailto:]
Sent: Friday, September 05, 2008 9:16 AM
To: Grouper Dev
Subject: [grouper-dev] Draft minutes: Grouper Call 3-Sep-08


**Grouper Call 3-Sep-08**


Tom Barton, Chair

Gary Brown, Bristol U.

Shilen Patel, Duke

Chris Hyzer, U. Penn

Bill Kasenchar, U. Penn

Tom Zeller, U. Memphis

Dave Donnelly, Stanford

Joy Veronneau, Cornell U.

RL "Bob" Morgan, U. Washington

Steve Olshansky, Internet2

Emily Eisbruch, Internet2 (scribe)


New Action Items

[AI] {Chris} will make the encrypted password function external to Grouper.

[AI] {TomZ} will create a JIRA issue summarizing today's discussion on handling of utilities by gsh.

 Carry Over Action Items

[AI] {Chris} will create a proposal for using a shell script to make binaries.

[AI] {Chris} will develop guidelines for standardizing build script procedures across the I2 middleware products.

[AI] {Kathryn} will do background research on a messaging system to be used as a test/example case for hooks.


Grouper Release 1.3.1.

Grouper Release 1.3.1 is ready for final testing and packaging, with all JIRA items having been marked completed. Chris will test web services; Chris, TomZ, and Shilen will do unit testing. Chris will tag the code for the 1.3.1 release in CVS and inform TomB.  

Binary Format for Grouper 1.4

Binary format will be considered for Grouper 1.4, not for this 1.3.1 release.

Documentation for 1.3.1

Shilen welcomes feedback on his Bad Membership Finder utility documentation at:

Gary will edit the documentation on the Grouper wiki for API configuration changes in Grouper 1.3.1.

Encrypting passwords in config files


Encrypting passwords in config files was deferred, to be reconsidered along with the release of Subject 1.0. This deferral decision was based on concern about creating a need for Grouper customized versions of 3rd party source, such as JDBC source files.  However, it makes sense now to proceed with putting encrypted passwords in a separate JAR.

[AI] {Chris} will make the encrypted password function external to Grouper.


What are the potential impacts of cleaning up and removing some indexes, as suggested in GRP-146?

There is a risk that indexes that we consider redundant are not actually redundant in all cases. Making some indexes optional through a configuration file was discussed. There is a need to understand how various databases use indexes. The decision was not to make changes to indexes for 1.4.  Soon after 1.4, it might make sense to develop test/benchmark databases to be able to make a future determination on this issue.

Packaging of Utilities

The consensus was to use gsh for storing utilities.

Utilities for 1.4 will include those needed to replace Apache Ant (Scheme export, run test, export import, XML, etc.), Bad Membership Finder, and more.

TomB noted it will be important to maintain a wiki page or interactive, built-in help so people know what utilities are in gsh.

[AI] {TomZ} will create a JIRA issue summarizing today's discussion on handling of utilities by gsh.

Next call: Wed 17-Sep-08 Noon EDT.

Archive powered by MHonArc 2.6.16.

Top of Page