When you are ready to publish, there are a few things you need to do.
I'm glad you said this because I did think of it before but I totally forgot - plus the newer things:
settings.properties must be updated. This can be edited in "Tools / Skin developer". There are some new settings since you last published.
I guess you mean skin.properties?
- It shows that the skin works with jAlbum 9.4. This needs to be updated. In my case, I always (well nearly always) run a regression test in the oldest supported version of jAlbum. Don't claim compatibility with an old version where you will not do a regression test.
Yup, this is from the old. I think it 'might' work there but I don't have an older version besides that to test and I'd rather just set it to the most up-to-date version. This way it's just the most current. Besides I believe in keeping software updated.
- It shows that the skin requires Java 1.5. You should change this to at least 1.8. There's no point in allowing old unsupported insecure versions. Of course your Java compile script's parameters should match this version.
Yes. Actually I don't know what version it requires but I did disable setting to 1.5. I'm not sure what version I even have but I don't specify a version in the building now. I'll have to verify what versions I have (Linux, macOS).
- I recommend that you should add a skin family. This is helpful if you want to test with the current and previous version of a skin. jAlbum considers Reflections and "Reflections 2.0.1" to be different skins and it resets the variables when you change a project's skin. However, if these are in the same family, the settings will be retained.
How does this work?
Reflections is considered to be a legacy skin, so it no longer appears in the skins page. After publishing, you should ask Anders to restore it to the active skin list.