Re: [mdsal-dev] [release] SM projects check
I think some help regarding mdsal in Neon can be found here:
Od: Luis Gomez <ecelgp@...>
Odoslané: streda, 30. januára 2019 22:33:21
Kópia: tsc; transportpce-dev@...; mdsal-dev@...; release@...
Predmet: Re: [mdsal-dev] [release] SM projects check
> On Jan 30, 2019, at 6:28 AM, <guillaume.lambert@...> <guillaume.lambert@...> wrote:
> Luis, thank you for the reminder.
> I suspect either mdsal-model-artifacts or ietf-yang-types-20130715 is not ready yet, or perhaps will no more supported in neon.
> Can someone confirm that point , please?
I am not sure it is documented anywhere but I think you have to declare something like this:
> Luis, as you can see in the URL below, transportpce is actually building with latest neon dependencies since last month.
> However, we got run time issues with karaf so I have not merged this change yet (as we needed to work and test various new functionalities).
> I just updated that change with the dependencies given in your URL https://docs.opendaylight.org/projects/integration-distribution/en/latest/platform-versions.html
> It still builds but there are still karaf run-rime issues , but different this time.
> The list in your URL does not provide a version for mdsal-model-artifacts ( and ietf-yang-types-20130715), so I retrieved it from nexus: 0.13.2-SNAPSHOT
> The last configuration pushed triggers a new run-time error in karaf (missing requirement … [org.opendaylight.mdsal.model.ietf-yang-types-20130715/2013.7.15.13_2-SNAPSHOT] )
> There is more or less the same problem with 0.13.1-SNAPSHOT or 0.13.1.
> I noticed that mdsal binding-parent versions used to be aligned with that artifact and that it is no more the case.
> Best regards
> From: release-bounces@... [mailto:release-bounces@...] On Behalf Of Luis Gomez
> Sent: lundi 28 janvier 2019 00:53
> To: Release
> Cc: tsc
> Subject: [release] SM projects check
> Hello everybody,
> This is to remind Self Managed projects that want to be part of the Neon common distribution, to please check the release process in .
> As a summary:
> 1) Your project should be building latest Neon SNAPSHOT and platform release versions .
> 2) Your project should be in the common distribution, so far I can see 3 projects: sxp, telemetry and jsonrpc 
> 3) You should prepare for cutting the Neon stable branch and bumping the master version. It is recommended to do this at the same time as Managed projects, this is at Code Freeze on Feb 7th. You are invited to open a ticket to ODL helpdesk if you need assistance with this task.
>  https://docs.opendaylight.org/en/latest/release-process/managed-release.html#self-managed-projects
>  https://docs.opendaylight.org/projects/integration-distribution/en/latest/platform-versions.html
>  https://git.opendaylight.org/gerrit/gitweb?p=integration/distribution.git;a=blob;f=opendaylight/pom.xml;h=b84fe986d1a7ec35ccd39e08d616483aec65fe28;hb=refs/heads/master
> Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
> Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
> This message and its attachments may contain confidential or privileged information that may be protected by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and delete this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
> Thank you.
mdsal-dev mailing list