4dc1e41529
These manifest files are here for use by the Maven build, but Eclipse is now using Gradle (via Buildship). So the manifests as seen by Eclipse do not entirely make sense. I'm hesitant to change the manifests directly, since presumably they were correct for Maven and still are. Perhaps some day we'll be using Gradle to generate manifests. Until that day comes, we're better off leaving the manifests as they are and just suppressing Eclipse's warnings instead.
33 lines
1.0 KiB
INI
33 lines
1.0 KiB
INI
compilers.f.unresolved-features=0
|
|
compilers.f.unresolved-plugins=0
|
|
compilers.incompatible-environment=0
|
|
compilers.p.build=2
|
|
compilers.p.build.bin.includes=2
|
|
compilers.p.build.encodings=0
|
|
compilers.p.build.java.compiler=0
|
|
compilers.p.build.java.compliance=0
|
|
compilers.p.build.missing.output=0
|
|
compilers.p.build.output.library=2
|
|
compilers.p.build.source.library=2
|
|
compilers.p.build.src.includes=0
|
|
compilers.p.deprecated=0
|
|
compilers.p.discouraged-class=0
|
|
compilers.p.internal=0
|
|
compilers.p.missing-packages=0
|
|
compilers.p.missing-version-export-package=2
|
|
compilers.p.missing-version-import-package=0
|
|
compilers.p.missing-version-require-bundle=2
|
|
compilers.p.no-required-att=0
|
|
compilers.p.not-externalized-att=0
|
|
compilers.p.unknown-attribute=0
|
|
compilers.p.unknown-class=0
|
|
compilers.p.unknown-element=0
|
|
compilers.p.unknown-identifier=0
|
|
compilers.p.unknown-resource=0
|
|
compilers.p.unresolved-ex-points=0
|
|
compilers.p.unresolved-import=2
|
|
compilers.s.create-docs=false
|
|
compilers.s.doc-folder=doc
|
|
compilers.s.open-tags=0
|
|
eclipse.preferences.version=1
|