You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 66
Next »
Upgrading to VIVO 1.10.0 requires Java 8 and a triple store reload
As a result of the upgrade to Jena 3, upgrading to VIVO 1.10.0 requires Java 8 and a triple store reload – your triple store most be unloaded using a provided utility, your system upgraded, and then the triple store reloaded using a second provided utility. These processes are currently in test mode. See VIVO 2.0.0 Release Testing. Please participate in testing and report findings to vivo-tech@googlegroups.com
Issues included in beta Release 2.0.0
Issues without Jiras, or without resolved Jiras may be included.
- Interface
-
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
-
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
-
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
-
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
- Data Services
-
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
- Architecture
- Vitro clean-up and improvements based on the work of Cornell
-
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
-
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
- Ontology
- Domain definition and processes. See Ontology Improvement Task Force
- Domain modularization and selectable loading of domain modules
-
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
-
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
-
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
- Ontology editing enhancements based on work of Cornell
-
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
-
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
- Data Management
-
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
See Data Loader Task Force
-
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
-
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
- Upgrade VIVO Harvester to use Jena 3.1
- Documentation
-
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
-
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
-
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
-
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
-
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
-
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
-
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
-
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
-
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
- System Administration and Development
-
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
- Other improvements and bug fixes
-
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
-
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
-
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
-
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
-
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
