Removing source and target tags from pom.xml doesn't remove project specific
compiler settings in eclipse
---------------------------------------------------------------------------------------------------------
Key: MECLIPSE-149
URL: http://jira.codehaus.org/browse/MECLIPSE-149
Project: Maven 2.x Eclipse Plugin
Issue Type: Bug
Environment: SuSE Linux 10.1
Sun JDK 1.5.0_07
Eclipse 3.1
Maven 2.0.4
Reporter: Markus KARG
I added the following to the pom.xml, then execute mvn eclipse:eclipse:
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<configuration>
<source>1.5</source>
<target>1.5</target>
</configuration>
</plugin>
</plugins>
</build>
Then pressing F5 in Eclipse makes the project's compiler settings beeing
changed from "workspace defaults" to "project specific", reflecting the value
of 1.5. Fine. :-)
Now changing the pom.xml from 1.5 to 1.4, doing mvn eclipse:eclipse and F5 once
more, makes the 1.4 beeing reflected in Eclipse's compiler settings dialog.
Fine. :-)
Now completely removing the <build> section from pom.xml, doing mvn
eclipse:eclipse and F5 a third time. But Eclipse still keeps the project
specific settings! This is bad, it certainly has to remove the project specific
settings since there are none to be found in the pom.xml!
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
