Bug 539139 - code cleanup in ClasspathMultiReleaseJar

 - catch all runtime exceptions declared by FileSystems.newFileSystem
 - don't use e.printStackTrace()
 - log errors if classes can't be found or module can't be initialized
etc.
 - use try with resources
 - use blocks for if/else


Change-Id: I8fddf164efb7658d452f054ac3a80ccb54e5f3f0
Signed-off-by: Andrey Loskutov <loskutov@gmx.de>
1 file changed
tree: caf7e3f6baf695f3a949d62cc834c3c6c14ab7b7
  1. modules/
  2. org.eclipse.jdt.annotation/
  3. org.eclipse.jdt.annotation_v1/
  4. org.eclipse.jdt.apt.core/
  5. org.eclipse.jdt.apt.pluggable.core/
  6. org.eclipse.jdt.apt.pluggable.tests/
  7. org.eclipse.jdt.apt.tests/
  8. org.eclipse.jdt.apt.ui/
  9. org.eclipse.jdt.compiler.apt/
  10. org.eclipse.jdt.compiler.apt.tests/
  11. org.eclipse.jdt.compiler.tool/
  12. org.eclipse.jdt.compiler.tool.tests/
  13. org.eclipse.jdt.core/
  14. org.eclipse.jdt.core.ecj.validation/
  15. org.eclipse.jdt.core.internal.tools/
  16. org.eclipse.jdt.core.tests.builder/
  17. org.eclipse.jdt.core.tests.compiler/
  18. org.eclipse.jdt.core.tests.model/
  19. org.eclipse.jdt.core.tests.performance/
  20. tests-pom/
  21. .gitignore
  22. pom.xml
  23. README.md
README.md

JDT Core

This is the core part of Eclipse's Java development tools. It contains the non-UI support for compiling and working with Java code, including the following:

  • an incremental or batch Java compiler that can run standalone or as part of the Eclipse IDE
  • Java source and class file indexer and search infrastructure
  • a Java source code formatter
  • APIs for code assist, access to the AST and structured manipulation of Java source.

For more information, refer to the [JDT wiki page] 1 or the [JDT project overview page] 2.

License

Eclipse Public License (EPL) v1.0