I understand that you have a few (120) repos but once you have made the list, it is easy to maintain. Same as the list of active projects. 1000 is a lot of names to list but you probably can find one already existing or make one through a partially automated process.

Otherwise it is a clerical task that you can give to a junior tech.
DEPARTMENT_POM ->TEAM_POM -> PROJECT_POM -> MODULE_POM
is more interesting but probably not that hard to manage.

DEPARTMENT_POM ->TEAM_POM is a small list.
You want to eliminate duplicate sub-trees.

Just a suggestion for a non-maven solution. That is one of the advantages of using XML in the POM, You are not restricted to using the application for which the files are designed. There are lots of XML tools - both low level and high level that can be applied.

Ron


On 20/06/2014 11:55 AM, Mirko Friedenhagen wrote:
Ron,

* finding all POMs is not that simple in our case as we have at least
20 SVN repositories with multiple projects and about 100 git
repositories.
* POMs are XML but a lot of projects have at least DEPARTMENT_POM ->
TEAM_POM -> PROJECT_POM -> MODULE_POM relations, so we have to lookup
stuff in Artifactory anyway.
* I think I will implement a goal `display-ancestors` in the
versions-maven-plugin :-).

Regards
Mirko


Regards Mirko
--
http://illegalstateexception.blogspot.com/
https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen)
https://bitbucket.org/mfriedenhagen/


On Fri, Jun 20, 2014 at 4:22 PM, Ron Wheeler
<rwhee...@artifact-software.com> wrote:
Good description of the use case that helps.
You are not very explicit about how you identify the projects to be checked
or where (SCM, staging folder) you want to find them.

Just a thought:
Couldn't this be accomplished with a batch job that used XSLT or a simple
Java program with an XML parser to check POMs for outdated references?
POMs are just XML with a pretty simple structure.
They always have the same name so finding them in the project is not hard.
You are always looking down the same XPATH(s?) for the version and you know
which one is right.

Is there some magic that Maven includes that is needed here?

Ron


On 20/06/2014 8:09 AM, Mirko Friedenhagen wrote:
Hello,

does anybody know of a plugin which shows the GAV coordinates of the
parents of a given project recursively? Or is there any feasible
plugin where I could contribute with a goal?

My team of 3 is consulting approx. 200 developers in regards of build
engineering with ca. 1000 Jenkins jobs and we often see they are using
outdated versions of our department POM. Having this information in
the console of a Jenkins job would allow to see this without checking
the POM.

Regards Mirko
--
http://illegalstateexception.blogspot.com/
https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen)
https://bitbucket.org/mfriedenhagen/

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



--
Ron Wheeler
President
Artifact Software Inc
email: rwhee...@artifact-software.com
skype: ronaldmwheeler
phone: 866-970-2435, ext 102



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org




--
Ron Wheeler
President
Artifact Software Inc
email: rwhee...@artifact-software.com
skype: ronaldmwheeler
phone: 866-970-2435, ext 102


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Reply via email to