This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
org-netbeans-modules-project-ant is now in the java1 cluster. This is architecturally not correct. The java1 cluster should only contain moules that directly support the Java language and not modules that other non-Java projects may depend on. The C/C++ development pack (CND) projects are ant based (hence needs org-netbeans-modules-project-ant) and we have been one of the main requesters for this new Java cluster. A pure java cluster would enable us to run CND in NetBeans with no Java language support. It is one of the requirements to the Sun Studio product.
I thought CND projects used make? What do they use ant/project for? Please provide some details.
Yes, we use make and makefiles where Java projetcs use ant and build.xml files, but we are never the less ant based projects because of the basic project support it gives us. We use for instance ProjectGenerator.createProject(...) to create our projects and we use several methods from AntProjectHelper to maintain the project. Back when we originally designed CND projects (probably 2 years ago) we were actually adviced to make them ant based to take advantage of the basic project support ant based projects would give us. I checked a couple of other non-Java projects (symbian projects from mobility and cpplite projects) and they are also ant based probably for the same reasons as ours. I don't know if there is a good alternative today to what we do without rewriting a lot of code. Perhaps the most basic features should be factored out of org-netbeans-modules-project-ant
Well I can move it, as it does not directly reference anything in the Ant module, by design. Really most of the module deals with pretty Ant-specific things, such as properties files with a specific substitution syntax. There are only a few generic things, such as project.xml manipulation, but I guess these are the things you are using. Ideally these should indeed be factored out; late in a release cycle is not a good time to do it.
Moving ant/project to ide would solve our issue. Factoring out the basic project support would also solve our issue but is probably too late to do. But I'm not sure I believe ant/project belongs in the java cluster at all. I can imagine *true* ant based projects that are not Java projects and they shound't need the java cluster.
Checking in nbbuild/cluster.properties; /shared/data/ccvs/repository/nbbuild/cluster.properties,v <-- cluster.properties new revision: 1.253; previous revision: 1.252 done Checking in ide/golden/cluster-deps.txt; /shared/data/ccvs/repository/ide/golden/cluster-deps.txt,v <-- cluster-deps.txt new revision: 1.101; previous revision: 1.100 done Checking in ide/golden/deps.txt; /shared/data/ccvs/repository/ide/golden/deps.txt,v <-- deps.txt new revision: 1.569; previous revision: 1.568 done Checking in ide/golden/files-layout.txt; /shared/data/ccvs/repository/ide/golden/files-layout.txt,v <-- files-layout.txt new revision: 1.246; previous revision: 1.245 done Checking in ide/golden/modules.txt; /shared/data/ccvs/repository/ide/golden/modules.txt,v <-- modules.txt new revision: 1.147; previous revision: 1.146 done
Btw. refactoring things out and moving the rest to javaX cluster is going to be incompatible change. So unless you do it by the release, it is probably better to not do it for "small" reasons. Where "small" includes - purity, beauty, coolness, doing things the right way, etc.