-
Notifications
You must be signed in to change notification settings - Fork 108
Remap Jars to Gradle Projects ignores version #94
Comments
This is actually 'as designed'. As it was suggested to me that that made most sense by one user. It actually used to take the version into account as well but that was changed. I suppose we really should make this a configurable preference as obviously not everyone agrees on whether or not the version should be taken into account. On the other hand, if you didn't want to work with a particular project dependency in your workspace... can't you simply close that project? (Or if you do want it as a dependency, then you should probably make sure to check out the right branch / version of that project). |
I prefer a configurable solution. |
Not really, I only followed the feedback from a user who leads a team of If I have to try and explain it to you... I'd say... maybe the reasoning is On Tue, Aug 4, 2015 at 8:59 AM, Martin Burchard notifications@github.com
|
I slept on it and now I disagree. ;) Defining a dependency this way If a team like to switch of usage of a specific version, or always likes to use the latest, it can be achieved by Without a specific Eclipse Flag you can have everything you need and in addition it will also behave the same way if you use Gradle outside Eclipse... What about that? |
I am probably not going to be supporting this kind of version matching in the IDE. I'd have to re-implement gradle's patterns for matching version and implement the resolution algorithm to essentially resolved agains workspace projects. Moreover, I'd have to implement that without even having a complete model of the project (because tooling API just doesn't expose very detailed information to the IDE). So... if your script uses 'fuzzy' versions like these then the best you are going to get is the IDE ignoring version on the project instead of matching it to a complex expression matching a range of versions. Conclusion, maybe we are best to leave it as is. |
I had to deactivate the Remap Jars to Gradle Projects because it ignores the version of the project.
Main project has to branches. The v1.7 brunch depends on other project v0.5 and the v1.8 brunch depends on other project v0.6. In v0.6 a constructor has changed and when I switch to brunch v1.7 it complains about a Java failure.
Without "Remap Jars" it uses the right dependencies from local repositories and ignores the open projects in Eclipse.
The text was updated successfully, but these errors were encountered: