[jbpm-issues] [JBoss JIRA] Resolved: (JBPM-2718) Database Version Issue between 4.2 and 4.3
Tom Baeyens (JIRA)
jira-events at lists.jboss.org
Wed Jan 20 07:37:47 EST 2010
[ https://jira.jboss.org/jira/browse/JBPM-2718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tom Baeyens resolved JBPM-2718.
-------------------------------
Resolution: Done
i've made sure that the version check is done based on the single ProcessEngineImpl.JBPM_LIBRARY_VERSION constant.
> Database Version Issue between 4.2 and 4.3
> ------------------------------------------
>
> Key: JBPM-2718
> URL: https://jira.jboss.org/jira/browse/JBPM-2718
> Project: jBPM
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Runtime Engine
> Affects Versions: jBPM 4.3
> Environment: OS X 10.6, java version "1.6.0_17" Java(TM) SE Runtime Environment (build 1.6.0_17-b04-248-10M3025) Java HotSpot(TM) 64-Bit Server VM (build 14.3-b01-101, mixed mode), database: MySQL 5, jBPM version 4.3
> Reporter: Nils Preusker
> Assignee: Tom Baeyens
> Fix For: jBPM 4.4
>
>
> There seems to be an inconsistency with the database upgrade between versions 4.2 and 4.3. Running the database upgrade target of the ant script ("ant -Ddatabase=mysql upgrade.jbpm.schema") will return an error message that the schema is up to date, but running test cases or my application results in this error message:
> "jBPM DB schema version (4.2) differs from jBPM library version (4.3): run the upgrade tool first."
> The workaround is to set "db.version".VALUE_ to "4.3" manually in the database, but I believe the core of the issue is that the value of "ProcessEngineImpl.JBPM_LIBRARY_VERSION" is still "4.2".
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jbpm-issues
mailing list