Page 16 of 16

Re: Test builds for 3.3.0

PostPosted: April 28th, 2020, 7:24 am
by ClaudioC
Thanks TO YOU for the hard work. I might speak only for myself, but we were only supporting you.

Re: Test builds for 3.3.0

PostPosted: May 3rd, 2020, 1:42 am
by alanesh
Hey all, I've been working on a module, almost finished, but I have been using v3.3.0 betas while doing so. I've belatedly decided I want users who are on v3.2 to be able to open my module, is even that possible now?

If I change the VassalVersion in the buildFile to 3.2.17, will that allow my module to be opened with that version of vassal? Thanks!

Re: Test builds for 3.3.0

PostPosted: May 3rd, 2020, 9:28 am
by marktb1961
alanesh wrote:Hey all, I've been working on a module, almost finished, but I have been using v3.3.0 betas while doing so. I've belatedly decided I want users who are on v3.2 to be able to open my module, is even that possible now?

If I change the VassalVersion in the buildFile to 3.2.17, will that allow my module to be opened with that version of vassal? Thanks!


I’m no expert but I would expect so. Is anything stopping you from installIng 3.2.17 and tryIng it?

Re: Test builds for 3.3.0

PostPosted: May 3rd, 2020, 1:28 pm
by uckelman
Thus spake alanesh:
> Hey all, I've been working on a module, almost finished, but I have been
> using v3.3.0 betas while doing so. I've belatedly decided I want users
> who are on v3.2 to be able to open my module, is even that possible now?
>
> If I change the VassalVersion in the buildFile to 3.2.17, will that
> allow my module to be opened with that version of vassal? Thanks!

Yes, in this particular case, that should work, because there aren't
any component or file format changes in 3.3.0. (You should also update
the VassalVersion element in the moduleData file.)

It's not something you should rely on working in general, however. (There
are modules for which this would not have worked between 3.1 and 3.2,
for example.)

--
J.

Re: Test builds for 3.3.0

PostPosted: May 3rd, 2020, 2:18 pm
by alanesh
Super, thank you for the details.

Re: Test builds for 3.3.0

PostPosted: May 9th, 2020, 1:57 pm
by uckelman
New test build 3.3.0-svn9380: http://www.vassalengine.org/~uckelman/tmp/

This moves the Java bundled with the Windows and Mac builds from Java 13 (which is now EOL) to Java 14.

Re: Test builds for 3.3.0

PostPosted: May 10th, 2020, 7:35 am
by slimy
uckelman wrote:New test build 3.3.0-svn9380: http://www.vassalengine.org/~uckelman/tmp/

This moves the Java bundled with the Windows and Mac builds from Java 13 (which is now EOL) to Java 14.



I already see an svn0383. Is that the current test target?

Re: Test builds for 3.3.0

PostPosted: May 10th, 2020, 12:51 pm
by uckelman
Thus spake slimy:
>
> "uckelman" wrote:
> > New test build 3.3.0-svn9380:
> > http://www.vassalengine.org/~uckelman/tmp/[1]
> >
> > This moves the Java bundled with the Windows and Mac builds from Java
> > 13 (which is now EOL) to Java 14.
>
>
>
> I already see an svn0383. Is that the current test target?

Yes.

9381 has some code cleanup, 9382 (probably) fixes a problem with playing
WAV files on some systems (Bug 12731), 9383 has a font rendering
improvement (Bug 12732).

All three of those contain the Java 14 change from 9380.

--
J.