9cd422d56a
Since March 2014 Bukkit has been converting and preparing plugins for UTF-8 compliance. With this change in place, all plugins will now load their configuration files as UTF-8, which is a supported encoding on any valid JVM implementation. This should pose no issues on any server which has run Bukkit after 2014, and the only possible breaking path is when an embedded file is of a non UTF-8 compatible encoding (which it should not be anyway). By: Matt <mattbdev@outlook.com>
29 lines
792 B
Java
29 lines
792 B
Java
package org.bukkit.plugin;
|
|
|
|
import java.util.Set;
|
|
|
|
/**
|
|
* Represents a concept that a plugin is aware of.
|
|
* <p>
|
|
* The internal representation may be singleton, or be a parameterized
|
|
* instance, but must be immutable.
|
|
*/
|
|
public interface PluginAwareness {
|
|
/**
|
|
* Each entry here represents a particular plugin's awareness. These can
|
|
* be checked by using {@link PluginDescriptionFile#getAwareness()}.{@link
|
|
* Set#contains(Object) contains(flag)}.
|
|
*/
|
|
public enum Flags implements PluginAwareness {
|
|
/**
|
|
* This specifies that all (text) resources stored in a plugin's jar
|
|
* use UTF-8 encoding.
|
|
*
|
|
* @deprecated all plugins are now assumed to be UTF-8 aware.
|
|
*/
|
|
@Deprecated
|
|
UTF8,
|
|
;
|
|
}
|
|
}
|