I got a maven project (myApp) depending on another maven project in snapshot version.
like:

```
<dependency>
    <groupId>org.group.dep</groupId>
    <artifactId>arty</artifactId>
    <version>12.1.4-SNAPSHOT</version>
</dependency>

```

But I got a problem with this after the "arty" got an update without changing the version (I know that would be the cleanest solution).
I build the myApp local and got still the old version of the "arty" dependency. 

I verified tow option working for me (and a college):  

1) Manual cleaning of the local repository: navigating to my `.m2/repo/org/group/dep/arty` and deleted all folders inside. After rebuilding the myApp local it was working fine - arty was downloaded form the artifactory.company.com again with the updated content. 

2) Local building of the arty package so it got updated in the local repository. After rebuilding the myApp local it was working fine.

But I got similar problem on the Jenkins:  

I got a Jenkins job just building `org.group.myApp` without building before `org.group.dep.arty`. It failed for the missing changes form "arty". 

What can I do now to solve my problem there?  

I can not rely on first building `org.group.dep.arty` as I can not be sure for Jenkins to run both jobs on the same host using same local repository (I don't want to change that).
Somehow the myApp-Jobs was failing after I manually cleared on that Jenkins node the `org.group.dep.arty` in the repository and running than the myApp-job (was somehow not downloading the package).

I finally found the `mvn -u` but as I tried this I was as well disappointed. 
I tried different maven versions on that jenkins and got the same result.
Is there no way to force the update of the snapshot versions?