It could be a case since I am not in control of who has control to write to
the POM file.
On Wednesday, August 7, 2013 4:24:21 PM UTC-4, Geoff Cummings wrote:
>
>
> Could something have modified the Pom file in the jenkins workspace?
>
> I dont think Svn update will overwrite a modified file..
Could something have modified the Pom file in the jenkins workspace?
I dont think Svn update will overwrite a modified file..
Just a guess..
Geoff
On 7 Aug 2013, at 21:03, DAVID HO wrote:
Daniel,
Yeah, I checked the POM in workspace and realized that it was the old
version. There is nothing
Daniel,
Yeah, I checked the POM in workspace and realized that it was the old
version. There is nothing interesting about this problem in the log, except
that the build was fail because of the change in dependencies in the POM.
On Wednesday, August 7, 2013 3:52:54 PM UTC-4, Daniel Beck wrote:
>
Anything interesting in the build logs when this occurred?
How do you know the file wasn't updated, did you view the file in the workspace?
On 07.08.2013, at 21:50, DAVID HO wrote:
> Hi all,
>
> I am very new to Jenkins and also to the build process. I have just started
> using Jenkins at my
Hi all,
I am very new to Jenkins and also to the build process. I have just started
using Jenkins at my workplace. For our build process, we have the source
code store in a remote SVN server and use Maven for the build. For the
build configuration, we had *Checkout Strategy* as "Use SVN update
