• Guus der Kinderen's avatar
    OF-546: Plugins should not inherit from parent. · 0ac528dd
    Guus der Kinderen authored
    The build plans for the plugins should not inherit from the parent project, as this
    ties their existence in with our parent project. Third party developers cannot do
    this (without modifying the parent project structure). We should facilitate third
    party developers, and use the same tools as we provide them.
    
    This commit removes the parent/child dependencies between the top-level parent POM
    and the plugins POM. There still as a parent/child dependency between the plugins
    POM and each individual plugin.
    
    Although I'm not sure this change is a complete solution, it is aimed to more closely
    represent a development setup in which a third party developer might find itself. To
    create a plugin of their own, they can now:
    
     - Use our 'plugins' module directly (define it as a parent)
     - Replace our 'plugins' module by a proprietary one (when developing multiple
       proprietary plugins).
     - Take most POM definition from our 'plugins' module and merge that with a new
       stand-alone plugin project.
    0ac528dd
Name
Last commit
Last update
build Loading commit data...
dbutil Loading commit data...
documentation Loading commit data...
i18n Loading commit data...
plugins Loading commit data...
src Loading commit data...
starter Loading commit data...
webadmin Loading commit data...
xmppserver Loading commit data...
.gitignore Loading commit data...
.travis.yml Loading commit data...
LICENSE.txt Loading commit data...
Makefile Loading commit data...
README.md Loading commit data...
pom.xml Loading commit data...