[GRADLE-1080] Eclipse .project merging creates significant whitespace diffs Created: 29/Jul/10 Updated: 04/Jan/13 Resolved: 16/Jan/11 |
|
Status: | Resolved |
Project: | Gradle |
Affects Version/s: | 0.9.1 |
Fix Version/s: | 0.9.2 |
Type: | Improvement | ||
Reporter: | Chris Beams | Assignee: | Peter Niederwieser |
Resolution: | Fixed | Votes: | 0 |
Description |
Repro steps:
|
Comments |
Comment by Chris Beams [ 29/Jul/10 ] |
premature save on issue creation. step #7 above should read: 7. notice that the spring nature is preserved, but formatting is not <projectDescription> <name> helloworld </name> <comment/> <projects/> <natures> <nature> org.springframework.ide.eclipse.core.springnature </nature> <nature> org.eclipse.jdt.core.javanature </nature> </natures> <buildSpec> <buildCommand> <name> org.eclipse.jdt.core.javabuilder </name> <arguments/> </buildCommand> <buildCommand> <name> org.springframework.ide.eclipse.core.springbuilder </name> <arguments/> </buildCommand> </buildSpec> <links/> </projectDescription> 8. assume the user checks in once again Ideally, Gradle's .project (and .classpath) generation facilities should generate and preserve standard eclipse formatting. |
Comment by Hans Dockter [ 29/Jul/10 ] |
I agree. We should observe standard eclipse formatting. It would be hard to maintain any existing custom formatting when doing the merge. |
Comment by Chris Beams [ 16/Jan/11 ] |
Great news that this is resolved. Thanks, Peter. |