LOG4J2-619 - correct bad fix

git-svn-id: https://svn.apache.org/repos/asf/logging/log4j/log4j2/trunk@1603048 13f79535-47bb-0310-9956-ffa450edef68
LOG4J2-539: Fixed issue with "Reconfigure using XML below" function in JMX Client GUI.
ConfigurationSource is now a top-level class and can be obtained with Configuration.getConfigurationSource().
LoggerContext.getConfiguration().getConfigurationSource() provides a reliable public method for obtaining a logger context's configuration location and content.

git-svn-id: https://svn.apache.org/repos/asf/logging/log4j/log4j2/trunk@1603937 13f79535-47bb-0310-9956-ffa450edef68
fix XML structure (maven wouldn't build the site)

git-svn-id: https://svn.apache.org/repos/asf/logging/log4j/log4j2/trunk@1604048 13f79535-47bb-0310-9956-ffa450edef68
Use correct LoggerContext

git-svn-id: https://svn.apache.org/repos/asf/logging/log4j/log4j2/trunk@1604079 13f79535-47bb-0310-9956-ffa450edef68
Add missing license headers

git-svn-id: https://svn.apache.org/repos/asf/logging/log4j/log4j2/trunk@1604081 13f79535-47bb-0310-9956-ffa450edef68
Add license header

git-svn-id: https://svn.apache.org/repos/asf/logging/log4j/log4j2/trunk@1604082 13f79535-47bb-0310-9956-ffa450edef68
LOG4J2-673 – plugin preloading fails in shaded jar files
Support for plugin preloading through the standard javax.annotation.processing tool was adding in LOG4J2-595

But the plugin processor always creates and stores the processed "Plugin" annotated classes into the same file. This works fine when the classpath consists of individual jar files, but fails when shaded jar files are used.

The fix saves the dat file in a location under META-INF that matches the shared package all the processed plugins are found under.
The package attribute in the config file is then used so that multiple dat files can be loaded at runtime.
This means that the package attribute is no longer deprecated.