incubator-jena-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andy Seaborne (JIRA)" <>
Subject [jira] [Commented] (JENA-87) SVN directories are included in Eclipse .classpath
Date Sat, 06 Aug 2011 11:09:27 GMT


Andy Seaborne commented on JENA-87:

This only happens if the project is not team-svn-shared.  I guess you have checked out project
with command line svn tools and then added the project to Eclipse.  If you check it out in
Eclipse, it all just works (tm).

Adding the classpathentry seems like a good idea if it does not break team-shared projects.

m2eclipse has been a long-running source of problems as it interacts with other Eclipse plugins.
 Currently, the aim is to have as few dependences as possible so interactions of Eclipse plugs
does not cause problems.

maven-eclipse-plugin is OK - I use to generate the .classpath files in the first place.

Evolution as resulted in a less then idea module structure (including the lack of cross linking).
We do need a better build system.

Several of the projects checking their lib/ directory - historical setup. This is slowly being

> SVN directories are included in Eclipse .classpath
> --------------------------------------------------
>                 Key: JENA-87
>                 URL:
>             Project: Jena
>          Issue Type: Bug
>          Components: ARQ, Fuseki, Jena, TDB
>         Environment: Eclipse Helios in Windows 7
>            Reporter: Stephen Allen
>            Assignee: Andy Seaborne
>            Priority: Trivial
>         Attachments: JENA-87-r1154408.patch
> The .classpath files for ARQ, Jena, TDB, Fuseki (and probably the other Jena projects)
do not exclude the .svn directories from the build classpath.  This causes a lot of the following
warnings to be displayed:
>     "The resource is a duplicate of src/.svn/all-wcprops and was not copied to the output
> The fix is to replace this line [1] in the .classpath with [2] for each of the "src"
classpath entries.  This issue might be masked if you are using an Eclipse SVN plugin.
> [1] <classpathentry kind="src" path="src"/>
> [2] <classpathentry excluding="**/.svn/" kind="src" path="src"/>

This message is automatically generated by JIRA.
For more information on JIRA, see:


View raw message