2 Oct
2017
2 Oct
'17
12:27 p.m.
+1, sounds good to me.
Also, if we could setup Nexus to clone just the org.xwiki artifacts from
maven central, that might be a good compromise, but I could live without it
also.
Thanks,
Eduard
On Mon, Oct 2, 2017 at 11:21 AM, Thomas Mortagne <thomas.mortagne(a)xwiki.com>
wrote:
On Mon, Oct 2, 2017 at 10:17 AM, Vincent Massol
<vincent(a)massol.net>
wrote:
maven.xwiki.org. I think it’s important that we can have the full list of
XWiki artifacts in a single place and I’d like that to be our place. If we
were publishing all our artifacts on Maven Central, I wouldn’t have this
problem but it’s not the case.
You do have all our artifacts in one place (at least from browser
point of view) trough nexus.xwiki.org.
Hi Thomas,
> On 2 Oct 2017, at 10:14, Thomas Mortagne <thomas.mortagne(a)xwiki.com>
wrote:
Hi devs,
To remove a big step from the release I would like to modify a bit our
setup and deploy released xwiki-commons and xwiki-rendering artifacts
on Maven Central instead of nexus.xwiki.org/maven.xwiki.org.
PRO:
* speed up releases
* less stuff to store on our side
* only one artifact for a specific version (right now they are built
twice which produce two different JARs in pratice)
CONS:
* depends more on Maven Central
In practice we already depend on Maven Central for many things so if
Maven Central ever end up dead the fact that we don't have the
artifact on our side is going to be the least of our issues :)
So WDYT ?
+1 on my side
+1 to automate the release on Maven Central for commons/rendering.
-0 (close to -1) to not releasing/copying commons/rendering artifacts on
Thanks
-Vincent
--
Thomas Mortagne
--
Thomas Mortagne