Set required build property for project-specific compiler settings
This fixes two Eclipse Plug-in Development warnings of the form "The 'javacProjectSettings' build entry should be set when there are project specific compiler settings".
This commit is contained in:
parent
182073ff4f
commit
d70e52e323
|
@ -4,7 +4,7 @@ compilers.incompatible-environment=1
|
|||
compilers.p.build=1
|
||||
compilers.p.build.bin.includes=1
|
||||
compilers.p.build.encodings=1
|
||||
compilers.p.build.java.compiler=1
|
||||
compilers.p.build.java.compiler=0
|
||||
compilers.p.build.java.compliance=1
|
||||
compilers.p.build.missing.output=1
|
||||
compilers.p.build.output.library=1
|
||||
|
|
|
@ -4,3 +4,4 @@ bin.includes = META-INF/,\
|
|||
.,\
|
||||
OSGI-INF/l10n/bundle.properties,\
|
||||
OSGI-INF/
|
||||
javacProjectSettings = true
|
||||
|
|
|
@ -4,7 +4,7 @@ compilers.incompatible-environment=1
|
|||
compilers.p.build=1
|
||||
compilers.p.build.bin.includes=1
|
||||
compilers.p.build.encodings=1
|
||||
compilers.p.build.java.compiler=1
|
||||
compilers.p.build.java.compiler=0
|
||||
compilers.p.build.java.compliance=1
|
||||
compilers.p.build.missing.output=1
|
||||
compilers.p.build.output.library=1
|
||||
|
|
|
@ -10,4 +10,4 @@ bin.includes = META-INF/,\
|
|||
com.ibm.wala.core.testdata_1.0.0a.jar,\
|
||||
OSGI-INF/l10n/bundle.properties,\
|
||||
OSGI-INF/
|
||||
|
||||
javacProjectSettings = true
|
||||
|
|
|
@ -4,7 +4,7 @@ compilers.incompatible-environment=1
|
|||
compilers.p.build=1
|
||||
compilers.p.build.bin.includes=1
|
||||
compilers.p.build.encodings=1
|
||||
compilers.p.build.java.compiler=1
|
||||
compilers.p.build.java.compiler=0
|
||||
compilers.p.build.java.compliance=1
|
||||
compilers.p.build.missing.output=1
|
||||
compilers.p.build.output.library=1
|
||||
|
|
|
@ -4,3 +4,4 @@ bin.includes = META-INF/,\
|
|||
.,\
|
||||
OSGI-INF/l10n/bundle.properties,\
|
||||
OSGI-INF/
|
||||
javacProjectSettings = true
|
||||
|
|
Loading…
Reference in New Issue