[ http://jira.codehaus.org/browse/MECLIPSE-77?page=all ]
Lukas Theussl moved MPECLIPSE-112 to MECLIPSE-77:
-------------------------------------------------
Workflow: Maven (was: jira)
Key: MECLIPSE-77 (was: MPECLIPSE-112)
Project: Maven 2.x Eclipse Plugin (was: maven-eclipse-plugin)
> Resource targetPath is relative to the project's output directory.
> ------------------------------------------------------------------
>
> Key: MECLIPSE-77
> URL: http://jira.codehaus.org/browse/MECLIPSE-77
> Project: Maven 2.x Eclipse Plugin
> Type: Bug
> Reporter: Emanuel Bulic
>
>
> I am using the following resource:
> <build>
> <resources>
> <resource>
> <targetPath>data/core/beanconfig</targetPath>
> <directory>.</directory>
> <excludes>
> <exclude>*target/**</exclude>
> </excludes>
> </resource>
> </resources>
> </build>
> Also, the eclipse plugin is configured to use a different outputDirectory:
> <plugin>
> <artifactId>maven-eclipse-plugin</artifactId>
> <configuration>
> <outputDirectory>eclipse-target</outputDirectory>
> </configuration>
> </plugin>
> The classpath entry for the resource above should be relative to the
> project's output path:
> <classpathentry kind="src" path="."
> output="eclipse-target/data/core/beanconfig"/>
> The pluging generates the wrong entry:
> <classpathentry kind="src" path="." output="data/core/beanconfig"/>
> The output classpath entry is correct:
> <classpathentry kind="output" path="eclipse-target"/>
--
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
