You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While reviewing build.xml for the upstream (UKf) deployment, I notice that this one differs in a way I'm sure wasn't intended. We should probably resolve this prior to the next merge, whenever that comes up. The good news is that the change here was related to separating the download and processing phases for the eduGAIN aggregate, which I am considering doing in the UKf tooling as well for slightly different reasons: so, it may be possible to use that version instead.
The clash is that edugain.dir is defined twice in build.xml:
The way ant handles property definitions, the second of these (which turns out to be the one added in this tooling relative to the UKf version) is always ignored. That probably means that in practice, it can just be removed, but we need to validate that closely during any future merge.
The text was updated successfully, but these errors were encountered:
While reviewing
build.xml
for the upstream (UKf) deployment, I notice that this one differs in a way I'm sure wasn't intended. We should probably resolve this prior to the next merge, whenever that comes up. The good news is that the change here was related to separating the download and processing phases for the eduGAIN aggregate, which I am considering doing in the UKf tooling as well for slightly different reasons: so, it may be possible to use that version instead.The clash is that
edugain.dir
is defined twice inbuild.xml
:Line 253:
Line 265:
The way
ant
handles property definitions, the second of these (which turns out to be the one added in this tooling relative to the UKf version) is always ignored. That probably means that in practice, it can just be removed, but we need to validate that closely during any future merge.The text was updated successfully, but these errors were encountered: