Hi Geoffrey,

in relation of the format issue, that tab/space was the problem.
In eclipse the default is to use tab for indentation, but this behavior can be changed. After change that I could provide a good commit.

But that change don't alter the issue with egit (all files seems to be changed)

regards,

Cristiano


On 22/03/13 12:12, Geoffrey De Smet wrote:
Weird. Haven't seen this reported before.

Can you a do a "hd pom.xml" comparison on 2 versions of the file to show what's different on every line?
Maybe it's not the line ending, but tabs instead of spaces for example.

Op 22-03-13 14:37, Cristiano Gavião schreef:
Hi Geoffrey,

well, as I use macos the default is the unix end-of-line characters and always when I create a new workspace, the first thing that I do is to change the encode to UTF-8

Worth to say that that problem is happening only in jbpmdroos repositories... I have more than hundred projects that I work here... :(

On 22/03/13 10:09, Geoffrey De Smet wrote:
Here's the relevant eclipse section:

 *

    Set the correct file encoding (UTF-8 except for properties
    files) and end-of-line characters (unix):

      o Open menu /Window/, menu item /Preferences/.
     o

        Click tree item /General/, tree item /Workspace/

          + Label /Text file encoding/, radiobutton /Other/,
            combobox |UTF-8|.
          + Label /New text file delimiter/, radiobutton /Other/,
            combobox |Unix|.
     o

        Click tree item /XML/, tree item /XML Files/.

          + Combobox /Encoding/: |ISO 10646/Unicode(UTF-8)|.
     o

        Click tree item /CSS/, tree item /CSS Files/.

          + Combobox /Encoding/: |ISO 10646/Unicode(UTF-8)|.
     o

        Open tree item /HTML/, tree item /HTML Files/.

          + Combobox /Encoding/: |ISO 10646/Unicode(UTF-8)|.
     o

        Note: normal i18n properties files must be in |ISO-8859-1|
        as specified by the java |ResourceBundle| contract.

          + Note on note: GWT i18n properties files override that
            and must be in |UTF-8| as specified by the GWT contract.


Op 22-03-13 14:05, Geoffrey De Smet schreef:
Check if your IDE settings are compatible with our defaults.
Eclipse:
https://github.com/droolsjbpm/droolsjbpm-build-bootstrap/blob/master/README.md#developing-with-eclipse
IntelliJ:
https://github.com/droolsjbpm/droolsjbpm-build-bootstrap/blob/master/README.md#developing-with-intellij

Basically, line endings should be "\n" (except for .bat files).
99% of the files are "\n" line endings.
Recently, a few new files in the drools repo snook in with a different line ending, but those files need have a dos2unix.

Op 22-03-13 13:11, Cristiano Gavião schreef:
Hello,

I would like to discuss a problem that I'm facing with the git repositories from droolsjbpm when using it with eclipse Jgit/Egit.

The problem is that after import the projects into eclipse IDE and 'shared them with git', all files seems to be modified.
I could find the same type of problem here:
http://stackoverflow.com/questions/8227233/the-is-nothing-changed-but-eclipse-egit-keep-to-marked-the-file-as-changed

The worst is if I do a "format" in the code file, seems as the entire file have changed. :(

As I use MacOS I've setup my system *core.autocrlf* with 'input' as stated here: https://help.github.com/articles/dealing-with-line-endings

I've been using egit for a long time and I only face this kind of problem with droolsjbpm repos.

What kind of SO and IDE do you guys use at RedHat ?

Any of you had this kind of problem? any tip how to deal with ?

thanks and regards,

Cristiano


_______________________________________________
rules-dev mailing list
rules-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-dev



_______________________________________________
rules-dev mailing list
rules-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-dev



_______________________________________________
rules-dev mailing list
rules-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-dev



_______________________________________________
rules-dev mailing list
rules-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-dev



_______________________________________________
rules-dev mailing list
rules-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-dev

_______________________________________________
rules-dev mailing list
rules-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-dev

Reply via email to