Today you cannot build Web UI without access to https://mavenin.nuxeo.com/nexus/#browse/search/npm=group%3Dnuxeo
We'll eventually publish to npmjs central public repo when releasing but not the snapshot.
I understand that https://packages.nuxeo.com would be publically available for this kind of purpose
In https://mavenin.nuxeo.com/nexus/#browse/search/npm=group%3Dnuxeo, we publish:
which are direct dependencies of Web UI and build by our CI. For now, it is https://qa.nuxeo.org/jenkins/job/master/job/nuxeo-elements-master/configure that push packages to mavenin.
Could we even do the same with https://packages.nuxeo.com? No
Small attempt told:
Anyway, let's say it our JenkinsX future pipeline that would be in charge -> need to update https://github.com/nuxeo/nuxeo-elements/blob/master/Jenkinsfile#L133:
in order to publish to https://packages.nuxeo.com/.
We also have forked libraries under the nuxeo scope:
We could manually publish them
So far, I am able to login to https://packages.nuxeo.com/ with a GH Personal access tokens with read:org permission. I am admin right there, couple of observation: