[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

.svn dirs copied to output during build (with solution)

From: Matt Doran <matt.doran_at_papercut.biz>
Date: 2005-04-19 10:36:22 CEST

Hi there,

I've noticed a something annoying with our SVN managed project in
Eclipse 3.0.1 (with Subclipse 0.9.30). When Eclipse to does a rebuild,
it not only compiles the java classes, but it copies other resources to
the output directories (in our case "target\classes"). I guess this is
handy for things like *.properties files, but it also copies across the
".svn" dirs. Not only does this slow the build process considerably,
it also confuses TortoiseSVN into thinking the output dirs are a working
copy.

Is this something others have experienced this? Or is this something
peculiar with my workspace? (I've also seen the same thing on
colleagues machines).

I couldn't find any answers on this or the dev mailing lists, or the
issue tracker. After a bit of searching around I found the solution,
and thought I'd share it here.

There is a setting deep in the Eclipse prefs to filter resources that
should be copied on build. Adding ".svn/" to the list, fixes the
problem....
    * Open Window->Preferences
    * Select Java->Compiler, and select the "Build Path" tab
    * Add ".svn/" to "Filtered resources" list (comma separated).

Subclipse devs.... is it possible for Subclipse stop this occurring
without changing this setting? Or maybe modifying it on install? Or
maybe just document this option somewhere in a FAQ?

Cheers,

-- 
Matt Doran
PaperCut Software Pty. Ltd.
E-mail:  matt.doran@papercut.biz
Web: 	 http://www.papercut.biz
Blog:    http://blogs.papercutsoftware.com/matt.doran/
Received on Tue Apr 19 18:36:22 2005

This is an archived mail posted to the Subclipse Users mailing list.