Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Mastering Java 11

You're reading from   Mastering Java 11 Develop modular and secure Java applications using concurrency and advanced JDK libraries

Arrow left icon
Product type Paperback
Published in Sep 2018
Publisher Packt
ISBN-13 9781789137613
Length 462 pages
Edition 2nd Edition
Languages
Tools
Arrow right icon
Authors (2):
Arrow left icon
Dr. Edward Lavieri Jr. Dr. Edward Lavieri Jr.
Author Profile Icon Dr. Edward Lavieri Jr.
Dr. Edward Lavieri Jr.
Mandar Jog Mandar Jog
Author Profile Icon Mandar Jog
Mandar Jog
Arrow right icon
View More author details
Toc

Table of Contents (20) Chapters Close

Preface 1. The Java 11 Landscape FREE CHAPTER 2. Discovering Java 11 3. Java 11 Fundamentals 4. Building Modular Applications with Java 11 5. Migrating Applications to Java 11 6. Experimenting with the Java Shell 7. Leveraging the Default G1 Garbage Collector 8. Microbenchmarking Applications with JMH 9. Making Use of the Process API 10. Fine-Grained Stack Tracing 11. New Tools and Tool Enhancements 12. Concurrency Enhancements 13. Security Enhancements 14. Command-Line Flags 15. Additional Enhancements to the Java Platform 16. Future Directions 17. Contributing to the Java Platform 18. Assessment 19. Other Books You May Enjoy

Resolving lint and doclint warnings

Lint and doclint are sources that report warnings to javac. Let's take a look at each one:

  • Lint analyzes bytecode and source code for javac. The goal of lint is to identify security vulnerabilities in the code being analyzed. Lint can also provide insights into scalability and thread locking concerns. There is more to lint and the overall purpose is to save developers time.
You can read more about lint here:
http://openjdk.java.net/jeps/212
  • Doclint is similar to lint and is specific to javadoc. Both lint and doclint report errors and warnings during the compile process. Resolution of these warnings was the focus of JEP 212. When using core libraries, there should not be any warnings. This mindset led to JEP 212, which has been resolved and implemented in Java 9.
A comprehensive list of the lint and doclint warnings can be reviewed...
lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime