DASCA
/
WALA
2
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Tell Eclipse to ignore some questionable manifest contents 

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.
This commit is contained in:
Ben Liblit 2018-03-21 20:25:21 -05:00
parent 9d7df5de7e
commit 272e3adaf8
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
com.ibm.wala.cast/.settings/org.eclipse.pde.prefs
View File

@ -1,14 +1,14 @@
compilers.f.unresolved-features=0
compilers.f.unresolved-plugins=0
compilers.incompatible-environment=0
compilers.p.build=0
compilers.p.build.bin.includes=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=0
compilers.p.build.source.library=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
@ -25,7 +25,7 @@ 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=0
compilers.p.unresolved-import=2
compilers.s.create-docs=false
compilers.s.doc-folder=doc
compilers.s.open-tags=0