nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

Activiti 5.3 install does not work due to bad version number

eye

Hi everyone,

I have an interesting problem to report. I unpacked activiti 5.3 first thing this morning. I tried ant demo.install and that failed (after I cleaned up I tried again with ant demo.start just in case … but no luck). The first error that occurs is:

org.activiti.engine.ProcessEngines initProcessEnginFromResource
INFO: Exception while initializing process engine :Bad version number in .class file‍‍

I am using JDK 1.5.0_11 which worked fine till activiti 5.2 (and which I am not able to change due to missing privileges)
and JRE 1.6.0_18 and ant 1.8.2.

This setup worked (and works) with activiti 5.2. Are there any steps I can take to solve this? Or am I bound to activiti 5.2 (maybe I try to simply copy a newer JDK from another computer without installing it …)

Kind regards

Dirk

Find more posts tagged with

Comments

gaoyan

I've got the same problem with jdk1.5.0_15, ant1.8.2 and jre1.6.0_22 installed ……

eye

Hi,

I copied jdk1.6.0_13 to the target machine. As I can not install anything there I simply copied it and made JAVA_HOME point to the new directory. Bottom line is: It works now. Obviously the dependencies changed since activiti5.2. You need JDK 6 now. I am not too happy and saw this nowhere announced but on the other hand I didn't really search. Anyway. Works for me. I suggest to everyone with the same problem: Copy/install a JDK 6 to your machine and you are good to go.

Kind regards

Dirk

frederikherema1

Hi Dirk,

The goals is till to keep activiti JDK 5 compliant. A dependency slipped in with the new webapp, activiti administrator, which is compiled agianst java 6 (has 50.0 version). This will be obviously fixed in the next release.

Although the jar isn't directly used from within the engine, being on the classpath is enough to cause this issue (class is loaded by spring's DefaultListableFactoryBean, maybe something with SPI's/factories in there or whatever).

Simple workaround now is to remove the folowing jar from the /setup/files/dependencies/lib/ folder:
javaee-web-api-6.0.jar
Not sure if the activiti-administrator webapp will work as it should, we'll investigate that further. All other apps (and the engine itself) run perfectly fine without this library.

Cheers,

eye

Hi,

ah ok. In that case this will be a non-issue next month which is fine for me.

Thanks for your reply

Dirk