[Bluej-discuss] BlueJ and darcs: "Boring Files" and extra folders

[Michael Kölling]

On 10 May 2007, at 19:37, Charles Bachhuber wrote:

> Hello! I'm looking into shareing BlueJ projects using darcs. What  
> files in the project folder are 'boring' and don't need to be  
> copied across? '*.\.class' files and 'doc/.*', at least, I would  
> assume, but what about the '*.\.ctxt' and 'bluej.pk?'? Also, will  
> bluej complain about haveing the extra folder '_darcs' in a project  
> folder?

The following can be deleted:

*.class	can be re-created with "compile"
*.ctxt	can be re-created with "compile"
doc/		can be re-created with "generate doc"
bluej.pkh	is a backup file, will be re-generated


bluej.pkg should be left - it contains diagram information. It's not  
fatal if it gets lost -- BlueJ would do a recovery and much of the  
information would be automatically regenerated, but info about  
positions of class icons on screen, for example, would be lost.

An extra folder should not be a problem, but if it contains java  
classes or sources, it would show up as a package in BlueJ. To avoid  
that, you could give it a name that is not a valid Java identifier  
(as we have done with the +libs directory).

mik