https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/INTDIST-51 integration-distribution <p>Suppose that a test needs the "testtool" testing tool to do its work. How it can automatically determine where it is located in the Nexus?</p> <p>For Lithium releases it is needed to pull from "org/opendaylight/netconf/netconf-testtool/1.0.0-SNAPSHOT" (I am not sure about this one to be exact). For Beryllium releases it is also needed to pull from "org/opendaylight/netconf/netconf-testtool/1.0.0-SNAPSHOT" But for Boron releases is is needed to pull from "org/opendaylight/netconf/netconf-testtool/1.1.0-SNAPSHOT".</p> <p>The particularly troublesome part of the path to the test tool is the "1.0.0-SNAPSHOT"/"1.1.0-SNAPSHOT". There is no automatic way to figure this one out. Currently the test tools deployment code needs to harbor a large dictionary </p> <p>It is not particularly safe to use e.g. Boron test tools to test Lithium. For example now this won't work because Lithium/Beryllium require Java 7 while Boron test tools require Java 8.</p> <p>Operating System: All<br/> Platform: All</p> INTDIST-51

No way to automatically find test tools belonging to a particular ODL release

Bug Resolved Done Unassigned Jozef Behran Wed, 3 Feb 2016 09:53:37 +0000 Fri, 20 Oct 2017 10:32:31 +0000 Sat, 19 Nov 2016 00:52:32 +0000 unspecified Scripts 0 2 <p>This seem to work for Beryllium, both snapshots and autorelease, since Change 34149 was merged.<br/> Setting to FIXED.<br/> Official release and Boron snapshots are not tested thoroughly, reopen when necessary.</p> Development External issue ID 5206 External issue URL Rank 0|i01lm7: