Skip to Content.
Sympa Menu

shibboleth-dev - Re: More defined custom extensions mechanism

Subject: Shibboleth Developers

List archive

Re: More defined custom extensions mechanism


Chronological Thread 
  • From: Tom Scavo <>
  • To: Chad La Joie <>
  • Cc:
  • Subject: Re: More defined custom extensions mechanism
  • Date: Sat, 9 Jul 2005 17:26:01 -0400
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=FP8TnqAVmWmUpIEF8alb02ilCAXQOfPwYYuptXTVnZylCujbA7MJnp8tauNTCUKjrF/0suT7p/0KkHkr+qM5wtM1ZCnftr+7AGlvR8cALw/oS8XK4t8njm7qY7nMBUt+QrJUUNXNukqJvk7kuJuOcPINZKulqoyJt7aPyBAMIvs=
On 7/8/05, Chad La Joie
<>
wrote:
>
> The bugs in the build itself are also fixed.

Thanks, Chad. Will you also add the enhancements discussed earlier in
this thread?

- protect ${idp.home}
- copy custom/${ext.name}/bin to ${idp.home}/bin
- copy files in custom/${ext.name}/etc to ${idp.home}/etc

The latter clashes with the original purpose of etc/ described in the
first message of this thread. Why not break etc/ into two?

custom/${ext.name}/build ==> WAR
custom/${ext.name}/etc ==> ${idp.home}/etc

This separates the files intended for the WAR from the other files
that are simply copied to etc/.

Thanks,
Tom

PS. You've inadvertently brought back "docs" instead of "doc" in custom.

Archive powered by MHonArc 2.6.16.

Top of Page