Not a Jenkins issue. Try passing `-U` argument to Maven to force repository check.
On 23.07.2014, at 17:40, Juan Ignacio Garzón <[email protected]> wrote: > Hi, > > I'm having this problem. I use an Artifactory server to store my maven > libraries. I configured the maven installation inside the jenkins server to > use that artifactory server as central repository. > > Sometimes an app being built uses a library that does not exist in the > Artifactory server and also does not exists on the central maven repository > (the artifactory server connects to the maven central repo). So, the build > inside Jenkins fails, and I have to manually deploy that library on > artifactory and execute the build inside Jenkins again. The problem, is that > the Maven installation used by Jenkins creates a file called xxx.lastupdated > inside the local repository. So, jenkins does not try to download the library > from the artifactory server again. To solve this, I have to manually connect > to the jenkins server, delete the .lastupdated file and build again. Is there > a way to avoid connecting via console to my server, asi it requires some > special permissions on my company? (I mean: Plugins, maven configuration for > this case, or something). > > > Thanks a lot!!! > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
