search

jishipp / javacv

Automatically exported from code.google.com/p/javacv
GNU General Public License v2.0
0 stars 0 forks source link

nbproject directory should not be under version control #210

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?
IDE-dependent files should be out of version control

What version of the product are you using? On what operating system?

Please provide any additional information below.
It's a bad practice to store ide-project files under  version control. Idea, 
Netbeans and eclipse can import maven projects

Original issue reported on code.google.com by Jkolo...@gmail.com on 20 Jun 2012 at 9:44

GoogleCodeExporter commented 9 years ago 
And what about people that don't use an IDE or Maven?

Original comment by samuel.a...@gmail.com on 21 Jun 2012 at 2:59

GoogleCodeExporter commented 9 years ago 
Those who don't use ide don't need ide-files. Those who use can create 
project-files from maven pom.xml files and forget about maven if they don't 
need it.
I think 99% use IDE for java development. Maven usage is not an obligation..

Original comment by Jkolo...@gmail.com on 21 Jun 2012 at 3:05

GoogleCodeExporter commented 9 years ago 
The build.xml file requires the files in nbproject. Can we somehow create a 
self-contained build.xml file from the pom.xml file or something?

Original comment by samuel.a...@gmail.com on 21 Jun 2012 at 3:31

GoogleCodeExporter commented 9 years ago 
Once we have maven integrated and working you wont need build.xml.

Original comment by Jkolo...@gmail.com on 21 Jun 2012 at 3:37

GoogleCodeExporter commented 9 years ago 
I am sure users who don't use Maven would disagree.

Original comment by samuel.a...@gmail.com on 21 Jun 2012 at 3:38

GoogleCodeExporter commented 9 years ago 
User who don't use netbeans don't need netbeans project files in repo too. what 
about users who don't use ant?d
Also this build require javacpp SOURCE. instead of only jar file

Original comment by Jkolo...@gmail.com on 21 Jun 2012 at 3:45

GoogleCodeExporter commented 9 years ago 
basically you cannot modify the build without netbeans and it sucks. on the 
other side maven is ide-independent

Original comment by Jkolo...@gmail.com on 21 Jun 2012 at 3:47

GoogleCodeExporter commented 9 years ago 
The pom.xml file depends in no way on build.xml or nbproject. We don't need 
NetBeans to modify the build. I am not sure what your gripe is about... ?

Original comment by samuel.a...@gmail.com on 22 Jun 2012 at 10:04

GoogleCodeExporter commented 9 years ago 
why do you want to support 2 build systems (maven and ant(netbeans's build xml 
is not easy to modify unlike pom.xml))  if maven covers everything?

Original comment by Jkolo...@gmail.com on 23 Jun 2012 at 11:55

GoogleCodeExporter commented 9 years ago 
I wasn't sure that Maven could do everything I wanted from it, but I am now 
pretty convinced that I can, so it's probably not worth maintaining the 
Ant-related files. They still work for now, but when they break, it's probably 
better to remove them. I will wait for that moment...

Original comment by samuel.a...@gmail.com on 16 Jul 2012 at 8:49

GoogleCodeExporter commented 9 years ago 
keep files.

Original comment by kuznetsov.alexey on 15 Nov 2012 at 3:47

GoogleCodeExporter commented 9 years ago 
Done! NetBeans project files have been scrubbed away starting with the latest 
release of JavaCV 0.8.

Incidentally, the project is now hosted on GitHub:
    https://github.com/bytedeco/javacv

Original comment by samuel.a...@gmail.com on 29 Apr 2014 at 12:09