CODEWITHSUNDEEP
eclipsemaven
Dirt McCrasse
Dirt McCrasse

Reputation: 42

Why are Eclipse project files modified when excuting the "Update Maven Project" command?

I installed Eclipse 2019-06 on a new workstation and imported our team's maven project. When running the "Update Maven Project" command, for all subprojects, some of the project files are edited, whereas they are not on my current workstation (with one exception). My station runs Eclipse Oxygen 4.7.0.

Is there a way to determine why these modifications occur on this station and not on others?

Is there a way to turn off these modifications so that our projects are unified?

The modifications are the following :


       <classpathentry kind="src" output="target/test-classes" path="src/test/java">
              <attributes>
                     <attribute name="optional" value="true"/>
                     <attribute name="maven.pomderived" value="true"/>
                     <attribute name="test" value="true"/>***
              </attributes>
       </classpathentry>
       <classpathentry excluding="**" kind="src" output="target/test->classes" path="src/test/resources">
              <attributes>
                     <attribute name="maven.pomderived" value="true"/>
                     <attribute name="test" value="true"/>***
              </attributes>
       </classpathentry>



              <buildCommand>
                     <name>org.fusesource.ide.project.RiderProjectBuilder</name>
                     <arguments>
                     </arguments>
              </buildCommand>
       </buildSpec>
       <natures>
              <nature>org.fusesource.ide.project.RiderProjectNature</nature>
              <nature>org.eclipse.jdt.core.javanature</nature>
              <nature>org.eclipse.m2e.core.maven2Nature</nature>
       </natures>
</projectDescription>



    org.eclipse.jdt.core.compiler.problem.enablePreviewFeatures=disabled
    org.eclipse.jdt.core.compiler.problem.forbiddenReference=warning
    org.eclipse.jdt.core.compiler.problem.reportPreviewFeatures=ignore
    org.eclipse.jdt.core.compiler.release=disabled

The exception I mentionned earlier concerns the line "org.eclipse.jdt.core.compiler.problem.forbiddenReference=warning" which is also added on my workstation. It seems to be replicating an exception I configured for one subproject to all other subprojects, and it is also annoying.

Upvotes: 1

Views: 881

Answers (1)

LMC
LMC

Reputation: 12672

Eclipse 2019-06 (4.12) releases notes on Workspace compatibility

Downward workspace compatibility is not supported. A workspace created (or opened) by a product based on Eclipse 4.12 will be unusable with a product based on an earlier version of Eclipse.

While individual projects could still be usable across different versions the paragraph above states that backward compatibility is not supported, meaning issues like the one you describe are expected to happen.

To turn off any unwanted modification as much as possible it's suggested to exclude IDE specific project files from git repositories.
Another option could be to normalize the IDE version across teams, i.e. make all team members use the same version.

Upvotes: 2

Related Questions