Maven 2.x Eclipse Plugin

Configure eclipse to use same source/target version as configured in maven-compiler-plugin.

Details

  • Type: Bug Bug
  • Status: Open Open
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: None
  • Fix Version/s: None
  • Component/s: Core : Workspace settings
  • Labels:
    None
  • Number of attachments :
    0

Description

With a configuration like this:

<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<configuration>
<source>1.3</source>
<target>1.3</target>

The following should be written to ".settings/org.eclipse.jdt.core.prefs":

org.eclipse.jdt.core.compiler.codegen.targetPlatform=1.3
org.eclipse.jdt.core.compiler.source=1.3
org.eclipse.jdt.core.compiler.compliance=1.3

We are working with a multi-module project where certain modules have a non-default source/target version because they are applets and need to be compatible with JSE 1.3. Without the above; these projects cause a mass of warnings in our eclipse workspace which shouldn't be there.

Issue Links

is duplicated by

Bug - A problem which impairs or prevents the functions of the product. MECLIPSE-506 Property of parent project not resolved

  • Major - Major loss of function.
  • Open - The issue is open and ready for the assignee to start work on it.

Activity

Hide
Permalink
Jerome Lacoste added a comment -

Note I tested this on a project with maven 2.2.1 and the problem disappeared. So I guess the problem is related to maven not properly interpolating the values.

Can someone test also with maven 2.2.1 ?

See MECLIPSE-506

Show
Jerome Lacoste added a comment - Note I tested this on a project with maven 2.2.1 and the problem disappeared. So I guess the problem is related to maven not properly interpolating the values. Can someone test also with maven 2.2.1 ? See MECLIPSE-506

People

  • Assignee:
    Unassigned
    Reporter:
    Maarten Billemont
Vote (1)
Watch (3)

Dates

  • Created:
    Updated: