Servoy 2022.3.0

[jcompagner]

so you can't click on "64 bit"?
for me that downloads it just fine.

[mw]

It's done. I realised, that you have to click at the bottom of the tile, not in the middle.

[steve1376656734]

Does anyone know if there is a way to turn off the JAR version checking when exporting a WAR file. Servoy is flagging up an issue with JAR versions in a third party plugin (they have two JAR files with the same name but one is in a subdirectory) and we cannot now export a working version of our solution. The solution worked perfectly with the multiple JAR files on 2021.12 so should work with 2022.3 if we can just switch off the JAR checking temporarily!

Thanks
Steve

[jcompagner]

you can't turn that off
but what goes wrong for you? Because what we output are just warnings.
Are you using smartclient an those jars are references in jnlps? (they need to be at the clients machine)?

[steve1376656734]

The problem that we are having is that although these are warnings on the screen, the JAR files it considers as duplicates are not then included in the WAR file and don't appear in the plugins.properties file. This causes the plugin we are using to fail because the necessary JAR files are not there. What your code picks up as duplicates in the checkDuplicateJars() method of the WarExporter class are not really duplicates but seem to be just JAR files with the same name (but different contents).

We are speaking to the third party plugin provider to get this amended but cannot export a working WAR until this is done.

[jcompagner]

so you have 2 jars with the same name (what jars are that)?
that also don't have the correct manifest entries? (like "Bundle-SymbolicName" or "Automatic-Module-Name") which are used by default (and jar name is just a fallback)
but those 2 jars are really completely different things?

can you just rename 1 jar then?

[steve1376656734]

I tried doing the renaming of the JAR but I obviously got something wrong because the warnings went away but the JAR files were not included in the WAR. I think it may be something to do with the jnlp file but I am not a Java expert so not sure.

Having played around with it this morning I do have a (very dodgy) workaround for the moment. I export the WAR file which is then missing the JAR files, open it using WinZip, add in the missing JAR files, update the plugins.properties file to include the addtional JAR file details and then upload the amended WAR file. This works for now but is a VERY tedious process.

[emera]

If you renamed the jar, then you also need to use the new name in the jnlp.