IdP version in the code
Cantor, Scott
cantor.2 at osu.edu
Fri Jul 18 16:48:00 EDT 2014
On 7/18/14, 4:46 PM, "Cantor, Scott" <cantor.2 at osu.edu> wrote:
>On 7/18/14, 4:43 PM, "Ian Young" <ian at iay.org.uk> wrote:
>
>>
>>On 18 Jul 2014, at 21:29, Cantor, Scott <cantor.2 at osu.edu> wrote:
>>
>>> I thought that at one point, but since V2 didn't appear to have such a
>>> manifest, I had the impression it defaulted somehow.
>>
>>Didn't someone report that in fact this wasn't working in V2?
>
>I think some people have, but I've run the code myself in V2 and it seemed
>to work. I don't know how or why. It's extremely convoluted, presumably
>for the purpose of avoiding having to maintain a version string, but
>sometimes manual is the simplest.
I finally re-tracked it down, the way it works is with a maven-jar-plugin,
it injects the version manifest into the built jar, it's not in the source
tree. So the version is derived from the POM at build-time.
And this doesn't work for V3 right now because the idp-conf POM never
actually builds a jar.
-- scott
More information about the dev
mailing list