> Since new hotness I'm having an issue where merging a topic branch
> back into the main branch fails because ".classpath" is not up to
> date. When switching back to the main branch, .classpath appears to
> get touched and subsequently is a newer version from what exists in
> the topic branch. Is it possible to exclude .classpath from
> versioning? Will WOLips simply re-create it if it isn't checked out
> with a project?
A checked out project will not build without a .classpath -- it's
impossible for wolips to autocreate it (it defines your project
dependencies). So it needs to be versioned. WOLips is autoconverting
old .classpath formats to the new .classpath format, though, which is
probably what you're seeing with it getting touched.
ms
This archive was generated by hypermail 2.0.0 : Thu Sep 18 2008 - 18:16:16 EDT