I think that will work. We could have nbproject-5.5, nbproject-6.0, etc.
On 6/29/07, Knut Anders Hatlen <[EMAIL PROTECTED]> wrote:
David Van Couvering <[EMAIL PROTECTED]> writes: > So, the message is, guaranteed compatibility from older to newer > version, but no guarantee from newer version to older version. And, > once you open a project with a newer version, it is auto-upgraded to > that new version's format. OK, so it sounds like there could be problems, like extra diffs, if people use different versions. What about adding a directory which contain project file templates instead? Then one could just do a "cp -r tools/templates/nbproject ." or something each time a new copy was checked out. That would allow users to do customizations without conflicting with the checked-in template. The same thing could be done for other IDEs as well. > On 6/28/07, David Van Couvering <[EMAIL PROTECTED]> wrote: >> I didn't get any answer from the user community about about project >> file portability between versions, I"m going to try another channel... >> >> On 6/28/07, Knut Anders Hatlen <[EMAIL PROTECTED]> wrote: >> > David Van Couvering <[EMAIL PROTECTED]> writes: >> > >> > > I don't know about the guaranteed compatibility between major >> > > versions, but I did notice that I could open a project in NB 5.5 that >> > > I created in NB 6, so things look pretty stable. But you're right, >> > > that's a concern. I'll ask around and see if I can find out how >> > > that's addressed, and get back to this list. >> > > >> > > All local changes are stored in a directory called 'private'. If you >> > > svn:ignore this directory, then what gets checked in is fully portable >> > > across user environments. >> > >> > Thanks for checking this out, David. It sounds OK to me. If it ever >> > becomes a problem, there's always the possibility of backing it out. >> > >> > -- >> > Knut Anders >> > >> -- Knut Anders
