You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@buildr.apache.org by "Nathan Hamblen (JIRA)" <ji...@apache.org> on 2008/08/04 23:26:45 UTC

[jira] Commented: (BUILDR-117) Shared directory for both code and resources produces duplicate Eclipse classpath entries

    [ https://issues.apache.org/jira/browse/BUILDR-117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12619711#action_12619711 ] 

Nathan Hamblen commented on BUILDR-117:
---------------------------------------

Yeah that test is failing because the user defined path 'src/java' does not exist. If you add

write 'src/java/Other.java'

to the before it will pass. But what is the correct behavior? Should only resources be checked for existence? Should nothing be checked for existence? 'src/main/resource' doesn't get added in the first place unless it exists, but that may have been different when this eclipse exporter was first written.

> Shared directory for both code and resources produces duplicate Eclipse classpath entries
> -----------------------------------------------------------------------------------------
>
>                 Key: BUILDR-117
>                 URL: https://issues.apache.org/jira/browse/BUILDR-117
>             Project: Buildr
>          Issue Type: Bug
>          Components: IDE
>    Affects Versions: 1.3.2, 1.3.3
>            Reporter: Nathan Hamblen
>            Assignee: Alex Boisvert
>             Fix For: 1.3.3
>
>         Attachments: 0001-Combine-sources-resources-and-generated-to-check-f.patch
>
>
> I usually use
> resources.from('src/main/java').exclude('**/*.java')
> to include resources from the java compilation directory, but this causes the eclipse task to produce a two identical entries for that directory and Eclipse gets all confused until you delete the duplicate. I've got a patch, just a sec!

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.