There should be… we use the enunciate plugin to do it, and there's no reason other projects couldn't as well. Pulling it all together in one place could be interesting. That said, we do

Hi Ed or any other integration member with some understanding on the development infrastructure: I saw that for controller project, every time they do a new build they generate a bunch of very

Hi Luis, there is no user of our code in ODL, to my knowledge. For BGP we can use http://www.nongnu.org/quagga/ (but note, that it doesn't implement BGP linkstate -

Check this at the Github. https://github.com/OPENNETWORKINGLAB/ONLabTest It is python based. I am trying to setup the environment. Regards, Swaraj From: carol.sanders@... To: swarajv@...;

Hi BGP/PCEP people, I am reading you project wiki and I have a question: do you know of any service or plugin that makes use of your libraries in this ODL first release? I am just trying to figure

Hi all, Please check MoM of yesterday meeting: https://wiki.opendaylight.org/view/CrossProject:Integration_Group:Meetings BR/Luis

Hi all, I have been reading about the components and NB APIs available for Basic Edition and I updated our wiki with basic information:

Hi Ed, The issue on VTN Project has been fixed by the following patch. https://git.opendaylight.org/gerrit/#/c/1592/ So could you delete the line to comment out vtn from

Hi Ed, The problem has been fixed by the patch pushed by Shigeru. https://git.opendaylight.org/gerrit/#/c/1592/ Now, all files of VTN Project needed for building Virtulization Edition

I just tried the verify job and it failed, maybe this is expected and thats why it is not triggered during the commit. On Oct 1, 2013, at 11:17 PM, "Luis Gomez" <luis.gomez@...> wrote:

Hi Ed, I have already approved your commit. Just one curiosity, how is it that the code got merged without running jenkins verify and merge jobs? Are not these set yet? On Oct 1, 2013, at 9:22 PM, "Ed

The initial commit of the distributions directories is here: https://git.opendaylight.org/gerrit/#/c/1593/ If another committer from integration could review it and submit it so it can be merged into

Hi Ed, Sorry for the inconvenience. We will look into vtn-verify job and vtn-merge job to support Release Vehicles, and also review the use of check style config. Thanks, Hideyuki Tai

And here is the meeting series till the end of the year. BR/Luis

Hi all, Please do not forget the weekly call tomorrow. https://wiki.opendaylight.org/view/CrossProject:Integration_Group:Meetings BR/Luis

Resending to affinity-dev as the original was bounced because I wasn't subscribed. Ed On Oct 1, 2013, at 4:41 PM, Ed Warnicke (eaw) <eaw@...> wrote:

Resending to defense4-all as original was bounced because I wasn't subscribed. Ed On Oct 1, 2013, at 3:57 PM, Ed Warnicke (eaw) <eaw@...> wrote:

Guys, It would appear that version 0.4.1-SNAPSHOT of your affinity artifacts are not appearing in Nexus:

Guys, Right now there are no artifacts for groupid org.opendaylight.defense4all innexus.opendaylight.org, which means I can't include them in the Release Vehicle (what we will actually be releasing)

I realized when trying to build your manager/commons that it suffers from an issue around the use of <configLocation> ${project.parent.basedir}/checkstyle.xml