With regards to Jenkins, it's not exactly what you're asking about, but if you have your project set up as a Maven build and configure builds trigger downstream builds, it will tell you the difference between the last upstream build version and the current one, ex you'll get something like
"No changes. Changes in dependency upstream_project Success#1208 → Success#1209 (detail) " in your view of the build. Which made it really easy for us to track what changes got picked up in a build. Re: snapshot versions, we got annoyed as well that it was very difficult to tell what snapshot version a build used just looking at maven output, so we wrote a small plugin to a least log it for debugging. General idea / code here: http://blog.liveramp.com/2014/09/29/identifying-maven-snapshot-artifacts-by-git-revision/ to plug my own blog post. Ben On Sun, Oct 19, 2014 at 10:20 AM, Irfan Sayed <irfu.sa...@gmail.com> wrote: > thanks bernd. > can you please explain in detail . i am sorry but haven't got much > if u can give me steps then that wud be great > > regards > > > On Sun, Oct 19, 2014 at 10:41 PM, Bernd Eckenfels <e...@zusammenkunft.net> > wrote: > > > Ah another thing, I always wished there is an option to archive the > > effective POM instead of the tear downed POM with the > > maven-archiver (addMavenDesciptor). > > > > Especially when the effective pom also contains the resolved snapshot > > timestamps (which it currently not does). > > > > Speaking of effective pom, you can create and archive it, then you have > > at least all expressions and profiles locked down. > > > > Gruss > > Bernd > > > > Am Sun, 19 Oct 2014 22:17:45 +0530 > > schrieb Irfan Sayed <irfu.sa...@gmail.com>: > > > > > thanks bernd. > > > anyone has any other suggestions please? > > > > > > regards > > > > > > > > > On Sun, Oct 19, 2014 at 9:49 PM, Bernd Eckenfels > > > <e...@zusammenkunft.net> wrote: > > > > > > > Hello, > > > > > > > > I dont have a good method for that (especially not if all > > > > dependencies arent fully version-specified. You can use and add > > > > dependencies:list as a target to the maven build, then the resolved > > > > list will be printed in the build log. This list can change > > > > depending on what is available at build time. > > > > > > > > Gruss > > > > Bernd > > > > > > > > Am Sun, 19 Oct 2014 20:57:29 +0530 > > > > schrieb Irfan Sayed <irfu.sa...@gmail.com>: > > > > > > > > > hello, > > > > > > > > > > we have java project and using maven to build the same. we are > > > > > using Jenkins. in Jenkins , we can generate the delta of source > > > > > code changes between two builds. > > > > > in the same way, do we have any way wherein , we can generate the > > > > > delta of maven dependencies changed between two builds. > > > > > > > > > > please suggest > > > > > > > > > > regards > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > 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 > > > > >
