Hi @luddaniel and thanks for your mail via the google group. https://groups.google.com/g/dataverse-community/c/YQgMEpSX360
And thanks for hanging with the containers nerd earlier today - as discussed there, let's release a 6.0.1 with JDK8+ compatibility to restore working builds for people.
I just pushed a little sth. to make the CI release such artifacts...
Could you check if it works for you by using the 6.0.1-SNAPSHOT on Maven Central?
You might need to enable the snapshot repos though, depending on your forks status
Please let me know if this works for y'all, then I'm happy to tag and push a 6.0.1 release
Pretty sure @Philip Durbin would do the honors of informing people... :stuck_out_tongue:
I just tested https://s01.oss.sonatype.org/content/repositories/snapshots/org/dataverse/unf/6.0.1-SNAPSHOT/unf-6.0.1-20230914.142442-1.jar and it seems to work :)
cp unf-6.0.1-20230914.142442-1.jar /home/ludan/.m2/repository/org/dataverse/unf/6.0/unf-6.0.jar
mvn package BUILD SUCCESS with Java 11
Haha that's another way of using a snapshot :grinning_face_with_smiling_eyes:
<dependency>
<groupId>org.dataverse</groupId>
<artifactId>unf</artifactId>
<version>6.0.1-SNAPSHOT</version>
</dependency>
[ERROR] Failed to execute goal on project dataverse: Could not resolve dependencies for project edu.harvard.iq:dataverse:war:5.14: Could not find artifact org.dataverse:unf:jar:6.0.1-SNAPSHOT in central-repo (https://repo1.maven.org/maven2) -> [Help 1]
hum looks bad, what do you think ?
Yeah... That's what I expected to see
Did you enable the snapshot repo?
mvn config ?
Here's how this looks like in DV 6.0:
https://github.com/IQSS/dataverse/blob/92404af076e51dd3799b23f00b1d45bf56885607/modules/dataverse-parent/pom.xml#L417-L438
Depending on the DV version you are using in your fork, you might already have these entries in the parent module, but probably commented out.
thanks
Does it work yet?
@Philip Durbin wanna practice releasing one more time?
Downloaded from oss-sonatype: https://s01.oss.sonatype.org/content/repositories/snapshots/org/dataverse/unf/6.0.1-SNAPSHOT/unf-6.0.1-20230914.142442-1.jar (51 kB at 124 kB/s)
BUILD SUCCESS :)
Hrhr
Glad to hear that!
what a maven storm machine ^^
@Philip Durbin it's all yours if you would like to do the honors
I just posted this to the group: https://groups.google.com/g/dataverse-community/c/YQgMEpSX360/m/iAOyZF38AQAJ
I suspect @Philip Durbin to be scoffing some lunch and going to standup, then frontend meeting. So might take a while until he responds back if he wants to actually cut the release. Please check back tomorrow (as our workday is coming to an end when living in CEST)
that's fast enough for me, I'm not in a rush. Thank you guys anyway ;)
No worries, anytime
@Oliver Bertuch ah, so you didn't make a pull request. Just pushed to master? Nothing for me to review? /me puts his feet up :big_smile:
Nope, nothing to Review. Sorry but without pushing to Master no snapshot
Worst case scenario would be Syntax error in workflow file
And it worked! Just like that! (Trivial change though)
And you did it all it a single commit with no mistakes?!? :robot: https://github.com/IQSS/UNF/commit/dfa4be3c457d886b265d4e0dcac42af8fc8a6339
@Philip Durbin - @Péter Pallinger is asking for a release of 6.0.1. Do you still want to do the honors or should I?
@Péter Pallinger would you be able to give the snapshot a try? Just want to make sure it really works before putting out a 6.0.1. Thx!
Oh! I should do the release. It would be good practice for me.
Please go ahead! :smiling_face:
Done! https://github.com/IQSS/UNF/issues/5#issuecomment-1725411589
Done! https://repo1.maven.org/maven2/org/dataverse/unf/6.0.1/
@Péter Pallinger we'd be glad to get feedback if 6.0.1 works for you! Out now! Let us know!
@Oliver Bertuch Dataverse 5.13 build works with UNF 6.0.1 , but it needs changing the pom.xml to explicitly use 6.0.1.
This is not a big problem for us, as we use a fork anyway, but anyone trying to install the standard 5.13 tag will still have problems.
Great that it works for you! It is indeed intended to help people running forks, so can change the version number.
There is no way to take back that 6.0 release anyhow
I can think of use cases where it is still problematic, so there should at least be a warning somewhere...
Also: anyone not building their own version but using the standard releases (WAR file) won't be bothered with this
ok, that is most probably true...
Not just "most probably" :wink: The WAR file contains all Java dependencies, nothing will be downloaded from anywhere.
Not as long as you won't build your own release package
I mean the war route is OK, but there is a tiny chance that someone tries to build the stock version for whatever reason :)
Oh yeah well... :shrug: Sounds like they'll need to update this tiny thing then...
For example, I did just that when I realized my fork does not work, and tried to check whether we did something wrong, or the build environment was somewhow bad on a new VM
How important is it that we switch to 6.0.1 in the develop branch?
Sure. No way around that. It was a mistake to not include backward compatibility, but what's done is done. We cannot make Maven present some warning message. There is a thread on the mailing list about this and people do find us here. If you have a good idea where else we can add a warning, please let us know @Péter Pallinger :smile:
Philip Durbin said:
How important is it that we switch to 6.0.1 in the develop branch?
Technically not at all.
ok, thanks
@Péter Pallinger here's the UNF thread, started by @luddaniel - https://groups.google.com/g/dataverse-community/c/YQgMEpSX360/m/GUqvuJDzAQAJ
@Oliver Bertuch I accepted the default for the next snapshot: 6.0.2. Is that what you would have done? I guess the other option is 6.1.
Fine with me
That lib does not have a release policy
Guess we can close this topic as resolved.
Oliver Bertuch has marked this topic as resolved.
Last updated: Nov 01 2025 at 14:11 UTC