IdP version in the code

[Cantor, Scott]

On 7/18/14, 4:59 PM, "Brent Putman" <putmanb at georgetown.edu> wrote:
>
>I've never quite understood how that stuff worked in v3, using the Java
>package implementation manifest stuff.

That was also done in V2, but when it was copied up to V3 it never worked.

>I have wondered if it would not be simpler to just use the Maven POM data
>that it puts in the jar(s), and just pull the version string out.  It's
>already there, so we get it for free.  For example, from idp-core jar:
>
>META-INF/maven/net.shibboleth.idp/idp-core/pom.xml
>META-INF/maven/net.shibboleth.idp/idp-core/pom.properties
>
>There's a 'version' property right in the properties file.  Would
>probably be only a few lines of code to read that in as a Property
>resource and pluck that out.  Unless I'm missing something.

Yes, we could read the properties file itself I suppose.


What it was doing before is calling a Java API that pulls out some
built-in value the POM build is inserting:

[shibboleth at authdev lib]$ cat META-INF/MANIFEST.MF
Manifest-Version: 1.0
Archiver-Version: Plexus Archiver
Created-By: Apache Maven
Built-By: scantor
Build-Jdk: 1.6.0_37
Main-Class: edu.internet2.middleware.shibboleth.idp.Version

Name: edu/internet2/middleware/shibboleth/idp/
Implementation-Version: 2.4.0
Implementation-Vendor: shibboleth.net
Implementation-Title: shibboleth-identityprovider

That particular maven plugin is only running for a module that no longer
generates a jar, so it never runs.


-- Scott