You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@vxquery.apache.org by "André Hildebrandt (JIRA)" <ji...@apache.org> on 2010/04/19 13:35:50 UTC
[jira] Created: (VXQUERY-26) Source compliance level configuration
in pom does not match to source
Source compliance level configuration in pom does not match to source
---------------------------------------------------------------------
Key: VXQUERY-26
URL: https://issues.apache.org/jira/browse/VXQUERY-26
Project: VXQuery
Issue Type: Bug
Reporter: André Hildebrandt
Priority: Trivial
When importing the vxquery project into eclipse, there are compile errors after import as the source code used the @Override annotation for interface implementations. While using the annotation is a good choice, the source compliance should be set to 1.6 in this case. This is configured during project import when using m2eclipse based on the maven-compiler-plugin configuration. Thus it should look like this to obtain the correct source compliance config:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<version>2.0.2</version>
<configuration>
<source>1.6</source>
<target>1.6</target>
</configuration>
</plugin>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (VXQUERY-26) Source compliance level configuration
in pom does not match source
Posted by "Vinayak Borkar (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/VXQUERY-26?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vinayak Borkar resolved VXQUERY-26.
-----------------------------------
Assignee: Vinayak Borkar
Resolution: Fixed
Fixed in r935634.
> Source compliance level configuration in pom does not match source
> ------------------------------------------------------------------
>
> Key: VXQUERY-26
> URL: https://issues.apache.org/jira/browse/VXQUERY-26
> Project: VXQuery
> Issue Type: Bug
> Reporter: André Hildebrandt
> Assignee: Vinayak Borkar
> Priority: Trivial
>
> When importing the vxquery project into eclipse, there are compile errors after import as the source code used the @Override annotation for interface implementations. While using the annotation is a good choice, the source compliance should be set to 1.6 in this case. This is configured during project import when using m2eclipse based on the maven-compiler-plugin configuration. Thus it should look like this to obtain the correct source compliance config:
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-compiler-plugin</artifactId>
> <version>2.0.2</version>
> <configuration>
> <source>1.6</source>
> <target>1.6</target>
> </configuration>
> </plugin>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (VXQUERY-26) Source compliance level configuration
in pom does not match source
Posted by "André Hildebrandt (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/VXQUERY-26?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
André Hildebrandt updated VXQUERY-26:
-------------------------------------
Summary: Source compliance level configuration in pom does not match source (was: Source compliance level configuration in pom does not match to source)
> Source compliance level configuration in pom does not match source
> ------------------------------------------------------------------
>
> Key: VXQUERY-26
> URL: https://issues.apache.org/jira/browse/VXQUERY-26
> Project: VXQuery
> Issue Type: Bug
> Reporter: André Hildebrandt
> Priority: Trivial
>
> When importing the vxquery project into eclipse, there are compile errors after import as the source code used the @Override annotation for interface implementations. While using the annotation is a good choice, the source compliance should be set to 1.6 in this case. This is configured during project import when using m2eclipse based on the maven-compiler-plugin configuration. Thus it should look like this to obtain the correct source compliance config:
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-compiler-plugin</artifactId>
> <version>2.0.2</version>
> <configuration>
> <source>1.6</source>
> <target>1.6</target>
> </configuration>
> </plugin>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.