IDEA gets super confused when you take a jar task and make it not a jar task.
These are only really used when running from CI (running `./gradlew jar` in
meta will still trigger all of the `:plugin:XXX:jar` tasks), so the names don't
matter.
Accessing 'repo' is bad practice and disabled in newer artifactory
versions (like the one we just deployed). Rely on releases instead.
Also, the identd plugin was depending on the wrong parser, and
was presumably pulling in criminally old versions from artifactory.
This prevents DMDirc's transitive dependencies from being bundled
in plugins. e.g. DMDirc includes SLF4J, so any plugin that depends
on it (or depends on another project that depends on SLF4J) should
not include it in the plugin jar to avoid having duplicate classes
from different class loaders.
Stop swimming against the tide and accept what most of the rest of
the world does.
While it adds an annoying depth to the actual source code, it makes
the root directory nicer (no more 'test-res' dirs), means we don't
have to override the gradle config, and makes it nicer to work in
IDEA 2016.1.
This makes the plugins include their version in the output file
name, and when used as a dependency.
Also create a dist-versioned directory which accumulates versioned
plugins.
Whenever we build a new jar -- or if the jar in dist is changed --
copy it into the dist directory with a proper name.
Change-Id: If05133cf38f1dbe2ce9ba6ace94bf8cf2b466bc1
Reviewed-on: http://gerrit.dmdirc.com/4060
Automatic-Compile: DMDirc Build Manager
Reviewed-by: Greg Holmes <greg@dmdirc.com>
Also make some things more groovy-y.
Change-Id: Iced4396b6a43f2548f0633f982edc63e7b978770
Reviewed-on: http://gerrit.dmdirc.com/4029
Reviewed-by: Greg Holmes <greg@dmdirc.com>
Automatic-Compile: DMDirc Build Manager
Define a 'plugin' function to use in place of 'project' that
will figure out where the plugin is living in the root gradle
project.
This allows the plugins to be included and built properly
when they are in a submodule of either the client or the meta
project.
Change-Id: Iacc3551ac9c0bf2343151eb9cf85296c85c5a28b
Reviewed-on: http://gerrit.dmdirc.com/4028
Automatic-Compile: DMDirc Build Manager
Reviewed-by: Greg Holmes <greg@dmdirc.com>
This copies licenses, identities, preferences, and anything else we add.
Change-Id: I7d78bfdce2ad2adf9c42db564366a30f55981c62
Reviewed-on: http://gerrit.dmdirc.com/4024
Reviewed-by: Chris Smith <chris@dmdirc.com>
Automatic-Compile: DMDirc Build Manager
Write the build environment to a list section of the plugin
meta-data. This should make it easier to figure out what
on earth is going on when everything breaks.
Change-Id: I317cd6795e81d56930b21b8d9beeabc28a0b775e
Reviewed-on: http://gerrit.dmdirc.com/4010
Reviewed-by: Greg Holmes <greg@dmdirc.com>
Automatic-Compile: DMDirc Build Manager
Feel like we've got a few too many moving parts at the moment,
so explicitly set versions of our dependencies.
Also took the opportunity to upgrade a couple of things.
Change-Id: I1af4dbfbbd149e5a4c64e83f66de015affcf4032
Reviewed-on: http://gerrit.dmdirc.com/4001
Automatic-Compile: DMDirc Build Manager
Reviewed-by: Greg Holmes <greg@dmdirc.com>
* Move all plugins to their own top-level directories.
* Move resources out of source trees
* Add Gradle build scripts.
* Remove ivy and ant build scripts.
Change-Id: Ib69a48ef26800c174ccf51c84ff9d1f73529460f
Depends-On: I303b6b69518468f98d48d835b8f40135d9e4bcbf
Reviewed-on: http://gerrit.dmdirc.com/3850
Automatic-Compile: DMDirc Build Manager
Reviewed-by: Greg Holmes <greg@dmdirc.com>
Shane Mc Cormack
