Initial commit.
add a simple .gitignore
add simple pom.xml
add classes from core branch
oops fix compilation failure
add jenkins parent and license informations
add scm infos
add myself as maintainer
[maven-release-plugin] prepare release config-provider-model-1.0
[maven-release-plugin] prepare for next development iteration
add me as dev
add marker interfaces to remove dependecy from config-file-provider-plugin to maven-plugin
[maven-release-plugin] prepare release config-provider-model-1.1
[maven-release-plugin] prepare for next development iteration
change name
doc improvement
There's duplicate defined in the maven plugin, and I'm assuming these are deprecated.

After all, if the base module needs to define such a marker for every use of ConfigProvider, I think it'd be broken
given that the ID needs to start with the provider ID, this default implementation doesn't make sense.
ConfigProvider/Config should be Descriptor/Describable

This brings the instantiation of Config in line with the rest of UI, and allows the Config implementations to enjoy the core taglib support and other existing infrastructure, such as form validation and checks. For example, Config object can now (and should) have default config.jelly that the rest of the client plugins can utilize.

Unfortunately, some of the ConfigProvider methods have already deviated from the Descriptor class, such that I couldn't eliminate some of the code duplication, but I still think this alignment is better long-term
folding ConfigDescription back into what Descriptor already does