-
Notifications
You must be signed in to change notification settings - Fork 492
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Development tooling: add 'enable hints for javac warnings' to project settings #2644
Comments
@bencomp after talking to you the other week I opened Netbeans Bug 255606 – Allow per-project settings (i.e. which warnings are enabled) to be shared across teams via source control - https://netbeans.org/bugzilla/show_bug.cgi?id=255606 The nb-configuration.xml file you sent me (below) says, "Properties that influence various parts of the IDE, especially code formatting and the like. You can copy and paste the single properties, into the pom.xml file and the IDE will pick them up." Based on this I tried adding it to the pom.xml like below but it didn't seem to make any difference (but quite possibly I'm doing something wrong):
Anyway, yes, let's try to get at the root problem. Developers are less likely to use raw types if their IDE such as Netbeans is warning about them. Maybe we should check in a nb-configuration.xml file? Other projects seem to do this. Right now it's in our .gitignore: https://github.com/IQSS/dataverse/blob/v4.2/.gitignore Contents of the nb-configuration.xml you sent me:
|
In #2574 I argue that the code lacks proper generics, which causes type safety warnings and makes parts of the code hard to understand.
In the Dataverse channel on IRC, @pdurbin says that developers don't see the warnings and my efforts to add generics ( #2422, #2425, #2589, etc.) don't tackle the root problem - that developers don't understand the benefits of Java generics.
Earlier Phil and I looked at possibilities to allow NetBeans configuration with the option to highlight code with raw types and unchecked conversions enabled to be shared in the repository.
Whereas in #775 we discussed that code quality should not depend on a single IDE, in practice it could make sense to nudge the NetBeans users to pay attention by supplying the correct settings automatically.
Simply asking them to change their settings is said to have too little effect.
The text was updated successfully, but these errors were encountered: