Process, whenever the user tries to add an eclipse by hand using the It then drops lombok.jar in the same directory asĮclipse.ini and makes the edit. Right now, the installer accomplishes these goals by looking for theĮclipse executable, knowing that it can go from there to eclipse.iniĮasily: It's either right there in the same dir, or it's inĮclipse.app/MacOS/Resources relative to the directory that theĮxecutable is in. Might be hidden somewhere in the insides of the eclipse install. It needs to hide these details from the end user, who probablyĭoesn't even know there's such a thing as eclipse.ini, and that it It needs to put lombok.jar in a suitable place.ģ. It needs to find eclipse.ini, and edit references to lombok.jarĢ. Usr/bin, and /usr/lib) is totally different from how the downloadableĮclipse package (from ) works, which bundles all files intoġ.
Given app across a bunch of directories, such as in this case, across / The much bigger concern is how the LSB view (of splitting files for a Well, at the very least we can have a quick look in /usr/lib/eclipseĪnd see if there's an eclipse.ini there, and use it.
0 kommentar(er)
