eclipse update of maven project fails for sonar-cxx-plugin #851
Comments
|
@jmecosta maybe you can fix it? |
|
i dont know, but seems to work with netbeans and maven command line. perhaps some eclipse bug? seems a standard maven feature and we dont have issues with it. is there more people having same issue with other ides? |
|
I'm using NetBeans and Maven: it's working with both. |
|
I modified the pom.xml and this version works fine. Please check. <?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
<modelVersion>4.0.0</modelVersion>
<parent>
<groupId>org.codehaus.sonar-plugins.cxx</groupId>
<artifactId>cxx</artifactId>
<version>1.0-SNAPSHOT</version>
</parent>
<artifactId>sonar-cxx-plugin</artifactId>
<packaging>sonar-plugin</packaging>
<name>Cxx :: Sonar Plugin</name>
<inceptionYear>2010</inceptionYear>
<description>Enable analysis and reporting on c++ projects.</description>
<url>https://github.com/SonarOpenCommunity/sonar-cxx/wiki</url>
<properties>
<sonar.artifact.path>target/${project.artifactId}-${project.version}.jar</sonar.artifact.path>
</properties>
<dependencies>
<dependency>
<groupId>org.codehaus.sonar</groupId>
<artifactId>sonar-plugin-api</artifactId>
<scope>provided</scope>
</dependency>
<dependency>
<groupId>org.codehaus.sonar</groupId>
<artifactId>sonar-deprecated</artifactId>
<scope>provided</scope>
</dependency>
<dependency>
<groupId>org.codehaus.sonar.dotnet.tests</groupId>
<artifactId>sonar-dotnet-tests-library</artifactId>
</dependency>
<dependency>
<groupId>${project.groupId}</groupId>
<artifactId>cxx-squid</artifactId>
<version>${project.version}</version>
</dependency>
<dependency>
<groupId>${project.groupId}</groupId>
<artifactId>cxx-checks</artifactId>
<version>${project.version}</version>
</dependency>
<dependency>
<groupId>org.sonarsource.sslr</groupId>
<artifactId>sslr-testing-harness</artifactId>
<scope>test</scope>
</dependency>
<dependency>
<groupId>org.apache.maven</groupId>
<artifactId>maven-project</artifactId>
<version>2.0.9</version>
<scope>test</scope>
</dependency>
<dependency>
<groupId>org.codehaus.sonar</groupId>
<artifactId>sonar-testing-harness</artifactId>
<scope>test</scope>
</dependency>
<dependency>
<groupId>org.apache.ant</groupId>
<artifactId>ant</artifactId>
</dependency>
<dependency>
<groupId>jdom</groupId>
<artifactId>jdom</artifactId>
</dependency>
<dependency>
<groupId>org.codehaus.sonar.common-rules</groupId>
<artifactId>sonar-common-rules</artifactId>
</dependency>
<dependency>
<groupId>org.mockito</groupId>
<artifactId>mockito-all</artifactId>
<scope>test</scope>
</dependency>
<dependency>
<groupId>ch.qos.logback</groupId>
<artifactId>logback-classic</artifactId>
<scope>test</scope>
</dependency>
<dependency>
<groupId>${project.groupId}</groupId>
<artifactId>cxx-lint</artifactId>
<version>${project.version}</version>
</dependency>
</dependencies>
<build>
<resources>
<resource>
<directory>src/main/resources</directory>
<excludes>
<exclude>com/sonar/sqale/cxx-model-project*</exclude>
<exclude>external/*</exclude>
</excludes>
</resource>
<!--
<resource>
<targetPath>static</targetPath>
<directory>../cxx-lint/target</directory>
<includes>
<include>cxx-lint-${project.version}.jar</include>
</includes>
</resource>
-->
</resources>
</build>
</project> |
|
@Bertk i will create a pr to and test in netbeans, dont see any reason not to merge this change |
|
@Bertk are you sure the pom you posted is correct? as far as i see there are no differences to current master.
|
|
@jmecosta : OK let us close this issue. I cannot find the strange path in the pom.xml. <resource>
<targetPath>static</targetPath>
<directory>../cxx-lint/target</directory>
<includes>
<include>cxx-lint-${project.version}.jar</include>
</includes>
</resource> |
|
But that's the pom for the cxx-plugin perhaps you need to share that one |
|
@jmecosta Thanks for the hint. I updated the comment with the pom.xml details and now it should be clear 😎 |
|
fixed by #863 |
Eclipse fails to update the project definition from pom.xml
The pom.xml shows a resource using a location outside of the project folder which causes the issue. After removing the resource from the pom.xml the update works again.
The text was updated successfully, but these errors were encountered: