IdP version in the code

[Cantor, Scott]

On 7/18/14, 5:17 PM, "Brent Putman" <putmanb at georgetown.edu> wrote:
>
>I guess that argument for the current method would be that it's a
>natively Java approach using the manifest (which could be populated by
>any build process), as where the POM properties is specifically tied to
>a Maven build process.  But unless we're going to move away from Maven
>anytime soon, then maybe the latter is ok.  Using the POM resources
>would also mean I think hardcoding in the Version classes the path to
>them, which includes the groupId and artifactId, which I suppose could
>change at some point.

Yeah. I moderately prefer the old way I guess as compared to hardcoding
the POM information.

Where it's at now is idp-parent, not idp-conf. I'll try moving it to
idp-core, which is where the Version class is sitting for the time being.
If that works, that's something for now.

-- Scott