[xwiki-devs] [VOTE] Release xwiki-commons and xwiki-rendering directly on Maven Central
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 -- Thomas Mortagne
Hi Thomas,
On 2 Oct 2017, at 10:14, Thomas Mortagne <[email protected]> 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 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. Thanks -Vincent
-- Thomas Mortagne
On Mon, Oct 2, 2017 at 10:17 AM, Vincent Massol <[email protected]> wrote:
Hi Thomas,
On 2 Oct 2017, at 10:14, Thomas Mortagne <[email protected]> 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 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.
Thanks -Vincent
-- Thomas Mortagne
-- Thomas Mortagne
+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 <[email protected]> wrote:
On Mon, Oct 2, 2017 at 10:17 AM, Vincent Massol <[email protected]> wrote:
Hi Thomas,
On 2 Oct 2017, at 10:14, Thomas Mortagne <[email protected]> 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 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.
Thanks -Vincent
-- Thomas Mortagne
-- Thomas Mortagne
0 Thanks, Caty On Mon, Oct 2, 2017 at 1:27 PM, Eduard Moraru <[email protected]> wrote:
+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 < [email protected]> wrote:
On Mon, Oct 2, 2017 at 10:17 AM, Vincent Massol <[email protected]> wrote:
Hi Thomas,
On 2 Oct 2017, at 10:14, Thomas Mortagne <[email protected]> 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 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.
Thanks -Vincent
-- Thomas Mortagne
-- Thomas Mortagne
+1 2017-10-02 12:34 GMT+02:00 Ecaterina Moraru (Valica) <[email protected]>:
0
Thanks, Caty
On Mon, Oct 2, 2017 at 1:27 PM, Eduard Moraru <[email protected]> wrote:
+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 < [email protected]> wrote:
On Mon, Oct 2, 2017 at 10:17 AM, Vincent Massol <[email protected]> wrote:
Hi Thomas,
On 2 Oct 2017, at 10:14, Thomas Mortagne <[email protected]
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 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.
Thanks -Vincent
-- Thomas Mortagne
-- Thomas Mortagne
-- Guillaume Delhumeau ([email protected]) Research & Development Engineer at XWiki SAS Committer on the XWiki.org project
+0 Thanks, Clément On 10/02/2017 01:25 PM, Guillaume Delhumeau wrote:
+1
2017-10-02 12:34 GMT+02:00 Ecaterina Moraru (Valica) <[email protected]>:
0
Thanks, Caty
On Mon, Oct 2, 2017 at 1:27 PM, Eduard Moraru <[email protected]> wrote:
+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 < [email protected]> wrote:
On Mon, Oct 2, 2017 at 10:17 AM, Vincent Massol <[email protected]> wrote:
Hi Thomas,
On 2 Oct 2017, at 10:14, Thomas Mortagne <[email protected]
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 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.
Thanks -Vincent
-- Thomas Mortagne
-- Thomas Mortagne
On Mon, Oct 2, 2017 at 12:27 PM, Eduard Moraru <[email protected]> wrote:
+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.
It's going to clone most of it in practice since every time someone build with nexus.xwiki.org as main repository in settings.xml everything that gets trough it get cloned (it's the case for many Maven central artifacts right now).
Thanks, Eduard
On Mon, Oct 2, 2017 at 11:21 AM, Thomas Mortagne <[email protected]> wrote:
On Mon, Oct 2, 2017 at 10:17 AM, Vincent Massol <[email protected]> wrote:
Hi Thomas,
On 2 Oct 2017, at 10:14, Thomas Mortagne <[email protected]> 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 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.
Thanks -Vincent
-- Thomas Mortagne
-- Thomas Mortagne
-- Thomas Mortagne
+0 Thanks, Marius On Mon, Oct 2, 2017 at 11:14 AM, Thomas Mortagne <[email protected]> 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
-- Thomas Mortagne
+0 Thanks, Alex On Oct 4, 2017 12:03 PM, "Marius Dumitru Florea" < [email protected]> wrote:
+0
Thanks, Marius
On Mon, Oct 2, 2017 at 11:14 AM, Thomas Mortagne < [email protected]> 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
-- Thomas Mortagne
participants (8)
-
Alexandru Cotiuga -
Clément Aubin -
Ecaterina Moraru (Valica) -
Eduard Moraru -
Guillaume Delhumeau -
Marius Dumitru Florea -
Thomas Mortagne -
Vincent Massol