[GRADLE-1702] Mapping of source folders and linked resources should try to avoid absolute paths (use path variables) Created: 28/Jul/11  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: 1.0-milestone-4
Fix Version/s: None

Type: Improvement
Reporter: Kris De Volder Assignee: Unassigned
Resolution: Won't Fix Votes: 0


Currently, if a project has source folders like "../shared-src". This results in a linked resource characterized by an absolute path.

This ends up inside the users .project file which can be quite annoying if that file is commited to a CVS/GIT/SVN/... repo.

Some better solution using path variables needs to be devised to avoid relative paths in users build files to result
in absolute paths in the .project file.

Comment by Kris De Volder [ 28/Jul/11 ]

Of course, it may be possible for me to do something on my end (i.e. in Eclipse).

I can imagine automagically turning the returned absolute paths into relative paths.

Anyway, it may be useful to think about this and discuss with you guys before I
implement something.

Comment by Szczepan Faber [ 30/Jul/11 ]

This feature request makes perfect sense to me.

Comment by Benjamin Muschko [ 15/Nov/16 ]

As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub.

We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to.

Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:

  • Checking that your issues contain requisite context, impact, behaviors, and examples as described in our published guidelines.
  • Leave a comment on the JIRA issue or open a new GitHub issue confirming that the above is complete.

We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!

Comment by Benjamin Muschko [ 10/Feb/17 ]

Thanks again for reporting this issue. We haven't heard back from you after our inquiry from November 15th. We are closing this issue now. Please create an issue on GitHub if you still feel passionate about getting it resolved.

Generated at Wed Jun 30 12:02:12 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.