Hi Jacopo,

> it would be much better to keep all these kind of file in a downloadable
> external file (or similar)

I totally agree with this.

Currently, I'm keeping all binaries (compiled codes) outside of SVN in my private OFBiz SVN (for individual projects). Doesn't make a lot of sense to include unchangeable files in the SVN. SVN tracks _changes_ to files! But that's a different reason from that for excluding config files unrelated to OFBiz.

I agree that we should keep Eclipse-related files in an external download (not 
in SVN).

Jonathon

Jacopo Cappellato wrote:
Hi Jacques,

in my opinion it is not a great idea.
Even if I am a NetBeans user (possibly one of the few in the OFBiz circle), I'd prefer to keep this file out:

1) because it is not usable as is (you have to at least unzip it)
2) because I don't like the idea of having config files for development environment in trunk (I can accept the existing file for Eclipse because many seem interested in it and because it is just onle little file); it would be much better to keep all these kind of file in a downloadable external file (or similar)

So I think that the one interested can simply use the file from the Jira issue.

Just my 2 cents... what do other think of this?

Jacopo



[EMAIL PROTECTED] wrote:
Author: jleroux
Date: Sun Sep  9 02:40:21 2007
New Revision: 573974

URL: http://svn.apache.org/viewvc?rev=573974&view=rev
Log:
I finally decided to add the file in root as is : better than nothing and maybe interested people will help toi update it when needed...
This close https://issues.apache.org/jira/browse/OFBIZ-3

Added:
    ofbiz/trunk/nbproject.zip   (with props)

Added: ofbiz/trunk/nbproject.zip
URL: http://svn.apache.org/viewvc/ofbiz/trunk/nbproject.zip?rev=573974&view=auto ==============================================================================
Binary file - no diff available.

Propchange: ofbiz/trunk/nbproject.zip
------------------------------------------------------------------------------
    svn:mime-type = application/zip





Reply via email to