Re: [onap-discuss] Staging repo in settings.xml

] On Behalf Of Gary Wu Sent: Wednesday, May 31, 2017 7:05 PM To: SPATSCHECK, OLIVER <spat...@research.att.com> Cc: onap-discuss@lists.onap.org Subject: Re: [onap-discuss] Staging repo in settings.xml Hi Oliver, There are definitely disadvantages to keeping all versions in sync, as you mentioned

Re: [onap-discuss] Staging repo in settings.xml

CHRISTOPHE <cc6...@intl.att.com>; Andrew Grimberg <agrimb...@linuxfoundation.org>; Coquelin, Sebastien <sebastien.coque...@bell.ca>; onap-discuss@lists.onap.org Subject: Re: [onap-discuss] Staging repo in settings.xml Gary, thanks for the summary. I would NOT try to keep t

Re: [onap-discuss] Staging repo in settings.xml

2:19 PM To: Andrew Grimberg <agrimb...@linuxfoundation.org> Cc: Gary Wu <gary.i...@huawei.com>; Coquelin, Sebastien <sebastien.coque...@bell.ca>; Closset, Christophe <cc6...@intl.att.com>; onap-discuss@lists.onap.org Subject: Re: [onap-discuss] Staging repo in settings.

Re: [onap-discuss] Staging repo in settings.xml

Would have to talk to all the teams to get the details but I think most artifacts need to be locked down. Please remember that since we created the 1.0.0 branch we have been contributing code based on two additional internal releases into the seed repos. This new code base has not been fully

Re: [onap-discuss] Staging repo in settings.xml

On 05/25/2017 02:36 PM, Gary Wu wrote: > That makes sense given that staging artifacts were supposed to exist > only long enough to decide whether they're good to release or not; > they were not meant to be used as long-lived build dependencies. > > I think the right thing to do is to move away

Re: [onap-discuss] Staging repo in settings.xml

VER) <spat...@research.att.com>; Gary Wu <gary.i...@huawei.com> Cc: Coquelin, Sebastien <sebastien.coque...@bell.ca>; CLOSSET, CHRISTOPHE <cc6...@intl.att.com>; onap-discuss@lists.onap.org Subject: Re: [onap-discuss] Staging repo in settings.xml On 05/24/2017 11:34 AM, SPA

Re: [onap-discuss] Staging repo in settings.xml

On 05/24/2017 11:34 AM, SPATSCHECK, OLIVER (OLIVER) wrote: > >> On May 24, 2017, at 10:54 AM EDT, Gary Wu >> wrote: >> >> 3) I understand that all the staging process was meant to be >> temporary, and to add on Gary’s last question, what is the plan >> moving forward and

Re: [onap-discuss] Staging repo in settings.xml

> On May 24, 2017, at 10:54 AM EDT, Gary Wu wrote: > > 3) I understand that all the staging process was meant to be temporary, and > to add on Gary’s last question, what is the plan moving forward and how could > we contribute to that effort ? I think that’s a TSC

Re: [onap-discuss] Staging repo in settings.xml

rew Grimberg <agrimb...@linuxfoundation.org>; onap-discuss@lists.onap.org Subject: Re: [onap-discuss] Staging repo in settings.xml Hi Christophe, Gary, Andy, I’m trying also to build projects on a local Jenkins and I’m facing some issues related to the nexus-staging-maven-plugin. I am reach

Re: [onap-discuss] Staging repo in settings.xml

lt;agrimb...@linuxfoundation.org>; onap-discuss@lists.onap.org Subject: RE: [onap-discuss] Staging repo in settings.xml Hi Gary, Andy, As for the OpenECOMP history, the whole original idea was also to align everyone's release number and date to a common one for the launch (the current release-1.0.0 branch

Re: [onap-discuss] Staging repo in settings.xml

mb...@linuxfoundation.org] Sent: Thursday, May 11, 2017 1:17 PM To: Gary Wu <gary.i...@huawei.com>; onap-discuss@lists.onap.org Subject: Re: [onap-discuss] Staging repo in settings.xml On 05/10/2017 02:05 PM, Gary Wu wrote: > What's the rationale behind including Staging in the glob

[onap-discuss] Staging repo in settings.xml

Hi Andy, What's the rationale behind including Staging in the global settings.xml? This seems unorthodox. I have now observed instances (e.g. sdnc/core, mso) where a clean build in a local environment will fail unless Staging is included in local settings.xml. This is because there are