Details
-
Type:
New Feature
-
Status:
Closed
-
Priority:
Critical
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 1.5-RC
-
Component/s: Core
-
Labels:None
-
User impact:High
-
Similar Issues:
GALAXY-342CommentManager 1.1 structure migrationGALAXY-344Lifecycle 1.1 migrationGALAXY-353Permission 1.1 migrationGALAXY-341PolicyManager 1.1 structure migrationGALAXY-343Index/PropertyDescriptor 1.1 structure migrationGALAXY-79Revisit how versioning and lifecycles workGALAXY-336Dependency JCR structure migration
GALAXY-378 Allow custom metadata per-artifactGALAXY-7Add new RESTful APIGALAXY-242History feed has entry/id node that can't be PUT back to galaxy without a 409 conflict error
Description
We need to implement something to move from the 1.0 JCR structure to the 1.1.
Migration from 1.0 to 1.1 is now seamless!