[ 
http://jira.codehaus.org/browse/MECLIPSE-444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=207061#action_207061
 ] 

Arnaud Heritier commented on MECLIPSE-444:
------------------------------------------

No, I'm not working on it. I wanted and finally didn't have the time.
The problem is that the eclipse plugin should have to generate an absolute path
path="/Users/ieb/Caret/sakai22/devcode/shindig-trunk
It should generate the relative one from basedir

> Included Resources break the classpath file and prevent eclipse from building
> -----------------------------------------------------------------------------
>
>                 Key: MECLIPSE-444
>                 URL: http://jira.codehaus.org/browse/MECLIPSE-444
>             Project: Maven 2.x Eclipse Plugin
>          Issue Type: Bug
>          Components: Core : Dependencies resolution and build path 
> (.classpath)
>    Affects Versions: 2.5.1
>            Reporter: Ian Boston
>             Fix For: 2.8
>
>
> In Apache Shingig we have more than one language using a set of resources 
> (PHP and Java), so the resources are stored on disk in a relative path.
> In the jars we have 
> <build>
>   <resources>
>       <resource>
>         <targetPath>features</targetPath>
>         <directory>${basedir}/../../features</directory>
>       </resource>
>       <resource>
>         <directory>${basedir}/../../javascript/</directory>
>         <targetPath>/gadgets/files</targetPath>
>         <includes>
>           <include>**/*.*</include>
>         </includes>
>       </resource>
> etc
> which results in a .classpath 
> shroud:~/Caret/sakai22/devcode/shindig-trunk ieb$ more java/server/.classpath 
> <classpath>
>   <classpathentry kind="src" 
> path="/Users/ieb/Caret/sakai22/devcode/shindig-trunk/config" 
> output="target/classes/containers/default" including="container.js" 
> excluding="**/*.java"/>
>   <classpathentry kind="src" 
> path="/Users/ieb/Caret/sakai22/devcode/shindig-trunk/features" 
> output="target/classes/features" excluding="**/*.java"/>
>   <classpathentry kind="src" 
> path="/Users/ieb/Caret/sakai22/devcode/shindig-trunk/javascript" 
> output="target/classes/gadgets/files" including="**/*.*" 
> excluding="**/*.java"/>
>   <classpathentry kind="output" path="target/classes"/>
>   <classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER"/>
>   <classpathentry kind="var" 
> path="M2_REPO/org/apache/abdera/abdera-core/0.4.0-incubating-SNAPSHOT/abdera-core-0.4.0-incubating-SNAPSHOT.jar"/>
>   <classpathentry kind="var" 
> path="M2_REPO/org/apache/abdera/abdera-i18n/0.4.0-incubating-SNAPSHOT/abdera-i18n-0.4.0-incubating-SNAPSHOT.jar"/>
> The first 3 entries are invalid as they are outside the project space the 
> eclipse project.
> Since this breaks the eclipse build, I am classifying this as a bug.... you 
> might want to reclassify.
> The work around is simple, but it generating questions on the list and 
> resulting in people not wanting to use the eclipse plugin.

-- 
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

        

Reply via email to