[GRADLE-284] New task to update classpaths in IDE configurations Created: 28/Oct/08  Updated: 04/Jan/13  Resolved: 12/Jul/11

Status: Resolved
Project: Gradle
Affects Version/s: None
Fix Version/s: None

Type: New Feature
Reporter: Martin Vlcek Assignee: Szczepan Faber
Resolution: Won't Fix Votes: 1

Attachments: File updateIdeClasspath.gradle    

 Description   

There should be a task that just updates the classpaths of IDE configuration files, as there might be other settings that should not be overwritten.
It should update all known configuration files that it finds in the current directory.

An example for Eclipse (.classpath) and IntelliJ (*.iml) is attached, however, the following should be addressed:

  • the relevant configurations should be set from a convention object (default is testRuntime)
  • the generated paths should be user independent (all jars are in ~/.gradle/...) for possible check in into subversion, etc.: for IntelliJ (probably just under Linux) using ~/.gradlet/... works, for Eclipse we should probable use a variable (USER_HOME? GRADLE_CACHE_HOME?)

 Comments   
Comment by Martin Vlcek [ 28/Oct/08 ]

Correction: ~/.gradle does not work with IntelliJ either.

Comment by Szczepan Faber [ 09/May/11 ]

>There should be a task that just updates the classpaths of IDE configuration files

Don't the 'eclipseClasspath' and 'ideaModule' tasks provide just that?

Comment by Szczepan Faber [ 12/Jul/11 ]

There're already specific tasks that only change classpath-related information. Also, the tasks that generate classpath info attempt to merge the content so some user info is preserved.

Therefore I don't think we want to fix this particular feature

Generated at Wed Jun 30 11:26:15 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.