In addition to addressing numerous bugs, this 4.1.1 release includes the initial design work of the Fedora 3 to 4 tooling, a Vagrant box, ontology updates and improvements to the Java Client and Camel Component.
Updates
Fedora 3 to 4 Migration
Designed FOXML-based migration utility
Related JIRA Issue
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
Camel Component
Added support for transactions
Related JIRA Issue
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
Repository Ontology
Added link to previously published version of ontology in the source document
Removed fedora:status term from repository ontology
Related JIRA Issues
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.
Fedora Java Client
Added ability to create version snapshots
Related JIRA Issue
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
Deployment
Created Vagrant project which includes
Fedora 4 repository
fcrepo-message-consumer
Solr
Fuseki
Changed one-click run artifacts to be executable jar files instead of war files
Related JIRA Issues
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.
Bugs
Updated REST behavior to return an error if a user attempts to add RdfSources to the repository that contain RDF subjects that are not repository resources
Removed mention of JCR in JMS message headers
Fixed bug which prevented successful behavior of LDP Indirect Containers
Fixed bug preventing some backups to fail
Fixed bug which allowed users with 'reader' role to unexpectedly be able to update resource properties
Updated response status code on unauthorized property update requests
Improved client-facing error messages
Reintroduced fixity button in HTML console
Fixed bug of not including all of a NonRdfSource's properties in user responses
Fixed bug which removed valid reference properties from a resource
Upgraded fcrepo-storage-policy build to work with recent code base changes
Updated fcrepo-message-consumer to properly index properties on NonRdfSources
Fixed streaming of large files in fcrepo-camel
Related JIRA Issues
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.
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.
Housekeeping
Prepared for Java 8 by ensuring compliant JavaDocs
Addressed dozens of issues flagged by our code analysis tools
Eliminated all 'Blocker' and 'Critical' issues
Updated project dependency versions, fcrepo4 and fcrepo-camel
Related JIRA Issues
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.
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.
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.
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.
All Issues
key
summary
type
assignee
reporter
priority
status
resolution
Unable to locate Jira server for this macro. It may be due to Application Link configuration.