Geek Answers Handbook

NetBeans: should nbactions.xml, nb-configuration.xml and catalog.xml go to the source control?

This thread is very useful for figuring out which files in Netbeans should go to the original counter, but it does not apply to all files.

In particular, I am wondering if the following files should go to the original control. Here are my assumptions / assumptions:

  • nb-configuration.xml - the simplest - the file itself in the comment says that it should go to the original control.

  • nbactions.xml - from what I see, this file stores information typical for launching an application. That is, JVM, etc. Therefore, I suggest that this is a matter of taste - if you want other developers to have a “suggested” launch configuration, enable it. Otherwise, no. Correctly?

  • catalog.xml - not sure what it does (I'm sure it is used by the editor to learn xml schemes, etc., to enable syntax coloring, but this is just an assumption). In any case, I see that this file has system information (path), so it should not go into the source code.

Can anyone confirm this? Thanks,

Peter

+8
version-control netbeans
source share
3 answers

In my Maven based projects, I put nbactions.xml in the original control. Just make sure you change the absolute paths to relative.

+2
source share

I have never added IDE configuration files to the repository for several reasons:

  • other colleagues may want to use them;
  • other colleagues may want to use other IDEs (for example, Eclipse) and see that these files (or even exclude them from the scan) may annoy them;
  • some of these files are usually not associated with one project, others are automatically generated, so there is no need to store them in the source code of each project.

To exclude them, our first solution was .svnignore , but it was logically incorrect to modify some common content for the specific needs of one user, so we decided to be more strict:

in my ~/.subversion/config I have:

 [miscellany] global-ignores = nbactions.xml nbproject

Hope this helps,

Marcello

+3
source share

I put nbactions.xml in the original control, but there is a caveat: its internal format may change, so if your developers use different versions of NetBeans for some reason, you could remove it because sharing becomes unpleasant.

I recently upgraded from NetBeans 7.3.1 to 7.4, and the "Run" action received a strange error message. I solved the problem by deleting and regenerating nbactions.xml : the old one had a custom Maven target for the "Run" and "Debug" actions; it was org.codehaus.mevenide:netbeans-deploy-plugin:1.2.4:deploy , it was not visible in IDE v7.3.1 (maybe it was generated by an older version for internal use) and generated a class not found for org.openide.util.Lookup in v7.4. I document the problem here because I found a solution myself after a failed search on the Web. Hope this helps someone else.

+2
source share

More articles:


All Articles