Ah, fun with Eclipse. :) I'm still an Eclipse newbie, obviously.
No, I have no desire at all to version control the "bin" directory.
What I was looking for was a way to store a version that could be
checked out by my team members that would work "as-is." Without the
bin directory, Eclipse complains and you have to create it yourself (or
my version does, anyway). I was trying to just version an "empty" bin
directory and then have Subversion just ignore the contents. Not a big
deal, so I'll just not put that under version control and deal with it.
Thanks!
Aside: I have been unsuccessful getting Subclipse to work on Mac OS X
(there are some fink based shared libraries that I still need to
install that the plug in is compiled against) but I haven't tried very
hard and I wanted to learn command-line svn first so I'd know what it
is fully capable of.
Ironically, it was Eclipse that led me to Subversion in the first
place. Since Eclipse makes it so darned easy to refactor Java code, I
was having a heck of a time with CVS and its inability to version
directories. I was having to manually fiddle with the CVS repository
to get the results I wanted and I was getting quite frustrated dealing
with it. Subversion is really helping in this regard so far!
Looks like I've got some more experimenting to do, though. Thanks for
the responses! I thought I was going a bit crazy there.
Thanks,
David Findley
On Apr 26, 2004, at 4:46 PM, Simon McClenahan wrote:
> By default, Eclipse will delete everything in your build directory
> before rebuilding a project. You can toggle this feature (in Eclipse
> 3.0M7) in Window, Preferences, Java, Compiler, Build Path, Clean
> output folders on full build checkbox.
>
> You may want to consider installing the Subclipse plugin for IDE
> integration with Subversion. I think Eclipse/Subclipse still has
> issues with the .svn directories existing, but save that discussion
> for the Subclipse list.
>
> Are you sure you want to version control the bin directory?
> Alternatively, you could specify a different build directory for
> Eclipse, and create an ant task or whatever that copies the
> appropriate files to your bin (or dist/bin ?) directory for version
> control management.
>
> - Simon
>
> -----Original Message-----
> From: Ben Collins-Sussman [mailto:sussman@collab.net]
> Sent: Monday, April 26, 2004 4:31 PM
> To: David Findley
> Cc: users@subversion.tigris.org
> Subject: Re: svn status showing "phantom" files?
>
>
> On Mon, 2004-04-26 at 16:25, David Findley wrote:
>> Next, I open the
>> project in Eclipse and allow it to build the .class
>> files, which it does.
>
> Eclipse is Evil. When you do this, it destroys your .svn/ directories.
> It treats the whole directory as an "opaque bundle", much like NeXTStep
> project builder.
>
> So what you're seeing is what happens when the .svn/ directory is
> destroyed. Lots of files/dirs are listed as "missing".
>
> --------------------------
> NOTE: This message and any included attachments are from HealthCom
> Partners, LLC and are intended only for the addressee(s). The
> information contained herein may include trade secrets or privileged
> or otherwise confidential information. Unauthorized review,
> forwarding, printing, copying, distributing, or using such information
> is strictly prohibited and may be unlawful. If you received this
> message in error, or have reason to believe you are not authorized to
> receive it, please promptly delete this message and notify the sender
> by e-mail.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Apr 27 01:16:12 2004