Force m2eclipse to check remote repository for latest artifact version when library is defined to use the latest version

[akerekes]

If m2eclipse is set to not check for latest version automatically in remote repositories (Window/Preferences/Maven/Do not automatically update dependencies from remote repositories), then if the user has an older version of any of the libraries we're adding to the classpath via the API Attacher, it will use that jar, and download the latest for those that are not present locally. This can lead to having App Engine API 1.9.40 and App Engine Endpoints 1.9.44 on the classpath (assuming that App Engine API 1.9.40 was present in the local repo, no App Engine Endpoints jar was available locally and the latest version is 1.9.44)

[chanseokoh]

Also, when we later download servlet-api.jar, we need to specifically pin a certain version.

[akerekes]

You can specify an explicit version for a library already.

On Fri, Oct 14, 2016 at 3:23 PM Chanseok Oh notifications@github.com
wrote:

Also, when we later download servlet-api.jar, we need to specifically pin
a certain version.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#830 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADOO_u3QB1HIVQHqTpR4M2shgQJvpxb2ks5qz9aogaJpZM4KXWc0
.

[chanseokoh]

Right. The title of this issue suggests to force using latest artifact versions, so I was making a note that servlet-api.jar is an exception. It should be 2.5 for App Engine standard.

[akerekes]

Title updated. Also for clarification: this issue has nothing to do with artifacts that are configured with a specific version, only with those that use 'LATEST' as version.

[akerekes]

I have dug into this issue, but I could not find a good way to override the preferences setting for a given request. I don't think we should change the user's preference just to make this work, so I'm not sure how we could achieve this (apart from deleting all local artifacts for the given Maven coordinates to ensure that the lookup will hit the remote repo, but this also seems excessive).

[branflake2267]

Could a m2e configurator pick up the version on a maven update and then reconfigure the API used? I do some configuring on m2e updates. Although I've noticed once I add a lifecycle, I have to run that lifecycle in eclipse m2e.

[briandealwis]

I suspect the best we can do is log the situation.