Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Newcomers » Newcomers » Building case-sensitive Eclipse for Mac(Building case-sensitive Eclipse for Mac)
Building case-sensitive Eclipse for Mac [message #1052866] Tue, 30 April 2013 19:28
Frank Rimlinger is currently offline Frank Rimlinger
Messages: 3
Registered: July 2009
Junior Member
I want to use Eclipse to support android PLATFORM development on a Mac. This is different from using the android plugin to build android apps, which I already know how to do.

For this to work, it is necessary for Eclipse to honor case sensitivity on the mac (yes, the mac supports case sensitive file systems). It all boils down to changing the following line of code in org.eclipse.core.internal.resources.Workspaace

public static final boolean caseSensitive = Platform.OS_MACOSX.equals(Platform.getOS()) ? false : new java.io.File("a").compareTo(new java.io.File("A")) != 0;

For example, the following would probably work:

public static final boolean caseSensitive = new java.io.File("a").compareTo(new java.io.File("A")) != 0;

Requesting this change is non-starter, because there is too much history. So I want to build my own Eclipse. Now the fun begins. I follow the instructions at the Platform_Build eclipse site.

I succeed in building my home-brew eclipse platform. Hooray, but now the problem is getting maven to honor my code change. To do this, I read all about git, especially the part about submodules. I understand that my particular file is in a submodule, so I go to that submodule, add and commit the change to the master branch. Then I go to the top of the workspace, and do

hercules:r frank$ git submodule update
Submodule path 'eclipse.platform.resources': checked out '0621f2a34ffbbf33d9df4955717872b510e3bbda'

This seems like good news, because the altered submodule has been singled out for attention, and appears to get a new checksum, so time to build:

hercules:r frank$ mvn clean verify
[INFO] Scanning for projects...

Two and half hours later, a fresh Eclipse comes out of the oven, BUT NO JOY. I still see the original line of code when I launch Eclipse and load the org.eclipse.core.resources plugin. I am assuming the Tycho build scripts would have imported and bound the new source file to the binary as a matter of course.

I understand there is a complex git/Maven/Tycho thing going on here, but where to start? The subject is vast. If someone could just point me in the right direction, I would be most grateful. In terms of understanding am I cold, warm, or hot?
Previous Topic:Rank newbie question
Next Topic:Eclipse Freezing on Windows 7/64 bit
Goto Forum:
  


Current Time: Wed Sep 17 17:36:48 GMT 2014

Powered by FUDForum. Page generated in 0.01696 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software