Force to use the release plugin 2.5 from command line
Extra options for autorelease

- possibility to specify the list of repositories to build
- possibility to do only one run on one repo
- possibility to use a different git mirror repo
remove wrong placement of pluginManagement in the localreleasesettings.xml.tmpl
When deploying make sure to deploy everything (enabling the appropriate profiles)

Signed-off-by: Giovanni Meo <gmeo@cisco.com>
Enhance autorelease to be able to apply patches to the repo on the
baseforrelease branch

In order to accomodate patches that are being discovered to solve bugs
that are not yet on master lets allow a pre-patch file to be applied
to the branch if exists

Signed-off-by: Giovanni Meo <gmeo@cisco.com>
Fix netconf-it failure on controller.git

- Add a non-committed yet patch that allow netconf-it to reliably pass
the build

Signed-off-by: Giovanni Meo <gmeo@cisco.com>
Fixed --restart_from parameters

--restart_from would only work for the repo after the one specified,
which is a counter sense, so fixing it.

Signed-off-by: Giovanni Meo <gmeo@cisco.com>
Enhance to use repo fully qualified

- Allow to specify in the repositorylist fully qualified repos so to
allow also to include other sources

Signed-off-by: Giovanni Meo <gmeo@cisco.com>
[maven-release-plugin]  copy for tag versions-maven-plugin-2.1

git-svn-id: https://svn.codehaus.org/mojo/tags/versions-maven-plugin-2.1@18420 52ab4f32-60fc-0310-b215-8acea882cd1b
Change revision and prevent the conflict between IDE and maven command line
Fix the UseLatestVersionsMojo to be able to update the plugins
dependencies and the plugin artifacts as well

- Enhance the mojo to update also the versions specified as variable
ignoring the variable expansion
- Enhance the mojo to process the plugins and plugins dependencies
section
Introduce a new mojo instead to overload the use-latest-versions

use-latest-versions is documented to simply bump the dependencies, for
bumping the plugin and plugin dependencies and parent pom versions we
better have a different more inclusive Mojo

Signed-off-by: Giovanni Meo <gmeo@cisco.com>
Reverted some changes in PomHelper that where not supposed to be done because a proper API was provided

- Added in RewritePomToLatestVersionsMojo.java the capability to
rewrite the parent pom file.
- Make sure when replacing in the plugin the old version if compared
with a variable is unconditionally rewritten

Signed-off-by: Giovanni Meo <gmeo@cisco.com>
Null parent check

Signed-off-by: Giovanni Meo <gmeo@cisco.com>
Removed cached versions-maven-plugin so we can replace it with the one
built from code

Signed-off-by: Giovanni Meo <gmeo@cisco.com>
More exclusions after importing versions-plugin

Signed-off-by: Giovanni Meo <gmeo@cisco.com>
Instead of using a cached binary version of versions-plugin lets build
from source

- versions-maven-plugin needs modifications so keeping with the
autorelease tool makes a lot of sense

Signed-off-by: Giovanni Meo <gmeo@cisco.com>
Enhance the versions plugin to allow to filter on the repositories we
want to include in the search for latest releases

- Searching many repositories is expensive in terms of execution, also
in an automatic release we actually want to seal together the
artifacts and as such having control of what goes inside by resolving
the ODL artifacts against the artifacts we are cutting make sense.

Signed-off-by: Giovanni Meo <gmeo@cisco.com>
Use the -Dversions.repofilter in the autorelease script

Signed-off-by: Giovanni Meo <gmeo@cisco.com>
Add extra gitignore

Signed-off-by: Giovanni Meo <gmeo@cisco.com>