Story #7506
Updated by Ben Leinfelder almost 9 years ago
This is to track libraries that will need to be updated and released as 2.0.1 artifacts. Some have changes on trunk to be merged into the branch, others need to have their poms updated to pull the updated libraries and remain consistent on the CN.
Changed directly:
* d1_cn_common
* d1_identity_manager
* d1_portal_servlet
Dependencies in chain to update
* d1_cn_noderegistry
* d1_cn_index_processor
* d1_cn_index_generator
* d1_cn_service
* d1_cn_rest_proxy
* d1_cn_rest TBD: other cn components that use d1_cn_common (replication, synchronization, log_agg, etc)
Required for release - cn-buildout
* dataone-cn-portal
* dataone-cn-rest-service
* (?) dataone-cn-os-core
Other libraries that use d1_cn_common (update to keep all the CN using the same lib versions?) cn-buildout (dataone-cn-portal, dataone-cn-rest-service, and perhaps dataone-cn-os-core)
* d1_cn_tools d1_cn_service
* d1_replication d1_cn_rest_proxy
* d1_solr_extensions
* d1_synchronization d1_cn_rest
Changed directly:
* d1_cn_common
* d1_identity_manager
* d1_portal_servlet
Dependencies in chain to update
* d1_cn_noderegistry
* d1_cn_index_processor
* d1_cn_index_generator
* d1_cn_service
* d1_cn_rest_proxy
* d1_cn_rest TBD: other cn components that use d1_cn_common (replication, synchronization, log_agg, etc)
Required for release - cn-buildout
* dataone-cn-portal
* dataone-cn-rest-service
* (?) dataone-cn-os-core
Other libraries that use d1_cn_common (update to keep all the CN using the same lib versions?) cn-buildout (dataone-cn-portal, dataone-cn-rest-service, and perhaps dataone-cn-os-core)
* d1_cn_tools d1_cn_service
* d1_replication d1_cn_rest_proxy
* d1_solr_extensions
* d1_synchronization d1_cn_rest
