Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [m2e-users] maven import changes the project
the source preferences set in JDT match the values inferred from your pom.xml. By default the maven compiler plugin settings set it to 1.5 [1]. 

If you want to use 1.8, make sure your compiler plugin uses the proper settings:

 <plugin>
   <artifactId>maven-compiler-plugin</artifactId>
   <version>3.5.1</version>
   <configuration>
     <source>1.8</source>
     <target>1.8</target>
   </configuration>
 </plugin>

As for the classpathentry exportedness (if you're talking about the Maven Classpath container), it should be preserved if you're using m2e 1.7 [2]


On Thu, Jul 21, 2016 at 10:39 AM, Michal Zan <michal.zan@xxxxxxx> wrote:

Hello,

I have searched the internet for this question, but with no luck. The problem is, that when I import projects to eclipse with “Existing Maven Projects” wizard, some projects get changed. For example in some projects org.eclipse.jdt.core.compiler.codegen.tergetPlatform, org.eclipse.jdt.core.compiler.complience and org.eclipse.jdt.core.compiler.source preferences in jdt prefs file gets changed from 1.8 to 1.5. Next problem is it messes with the .classpah file. The classpathentry with kind=”lib” and exported=”true” are all removed. Why is the plugin making changes that are not somehow transparent for the user? Thank you for help.

 

Regards,

Michal


_______________________________________________
m2e-users mailing list
m2e-users@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/m2e-users



--
"Have you tried turning it off and on again" - The IT Crowd
And if that fails, then http://goo.gl/tnBgH5

Back to the top