|Status:||Released||Start date:||May 06, 2016|
|Sprint:||gCube Release 3.11.0 - gCore|
|Wiki Updates:||NO||Version Control System:|
#3 Updated by Maria Di Girolamo over 3 years ago
- Status changed from Under Integration to Build Issue
- Subject changed from org.gcube.execution.RRPlugins.1-1-2-1 to org.gcube.execution.RRPlugins.1-1-2-1(gCore)
Please could you remove from the configuration's component the dependency for the org.gcube.execution.rraggregator?
As reported in the build36 [[http://eticsbuild2.research-infrastructures.eu/BuildReport/bdownload/AllBuilds/org.gcube.3-11-0-gcore/BUILD_36/reports/reportModuleDetail-org.gcube.execution.RRPlugins.html]], this component fails for this component because cannot collect the dependency for the org.gcube.execution.rraggregator.
#4 Updated by Nikolas Laskaris over 3 years ago
- Wiki Updates NO added
This component along with all other which belong in registry (the ones begin with rr* or resource-registry* ) are planned to be replaced or removed within the very next months, according to the refactoring of Index, Execution and Search subsystems (there is a corresponding ticket https://support.d4science.org/issues/1438). So, we can add all the resource registry components into this gcore release, and remove them completely when the ticket is done? Is this an acceptable way or should i do something different? Please, let me know which is the best way.