1. Integration-Dev
  2. Messages

Re: Please update vtn-verify and vtn-merge to support Release Vehicles

Ed Warnicke (eaw) <eaw@...>
 

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
</configLocation>

for check style, that causes a build error. We solved that in controller by pulling the check style config into its own
maven project (see opendaylight/commons/checkstyle, it's quite simple) and including it as a
dependency for the check style plugin (see opendaylight/commons/opendaylight :

<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-checkstyle-plugin</artifactId>
<version>${checkstyle.version}</version>
<dependencies>
<dependency>
<groupId>org.opendaylight.controller</groupId>
<artifactId>checkstyle</artifactId>
<version>0.0.2-SNAPSHOT</version>
</dependency>
</dependencies>
<executions>
<execution>
<phase>process-sources</phase>
<goals>
<goal>check</goal>
</goals>
</execution>
</executions>
<configuration>
<failsOnError>true</failsOnError>
<configLocation>controller/space_and_tabs_checks.xml</configLocation>
<consoleOutput>true</consoleOutput>
<includeTestSourceDirectory>true</includeTestSourceDirectory>
<sourceDirectory>${project.basedir}</sourceDirectory>
<includes>**\/*.java,**\/*.xml,**\/*.ini,**\/*.sh,**\/*.bat</includes>
<excludes>target\/</excludes>
</configuration>
</plugin>


).

Ed

On Oct 1, 2013, at 3:33 PM, Ed Warnicke (eaw) <eaw@...> wrote:

As part of putting together the release vehicles for ODL (Base, Virtualization, Service Provider) I am
constructing distribution directories for each flavor in the integration project.

When I attempt to pull in

<dependency>
<groupId>org.opendaylight.vtn</groupId>
<artifactId>manager</artifactId>
<version>0.1.0-SNAPSHOT</version>
</dependency>
<dependency>
<groupId>org.opendaylight.vtn</groupId>
<artifactId>manager.implementation</artifactId>
<version>0.1.0-SNAPSHOT</version>
</dependency>
<dependency>
<groupId>org.opendaylight.vtn</groupId>
<artifactId>manager.northbound</artifactId>
<version>0.1.0-SNAPSHOT</version>
</dependency>


To include the vtn pieces, I encounter an error:

[ERROR] Failed to execute goal on project distributions-virtualization: Could not resolve dependencies for project org.opendaylight.integration:distributions-virtualization:pom:0.1.0-SNAPSHOT: Failed to collect dependencies for [org.opendaylight.integration:distributions-base:zip:osgipackage:0.1.0-SNAPSHOT (provided), org.opendaylight.ovsdb:ovsdb:jar:0.4.0-SNAPSHOT (compile), org.opendaylight.vtn:manager:jar:0.1.0-SNAPSHOT (compile), org.opendaylight.vtn:manager.implementation:jar:0.1.0-SNAPSHOT (compile), org.opendaylight.vtn:manager.northbound:jar:0.1.0-SNAPSHOT (compile)]: Failed to read artifact descriptor for org.opendaylight.vtn:manager:jar:0.1.0-SNAPSHOT: Failure to find org.opendaylight.vtn:manager.common:pom:0.1.0-SNAPSHOT in http://nexus.opendaylight.org/content/repositories/jsonrpc4j-webdav-maven-repo/ was cached in the local repository, resolution will not be reattempted until the update interval of jsonrpc4j-webdav-maven-repo has elapsed or updates are forced -> [Help 1]


This error is occurring because the org.opendaylight.vtn:manager.common is not being built by your
merge job, and thus its artifact is not being pushed to Nexus. Since the other vtn manager artifacts depend on it,
I am unsuccessful in pulling them into the virtualization edition via maven/nexus. You can resolve this if you will insert
a Post Build Step into your vtn-verify and vtn-merge jobs that build

commons/
manager/commons/

So that their pom.xml files get deployed. Your prompt assistance with this would be very much appreciated,
as it is blocking getting the Release Vehicles going :)

Ed
Join integration-dev@lists.opendaylight.org to automatically receive all group messages.