Shibboleth Developers

[Chad La Joie <>]

This, along with bug 418 ($SP_HOME$ macro not expanded etc and bin files 
on SP install) have been resolved in both the trunk and 1.3 branch.

Thanks for catching these Tom.

Tom Scavo wrote:
> Confirmed.  See
>
> http://bugzilla.internet2.edu/show_bug.cgi?id=419
>
> for details.
>
> Thanks,
> Tom
>
> On 8/18/05, Tom Scavo 
> <>
>  wrote:
>
> > I'd like to revisit this problem.  I'm pretty sure there's a bug in
> > the extension build process.  Here is a particular manifestation of
> > the bug:
> >
> > - I have a subdirectory in src-conf:
> > custom/gridshib-idp/src-conf/conf
> > - There are files in this directory (of course) and they get added to
> > gridshib-idp.jar as expected.
> > - However, if I delete a file in src-conf/conf and rebuild, the file
> > *still* gets added to gridshib-idp.jar, which is a bug.
> > - Although the file has been deleted from src-conf/conf, it's still in 
> > directory
> > custom/gridshib-idp/build/classes/conf
> > which is presumably one reason why it still gets added to gridshib-idp.jar.
> > - If I manually delete the bogus files from build/classes/conf, delete
> > the entire IdP installation directory, and re-install, the deleted
> > files are *still* in gridshib-idp.jar.
> > - If I manually delete gridshib-idp.jar from custom/gridshib-idp/dist
> > and custom/lib, the bogus files disappear (finally).
> >
> > So it appears that the extension directory is not getting sufficiently
> > cleaned out prior to a build.  Can anyone confirm this bug?
> >
> > Tom
> >
> > On 8/12/05, Chad La Joie 
> > <>
> >  wrote:
> >
> > > Assuming nothing changed between the last and most current time that you
> > > ran the script than no, it won't replace the jar.  It's a feature of the
> > >  Ant copy task, unless explicitly instructed to do so, it will not
> > > overwrite an existing file with a new if there is no change (which I
> > > assume it determines by file size).
> > >
> > > Tom Scavo wrote:
> > >
> > > > Should <extension>.jar in custom/lib be replaced every time the
> > > > install target is run?  I think it should but experiments indicate
> > > > otherwise.  Is this a bug or a feature?

--
Chad La Joie             315Q St. Mary's Hall
Project Sentinel         202.687.0124