Version stuck at 1.0.0

Description

After install, it reports itself as 1.0.0. I should think it would be auto-set via Maven, so might be something that needs adjusting, or perhaps the “rebuild” didn’t really hit all the modules in some way.

Environment

None

Activity

Rod WiddowsonJune 25, 2022 at 1:15 PM

… its the trailing slash on the name (again)

Rod WiddowsonJune 25, 2022 at 11:06 AM

So, even with a manifest it fails. So what it wrong with the manifest

Manifest-Version: 1.0 Created-By: Maven JAR Plugin 3.2.2 Build-Jdk-Spec: 17 Automatic-Module-Name: net.shibboleth.plugin.storage.jdbc.impl Sealed: true Name: net/shibboleth/plugin/storage/jdbc/impl Implementation-Vendor: Shibboleth Implementation-Version: 1.0.2-SNAPSHOT Implementation-Title: jdbc-storage-impl

(And I’ve done this with a JDK-11 too

Rod WiddowsonJune 24, 2022 at 9:27 AM

The reason why this is the case is that I failed to update the version in the properties file while cranking that release out.

I have amended the process to check for that in future release.

However the property is suppose to be a fallback only if the version from the pom file is not found. So the important work is to diagnose this - we have an entire jar whose only purpose is to return the version and it isn't doing that.

Fixed

Details

Affects versions

Fix versions

Assignee

Reporter

Created June 23, 2022 at 10:15 PM
Updated July 18, 2022 at 2:10 PM
Resolved June 25, 2022 at 1:24 PM

Flag notifications