> > Thats weird, AFAIK ODL settings.xml is always required. > He still has settings.xml, he is stating he is using the one downloaded from stable/oxygen, if I understand correctly. The fact is, settings.xml hardly ever changes, even between releases [0]. It hasn't changed in over a year in fact.
The trick is to use stable release (never expires) instead of stable > branch, you can download a given release by using a tag, for example: > If you are trying to contribute a delta back upstream to the open source code base instead of maintaining a "permanent" fork, then you will want to build and submit against master. The stability of master has improved over the years :). Regards, Ryan Goulding [0] https://github.com/opendaylight/odlparent/commits/master/settings.xml On Tue, Jun 19, 2018 at 5:40 PM, Luis Gomez <ece...@gmail.com> wrote: > > > On Jun 19, 2018, at 2:26 PM, harry.zh...@us.fujitsu.com wrote: > > Hi Ecelgp, > > Thank you very much! It compiles now. > > May I ask whether settings.xml is common to all of the releases? After > switched to stable/oxygen, it compiles even without changing the > settings.xml file. > > > Thats weird, AFAIK ODL settings.xml is always required. > > > If I put some of my work under this stable/oxygen branch, someday later > the branch is no longer supported as what happened to stable/boron, may I > ask what the best strategy is for me to deal with the situation, in case I > am not ready to merge my code to a new release? > > > The trick is to use stable release (never expires) instead of stable > branch, you can download a given release by using a tag, for example: > > git fetch --all --tags —prune > git checkout tags/release/oxygen-sr2 > > > If I need to save my environment to share with a development team, may I > ask which files and directories that I should save to a local storage so > that our development efforts would not be effected by Opendaylight release > supporting plan? > > > I am not sure I full follow the question but you could save the entire git > repo or just the changes you did. > > > > Best Regards, > > Harry > > > > *From:* Luis Gomez [mailto:ece...@gmail.com <ece...@gmail.com>] > *Sent:* Tuesday, June 19, 2018 3:49 PM > *To:* Zhang, Harry <harry.zh...@us.fujitsu.com> > *Cc:* controller-dev@lists.opendaylight.org > *Subject:* Re: [controller-dev] Which Release is the Most Recent in > Stable State That Compiles > > Hi Harry, stable/oxygen is the latest stable release. > > > On Jun 19, 2018, at 1:46 PM, harry.zh...@us.fujitsu.com wrote: > > Hi Everybody, > > I am trying to find a recent stable branch to compile the controller and > Netconf projects. I did, > > git clone https://git.opendaylight.org/gerrit/p/controller.git > cd controller/ > git checkout stable/boron > > I saved the file https://github.com/opendaylight/odlparent/blob/ > stable/boron/settings.xml > <https://github.com/opendaylight/odlparent/blob/stable/boron/settings.xml%20to%20my%20.m2> > to > my local ~/.m2/ > > When compiled, I got errors as following. Mr. Tom Pantelis > <https://jira.opendaylight.org/secure/ViewProfile.jspa?name=tpantelis> said > “The Boron release is no longer maintained or supported. As such, the > failed dependencies likely no longer exist on ODL nexus”. > > May I ask which stable release that is still supported I should use to > continue my tests? > > > Regards, > > Harry > > > > ERROR] The build could not read 1 project -> [Help 1] > [ERROR] > [ERROR] The project org.opendaylight.controller:releasepom:0.4.5-SNAPSHOT > (/home/hzhang/controller/pom.xml) has 1 error > [ERROR] Non-resolvable parent POM for > org.opendaylight.controller:releasepom:0.4.5-SNAPSHOT: > Failure to find org.opendaylight.odlparent:odlparent-lite:pom:1.7.5-SNAPSHOT > in https://nexus.opendaylight.org/content/repositories/ > opendaylight.snapshot/ was cached in the local repository, > > > > > The Boron release is no longer maintained or supported. As such, the > failed dependencies likely no longer exist on ODL nexus. > > _______________________________________________ > controller-dev mailing list > controller-dev@lists.opendaylight.org > https://lists.opendaylight.org/mailman/listinfo/controller-dev > > > > _______________________________________________ > controller-dev mailing list > controller-dev@lists.opendaylight.org > https://lists.opendaylight.org/mailman/listinfo/controller-dev > >
_______________________________________________ controller-dev mailing list controller-dev@lists.opendaylight.org https://lists.opendaylight.org/mailman/listinfo/controller-dev
