[GRADLE-1937] EclipseProject.getName sometimes returns names that are not legal project names Created: 17/Nov/11  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: Bug
Reporter: Kris De Volder Assignee: Unassigned
Resolution: Won't Fix Votes: 2


 Description   

An example is returning a name containing a '/'.

See here for a sample project that demonstrates the problem:
https://issuetracker.springsource.com/browse/STS-1841

The HiearchicalEclipseProject model built for this project will contain a sub-project whose name 'greeteds/world'. But this is not a legal name for an Eclipse project.

Note: the sample project is corrupt but can be 'fixed' by replacing its build.gradle file with an empty file. (Still demonstrated the problem).

 Comments   
Comment by Szczepan Faber [ 20/Nov/11 ]

Ok, definitely a bug. It is exposed if one of the projects contains '/', for example when the user specifies such name in the settings.gradle.

I checked, and the idea plugin also has some issue in such case. It copes and imports ok but the iml is placed in an awkward place.

Comment by Kris De Volder [ 07/May/12 ]

Just had another user hit this bug in STS.
https://issuetracker.springsource.com/browse/STS-2614

Though I have a workaround coded into STS, the workaround doesn't actually work if users are choosing to use the Gradle eclipse plugin to generate .project files. Because in that case the workaround in code that uses the tooling API gets bypassed by the generated content in .project file itself.

Comment by Szczepan Faber [ 07/May/12 ]

We will fix it on our end at some point. In meantime, another workaround is to configure the project names in the build.gradle, for example:

allprojects {
  plugins.withType(EclipsePlugin) {
    eclipse.project.name = eclipse.project.name.replaceAll("/", "-")  
  }
}

It's also fairly easy to configure the project names to avoid '/' in the settings.gradle.

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:08:23 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.