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>
Remove version mismatch in config.version - End goal was to remove several config.version present in the pom, in the making i cleaned some of the repetition in config parent pom and aligned with the commons.opendaylight - Removed some more warning on the pom files Change-Id: I6717ceb915fe90fa7313472eb03884de9d09235d Signed-off-by: Giovanni Meo <gmeo@cisco.com>
update the pom files to enable the nexus repository path to be configured by properties such that if can be overriden via the command line to support deployment to alternative locations Change-Id: Ie96244a1a2a3f6b2f3760f366899017a44aa381d Signed-off-by: David K. Bainbridge <dbainbri@ciena.com>
Checksum errors seen on some setup while downloading guava - Due to some issues with the mirroring of {repo1|repo2}.maven.org of some artifact, forcing all the repo1/repo2 artifacts to be downloaded directly and not via ODP nexus proxy. This has been adviced also by sonatype support folks, now they have a content delivery network in place and can handle the load. Change-Id: Iff7e604d35f0a4a877e1316990be2bf6bf1ea1f6 Signed-off-by: Giovanni Meo <gmeo@cisco.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
- Removed sitebuildsettings, the deployment of this and manteinance in opendaylight infra is troublesome and also the settings are isolated that can be manually tweaked in the parent POM: - opendaylight/commons/opendaylight/pom.xl - third-party/commons/thirdparty - Adjusted the deployment of third-party snapshots to happen in opendaylight-snapshot nexus repo, given there is only deployment access to that on jenkins and also because there is not reason to distinguish it, anyway the groupID already avoid collision. Signed-off-by: Giovanni Meo <gmeo@cisco.com> Change-Id: Ieb20f107895dc9b186b1799de5cb84dc11c5ec7c