You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Vivek Pandey (JIRA)" <ji...@codehaus.org> on 2007/11/22 06:59:57 UTC

[jira] Commented: (MECLIPSE-114) eclipse:eclipse creates overlapping source directories

    [ http://jira.codehaus.org/browse/MECLIPSE-114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_114528 ] 

Vivek Pandey commented on MECLIPSE-114:
---------------------------------------

Surprising that the issue is written off like this !!
support for nested sources is an eclipse feature, not a limitation. When sources are nested, eclipse needs exclusion filters to take care of them. Should the maven-eclipse-plugin not take care of this and generate the exclusion filters ?

> eclipse:eclipse creates overlapping source directories
> ------------------------------------------------------
>
>                 Key: MECLIPSE-114
>                 URL: http://jira.codehaus.org/browse/MECLIPSE-114
>             Project: Maven 2.x Eclipse Plugin
>          Issue Type: Bug
>    Affects Versions: 2.2
>            Reporter: Matthew Beermann
>
> If I have a POM that looks like this:
> <build>
>     <sourceDirectory>src</sourceDirectory>
>     <resources>
>         <resource>
>             <directory>.</directory>
>             <includes>
>                 <include>foo.xml</include>
>             <indlude>
>         </resource>
>     <resources>
> </build>
> ...then I'll get a .classpath file that looks like this:
> <classpathitem kind="src" path="src"/>
> <classpathitem kind="src" path="."/>
> This is illegal, as far as Eclipse is concerned - build paths cannot be nested inside of one another.

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