Shibboleth Developers

[Tom Scavo <>]

On 5/31/05, Scott Cantor 
<>
 wrote:
> >
> > What if I wanted to use a custom deployment descriptor?  Short of
> > modifying the build file, is there a way to incorporate that into the
> > install process?
> 
> I enabled container security by modifying build.xml, yes. I suspect it will
> be addressed better later.

Oh sorry, I didn't notice that the script looks for a local
build.properties file first, which solves half the problem.  The other
half is solved by adding property idp.deployment.descriptor to
default.build.properties.  Then replace the simple copy in the build
file with this:

<if>
    <available file="${idp.deployment.descriptor}"/>
    <then>
        <property name="deployment.descriptor" 
                  value="${idp.deployment.descriptor}"/>
    </then>
    <else>
        <if>
            <available file="${configroot}/${idp.deployment.descriptor}"/>
            <then>
                <property name="deployment.descriptor" 
                          value="${configroot}/${idp.deployment.descriptor}"/>
            </then>
            <else>
                <property name="deployment.descriptor" 
                          value="${configroot}/dist.idp.xml"/>
            </else>
        </if>
    </else>
</if>
<copy file="${deployment.descriptor}" 
    tofile="${configroot}/idp.xml" overwrite="true"/>

The path to the desired deployment descriptor may be either absolute
or relative to webAppConfig/

Hope this helps (it does me :)

Tom