Move adsal into its own subdirectory. Moved various adsal components into an opendaylight/adsal subdir, gave it a parent pom, and changed the root parent pom to have the opendaylight/adsal as a module. Change-Id: I1d0e5a7b2a50c65559c2f80dd47cab491b68d561 Signed-off-by: Ed Warnicke <eaw@cisco.com>
Incrementing versions by 0.1.0 for post-Helium master branch * The only version not incrmented is aaa.version, which is left at 0.1.0-SNAPSHOT since they depend on controller and can't update yet. * To break the cyclic dependency, this patch temporarily stops running the netconf-connector and restconf feature tests. * Also fixing a bug causing Errors like "Choice has two nodes case with same qnames". A second patch (to be run after AAA increments their versions to 0.2.0-SNAPSHOT) wiil update aaa.version and re-enable these tests. Change-Id: I70a3987d32504e798c5ed05a67a0a1174338844b Signed-off-by: Colin Dixon <colin@colindixon.com> Signed-off-by: Robert Varga <rovarga@cisco.com>
Add serialVersionUID to Serializable Serializable classes have to have serialVersionUID. Add it where it's missing. Change-Id: I23689005878280b6ee9f97fb12ae0b15151f20d7 Signed-off-by: Robert Varga <rovarga@cisco.com>
Unify maven-bundle-plugin version at 2.4.0 This removes superfluous version declarations, fixing about 70 eclipse warnings. At the same time it bumps the version 2.4.0, to unify it -- we were using both 2.3.7 and 2.4.0 at the same time. Change-Id: I0f3f6b68c5c05cb9cc226f75b4eb4dab7d58651d Signed-off-by: Robert Varga <rovarga@cisco.com>
Adding auto-sorting plugin to all Controller via parent/pom.xml leveraging google's sortpom plugin, all controller poms are sorted at build time as per the opendaylight/commons/parent/pom.xml configuration. Sorted lists of properties, dependencies, and plugins will increase pom readability and help prevent duplicate entry errors. This first submission is huge as I changed one pom.xml and all are then sorted. Only if the sortpom plugin is reconfigured will all pom's again be changed. Note that if any pom.xml is pushed without having been through a build ... folks are going to see pom.xml files showup as modified unintentionally. Change-Id: I8553f38b9f0e5f6d27177ad6b9b9c35a4b43d55a Signed-off-by: jameshall03885 <ghall@brocade.com>
Addding a new method to let the clients of clustering service specify a transaction timeout when they start a transaction Change-Id: Icad02808e37d7852907a417436c72cbcff8e62f1 Signed-off-by: Asad Ahmed <asaahmed@cisco.com>
Reworked pom files Each pom (artifact) declares it's dependencies (internal and external) No dependencies declared at parent POM level, only dependency Management. Also moved the <modules> from distribution/opendaylight to the root pom.xml distribution/opendaylight now builds entirely from dependencies I have intentionally left some things in here I think are wrong, because the goal of this commit is to reproduce the existing build (which it does, I've checked). Subsequent commits will clean up other things. Change-Id: I358bdac1c0f6a59b37a418a811a30235967fdfdc Signed-off-by: Tony Tkacik <ttkacik@cisco.com>
Introduce ASYNC caches and use them in FRM - Add the option in clustering.services contract to allocate caches that are async - Use them for FRM workOrder and workStatus - Add unit tests for sync/async incompatibility Change-Id: Icfc8d9b8a9277d97b095805cb4323a950c82ef78 Signed-off-by: Giovanni Meo <gmeo@cisco.com>
Removing the Container Aware dependency from Clustering Services. Clustering Services implementation is ContainerAware to handle the case of Container deletion. More appropriate way to handle it is to have an explicit API in global cluster manager to expose a functionality to clean all the caches assocaited with a Container. This API can be used by the Container Manager to clean up the caches. Change-Id: I9758a01da13ffa7d951307a116df34a7fe9c19f6 Signed-off-by: Madhu Venugopal <vmadhu@cisco.com>
Remove public from interface methods. Cleans sonar warnings. Change-Id: I5a64f93cb452522c50f788fd24bd10340f61a4e5 Signed-off-by: Alissa Bonas <abonas@redhat.com>
Remove java.lang redundant imports. Taken from sonar. Change-Id: I5606e49f27c15539728a00cda7cde6fe48cb45a0 Signed-off-by: Alissa Bonas <abonas@redhat.com>
Prepare for mvn release:prepare release:perform operation - Make sure every bundle include a proper scm section - Provided a pom to be used for release operations in the root directory, this is due to some implicit assumptions maven-release-manager does when performing a release. The maven-release-manager in fact calculate a tag name starting from the developerConnection and removing from the URL layers based on how deep the release pom is versus the assumed root. This is hardcoded in: http://svn.apache.org/viewvc/maven/release/tags/maven-release-2.3.2/maven-release-manager/src/main/java/org/apache/maven/shared/release/util/ReleaseUtil.java?view=markup Line 182 (this logic is not really specific to 2.3.2 version, but pretty much in every version). The tag calculation is fine if applied to SCM live SVN but not to GIT hence this limitation of having to place the root pom in the root itself. - Removed uneeded distributions like sdk and parent, because are combined in the main distribution. - Corrected some wrong dependencies in clustering - Added parent poms to distribution so to simplify the deploy of the artifacts. - Disable signing of openflowJ during release, it hangs - Forcing maven-release-plugin to version 2.3.2, latest today (2.4.1) has some issues. - Updated README.OPENDAYLIGHT with process for releasing artifacts - pom file in the root directory is merely a pointer to the main distribution, this doesn't change any of the current workflow and enable release support - Create a profile triggered when the -DDOBUILDRELEASE is set which exclude modules that are still depending on snapshots not under controller project Signed-off-by: Giovanni Meo <gmeo@cisco.com> Change-Id: I7d18fd7a5efd5809d3fc77d4e0ddc302296d9d98