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.
If an automatic project processes a directory, maven seems to always take precedence over ant if both build systems are present. The automatic project should allow the user to choose which of them to use.
The existence of a pom.xml means there is definitely Maven metadata. Automatic projects based on scanning build.xml are generally a poor second choice, so this project factory is registered with a lower priority. That said, it would make sense for autoproject.core to register _two_ factories: one with high priority that only recognizes folders explicitly selected as autoprojects in the New Project wizard; and one with low priority that recognizes folders with a build.xml, if that option is enabled.
I agree with more metadata being available from mave from the point of view of the project detection software and in general, but I do have the situation that in the checked out subversion directory the (older) ant build process is the one that works and the (newer) maven based is the one that is incorrect and doesn't. The build is handled by somebody else in the project. There are not many options to deal with this (are there?) and being able to select the ant-based way for getting metadata on purpose for a specific project would therefore help tremendously.
The general advice would be to move the pom.xml into a Subversion branch (or a subfolder) until it is stabilized, but where that is not an option, this RFE would be useful.
This old bug may not be relevant anymore. If you can still reproduce it in 8.2 development builds please reopen this issue. Thanks for your cooperation, NetBeans IDE 8.2 Release Boss