Re: Maven and Continous Integration / Continous Delivery

here is what needs to be done: - while building the packages, use the mvn option -DnewVersion and replace the new version in POM.xml. this will happen through Jenkins server (for example CI server ) . for this, you need to make all POMs writable. - once the packages are built with new

Re: generate maven dependency difference between two Jenkins builds

are allowed to be changed. > Domi > > On 04.11.2014, at 08:10, Irfan Sayed wrote: > > > thanks. > > what i figured out is , nexus / artifactory will not download the > > dependency unless there is change in the version. > > if dependency x refers version 1.1 ,

Re: generate maven dependency difference between two Jenkins builds

ains 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 Su

Re: explicit dependencies in maven

thanks :) On Tue, Nov 4, 2014 at 10:57 AM, Anders Hammar wrote: > Yes, that's how it works. > > /Anders (mobile) > Den 4 nov 2014 06:06 skrev "Irfan Sayed" : > > > so, lets say if i am using x dependency with version 1.1 and if the > > developer change

Re: explicit dependencies in maven

you build with version 2.3.15 > of ourNiceUtility, you will always get the same code. The repo will simply > not allow them to overwrite version 2.3.15 once it is deployed into the > wild(public). > > Beats firing developers but stops them from doing silly things. > > > >

explicit dependencies in maven

hello, is there any good doc/blog which describes the handling of explicit declaration of dependencies. when we build the code, we use certain dependencies , how we can make sure that when we reproduce the same build after the gap of 6 months , same and exact dependencies will be used. ??? i know

Re: generate maven dependency difference between two Jenkins builds

ast all expressions and profiles locked down. > > Gruss > Bernd > > Am Sun, 19 Oct 2014 22:17:45 +0530 > schrieb Irfan Sayed : > > > thanks bernd. > > anyone has any other suggestions please? > > > > regards > > > > > > On Sun, Oct 19, 2014

Re: generate maven dependency difference between two Jenkins builds

gt; 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 : > > > hello, > >

generate maven dependency difference between two Jenkins builds

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

Re: failsafe plugin error with suiteXml

please suggest .. i am really stuck regards On Tue, Oct 7, 2014 at 10:51 PM, Irfan Sayed wrote: > hi, > > i am using maven failsafe plugin to run the integration tests > however, i am getting following error when i am executing integration > tests along with cobertura >

failsafe plugin error with suiteXml

hi, i am using maven failsafe plugin to run the integration tests however, i am getting following error when i am executing integration tests along with cobertura execute goal mvn-failsafe-plugin: (failsafe-integration-tests) project x: suiteXmlFiles is configured, but there is no TestNG dependen

maven compiler plugin

hi, i am using maven compiler plugin. i havent mentioned anything related to plugin in POM.xml i have just used the command on command prompt mvn compiler:compile what is happening is , above command compiles the test classes also . however which should not be the case in my opinion, only main j