SVN Ignore bin folder? How do you debug?

Development
1

Hi Joel, all.

How do you debug Vassal? Do you compile it into a “bin” folder, like what Eclipse lets us do? If so, should we commit a “svn:ignore bin” on trunk?

Or should I commit my own “svn:ignore bin” on my own branch (branches/viewport-3.2), and inform Joel to “block” this change? This can be done by lying to the trunk:

Say I commited a “snv:ignore bin” in r123. Say my branch is at (vassalengine.svn.sourceforge.ne … ewport-3.2, actually).

[]svn merge -c r123 --record-only [/]
[]svn status[/]
[]svn propget svn:mergeinfo[/]
[]svn commit -m “Ignoring Jon’s r123”[/]

What does everyone think about this?

2

Thus spake viewofheaven:

Hi Joel, all.

How do you debug Vassal? Do you compile it into a “bin” folder, like
what Eclipse lets us do? If so, should we commit a “svn:ignore bin” on
trunk?

I’m not sure what you’re asking. Can you be more specific about what
you’re trying to do?

–
J.

3

Commit a “svn:ignore bin” to ignore a bin folder. This folder is generated when I compile Vassal engine in Eclipse, usually for debugging purposes. The Makefile does this differently, and actually doesn’t leave behind traces (such as a bin or tmp folder).

Hence, the question. How do you debug Vassal engine? I don’t wanna commit a “svn:ignore bin” just to suit my Eclipse debug.

4

Thus spake viewofheaven:

Commit a “svn:ignore bin” to ignore a bin folder. This folder is
generated when I compile Vassal engine in Eclipse, usually for debugging
purposes. The Makefile does this differently, and actually doesn’t leave
behind traces (such as a bin or tmp folder).

Hence, the question. How do you debug Vassal engine? I don’t wanna
commit a “svn:ignore bin” just to suit my Eclipse debug.

The Makefile puts class files into the classes directory. I have Eclipse
set to do the same for the rare occasions when I use it.

(Debugging seems like a different issue to me. I use jdb for that.)

–
J.

5

Well, ok, I guess I’ll simply do a global ignore whenever I wanna play with VassalEngine coding. Note point fixing Vassal files for any particular IDE. But if we are to commit a svn:ignore, I’d recommend ignoring “classes”, and not “bin”.

Note to anyone else who might need this. Just set SVN client (say TortoiseSVN) thus:

[]TortoiseSVN[/]
[]Settings[/]
[]Under “General” page[/]
[]Under “Subversion” section[/]
[]Field “Global ignore pattern”[/]
[]Append " classes" (without quotes)[/]

6

Thus spake viewofheaven:

Well, ok, I guess I’ll simply do a global ignore whenever I wanna play
with VassalEngine coding. Note point fixing Vassal files for any
particular IDE. But if we are to commit a svn:ignore, I’d recommend
ignoring “classes”, and not “bin”.

Note to anyone else who might need this. Just set SVN client (say
TortoiseSVN) thus:

  • TortoiseSVN
  • Settings
  • Under “General” page
  • Under “Subversion” section
  • Field “Global ignore pattern”
  • Append " classes" (without quotes)

On reflection, “bin” is the standard name, so I’ve switched the Makefile
to use that instead of “classes” for binary output, and added some
svn:ignores. Should have done that long ago.

–
J.