The following are known issues in this release:
DEPOT-4: Maven indexer exception while crawling a public Maven repo halts futher processing and sets incorrect status against repo being indexed
Indexing a public Maven repository throws an exception causing no further artifacts to be indexed. The repository being indexed incorrectly shows a status of “Ready” in the Depot UI.
DEPOT-8: Clicking a deployment profile in Scheduled Tasks displays blank page
To edit the schedule, click Edit; clicking the deployment profile link doesn’t work.
DEPOT-10: Deployment profile fails to list all applications added to the profile by drag and drop
Drag and dropping applications in the deployment profile editor doesn’t work when more then one application is being moved
DEPOT-11: Deployment Profile name is changed to default name after selecting ‘Schedule Deploy on Save’
Edits to the deployment profile name are not persisted when you select Schedule Deploy on Save and then click Save.
DEPOT-13: ‘Deploy on Save’ fails to publish profile after you edit a scheduled deploy
When a deployment profile has a schedule already associated with it, you cannot deploy it straightaway by editing it and selecting Deploy on Save. You need to delete the scheduled deployment and re-edit the draft profile to publish immediately.
DEPOT-18: Schedule on deploy doesn’t work on published deployment profiles
You can only schedule deployment on draft deployment profiles; scheduling a deployment on a published draft does not work.
DEPOT-31: Configuration overrides do not play well with versioning of deployment profiles
If you override a deployment profile’s configuration variables, the changes are applied immediately to the currently versioned profile. We do not recommend using configuration variables if you may need to roll back to previous versions of your deployment profiles.
DEPOT-32: Editor layout needs clean-up
Elements in the UI editor pages are not aligned properly and have different widths.
DEPOT-38: Agents spit out exceptions every second if Depot goes down
Shutting down the Depot server without shutting down all the containers that have ClouodMix agents running results in a constant stream of Java exceptions.
DEPOT-39: Uninstalling a feature from ServiceMix 4 can render the agent useless
This is a bug in ServiceMix 4 (ESB-520)
DEPOT-41: When a deployment fails, agents need to recover gracefully
A failed deployment can result in features that are only semi-installed.
DEPOT-45: ‘Index now’ action creates scheduled task for 23:59
If the Index now action does not complete successfully, a scheduled index task set to run at 23:59 is persisted
DEPOT-57: Does not work with FUSE ESB 4.1
The SMX 4 agent does not start in FUSE ESB version 4.1.0.0. To workaround, use FUSE ESB 4.0.0.x.