Remove developer specific files

shannah / Java-Objective-C-Bridge

A thin bridge that allows for two-way communication from Java to Objective-C.

123 stars 25 forks source link

Remove developer specific files #39

Open Marcono1234 opened 3 years ago

Marcono1234 commented 3 years ago

This project contains a few developer-specific files, or files which might not be needed anymore. It is generally recommended to not check these fils in with version control (here Git) because each developer might have different settings. Instead respective files and folders should be excluded using .gitignore or locally by the developer using --skip-worktree.

Affected:

Eclipse settings:
- /.settings
- /.classpath
- /.project
/libjcocoa.xcodeproj, or at least some of its sub-directories (?)
/src/main/resources/ (?) And even if they are needed to build the project, I doubt that they should end up in the final .jar

mojo2012 commented 3 years ago

Some files like .project should imho be included because they allow new developers to use those projects in their favourite IDE (Eclipse ;-)) as long as they don't container developers-(machine) specific settings.

Marcono1234 commented 3 years ago

Though modern IDEs should (and likely are) able to import a plain Maven project without requiring any IDE specific settings (might be different for Native development using Xcode though). For example the Eclipse .project file dictates that the project has the name "Java-Objective-C-Bridge". If the user wants a different name then they might have issues with Eclipse and they will have to fight Git marking the file as modified (or be aware of --skip-worktree). Same .classpath and .settings, there does not appear to be anything special which a developer needs. Eclipse will very likely be able to generate these files with correct content on its own.