Subject: Grouper Users - Open Discussion List
Re: [grouper-users] ldappc-ng jars, gsh, and memory
- From: Tom Zeller <>
- To: "" <>
- Subject: Re: [grouper-users] ldappc-ng jars, gsh, and memory
- Date: Tue, 1 Feb 2011 15:09:41 -0600
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:content-type; b=OpBAlHU//bbPnGC1FeweWsqEHwOpuPzOGjXPuFrovQE2lrtHW+TwYT7oMSDCukYubG 72UPdYpAmWnVzJ8CoOzNvwCrDKQf0Fl88iLhH6bvFJuSNM3nZKMxpCOQ8qbEeNQ7uTgi 4ep5fYECH/0/wTc8v8Q41htNUfDPvZJou3Mmk=
For the archives. This thread is 4 months old, nearly forever.
> Are all of the jars (124 of them) necessary for ldappc-ng to run?
No. I chose to build ldappcng with maven primarily because it (maven)
will determine dependencies. Previously, with ant, I attempted to
select a set of minimal jars necessary to run ldappcng, but decided
that this was prone to runtime errors.
Ldappcng itself doesn't have a lot of immediate dependencies, but
ApacheDS, Grouper, and Shibboleth combined do.
- Re: [grouper-users] ldappc-ng jars, gsh, and memory, Tom Zeller, 02/01/2011
Archive powered by MHonArc 2.6.16.