Some of the warnings may be covered by one of these tickets https://issues.apache.org/jira/issues/?jql=text%20~%20%22Warnings%22%20AND%20project%20%3D%20NetBeans%20and%20status%20!%3D%20Closed
Eric Bresie [email protected] > On June 13, 2019 at 11:44:19 AM CDT, Brad Walker <[email protected]> wrote: > Hey Ken, > > The build warnings drive me nuts. So I've been working on cleaning them up > "here and there" as I can. > > I can say a lot of the build warnings could be fixed with some easy work. > Many of the build warnings do require some thought to fixing them. > > My experience is that cleaning up build warnings is a great student > project. The students would be able to hone their skills in Java and also > to give some technical thought on how to prioritize items for fixing. Also, > they would learn how to deal with a large software application. Many of the > warnings will require some technical thought but should be easy for a > college student to tackle. > > If your students would "freak out" over the build warnings, this is a good > time for them to also grow as engineers. I've worked on a lot of projects > professionally where there are a many warnings for various valid, technical > reasons. > > Hope my comments help. > > -brad w. > > On Thu, Jun 13, 2019 at 10:28 AM Kenneth Fogel <[email protected]> > wrote: > > > Hi, > > > > I am building NB from the current code in the repository. Its about a half > > hour job on my Windows machine and is going on while I type this. I am > > curious about the numerous build warnings. There are thousands. I know if I > > gave my students code to build and there were numerous warnings they would > > freak out. I know I can ignore them but is there not a process to slowly > > clean these up? I understand that fixing this is risky and many of the > > warnings are compiler based such as "unchecked" or "deprecated". I just > > want to learn more about how major projects are maintained over time. > > > > Ken > >
