-
Type: User story
-
Status: Resolved
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 5.6.0-HF18, ADDONS_5.6, 5.7.1
-
Component/s: Nuxeo Drive
-
Backlog priority:420
For now nuxeo-drive is not part of the released addons, the module being declared in addons/pom-optionals.xml and not addons/pom.xml. This is because the nuxeo-drive-jsf module needs to embed the Nuxeo Drive client binaries (.msi and .dmg) which are built by the Jenkins jobs listed below, through the maven-antrun-plugin at build time.
http://qa.nuxeo.org/jenkins/job/addons_nuxeo-drive-master-msi/ http://qa.nuxeo.org/jenkins/job/addons_nuxeo-drive-master-dmg/ http://qa.nuxeo.org/jenkins/job/addons_nuxeo-drive-5.6.0-msi/ http://qa.nuxeo.org/jenkins/job/addons_nuxeo-drive-5.6.0-dmg/
This is a problem at least because:
- we need to use a separate job to release nuxeo-drive: https://qa.nuxeo.org/jenkins/job/IT-release-on-demand-addon/
- nuxeo-drive might not be released when the platform is (if we forget to do the separate release), this is an issue especially when releasing hotfixes
Instead we should use a configuration template to externalize these binaries and use the marketplace package to include it, see https://github.com/nuxeo/marketplace-drive.