Bug 367758

Description Björn Thelberg 2012-01-03 08:02:32 EST

Build Identifier: 20110916-0149

If there is a new snapshot version of one of my projects dependencies available in Nexus I can update the local repository (and Eclipse) by doing a "Maven->Update Dependencies..." and check "Force Update of Snapshots/Releases".
The pom and jar files are updated nicely but the sources jar is not updated until I right click the specific jar under "Maven Dependencies" and perform a "Maven->Download Sources".
Until that, the sources for that artifact in my local repsitory are from the first snapshot version I downloaded. I have the option "Download Artifact Sources" checked in the Maven preferences.

I am using m2e 1.0.100.20110804-1717 and have updated the Embedded Maven Runtime Bundle to version 1.0.1.201106291304.

Reproducible: Always

Steps to Reproduce:
1. Deploy a new snapshot version to the repository manager, for example add a method to an existing class.
2. In a project that depends on that snapshot do a "Maven->Update Dependencies..." and check "Force Update of Snapshots/Releases".
3. Try to call the new method from another class and verify that the jar is updated and it compiles. Sometimes a refresh on the project is needed to make Eclipse use the new version.
4. Open the class file with the new method in Eclipse (for example using "Navigate->Open Type...") and now observe that the change is not in the source code.
5. Look in the local repository folder and observe the old date on the sources jar. The pom and the jar are up to date.
6. Now right click the specific jar under "Maven Dependencies" and perform a "Maven->Download Sources" and hopefully the source is also updated. Sometimes the repository is updated but not the source in Eclipse. Here as well, a refresh on the project does the magic.