Databases
StackOverflow2013
Postsdbo
POGradle - when is a plug-in preferable over a script?
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POGradle - when is a plug-in preferable over a script?
    text
    copied!<p>I'm using gradle to manage a multi-project J2EE build - the end-goal is to produces a series of server package/artifacts that can be deployed to a target server, unzipped, and run. </p> <p>In other words, each artifact contains everything it needs to run - minus the JDK. </p> <p>The project structure looks somewhat like so:</p> <pre><code>Root project 'proto' - This is the master-build project +--- Project ':applications' - Default build settings for applications | +--- Project ':applications:foo' - Foo API | +--- Project ':applications:bar' - Bar API | \--- Project ':applications:baz' - Baz API +--- Project ':common' - Common code shared by multiple projects | \--- Project ':common:subcomponents' - Settings shared by subcomponents | +--- Project ':common:subcomponents:configuration' - Configuration | \--- Project ':common:subcomponents:initializer' - Initializers +--- Project ':servers' - Default tasks for building server artifacts | +--- Project ':servers:foobar' - Assembles and runs the foobar server | +--- Project ':servers:foobaz' - Assembles and runs the foobaz server | \--- Project ':servers:barbaz' - Assembles and runs the barbaz server \--- Project ':webapps' - These are the defaults for webapps +--- Project ':webapps:foo' - The webapp for foo +--- Project ':webapps:bar' - The webapp for bar \--- Project ':webapps:baz' - The webapp for baz </code></pre> <p>Building common, apps and webapps as dependencies of each other is pretty straight-forward but building the servers projects have proven to be somewhat of a challenge. </p> <p>My current approach is to use a bare-bones server in the "servers" folder and copy it's contents over to the taget server being built, then copy war files to it and zip it all up... but my root/servers/build.gradle is starting to look a mess.</p> <p>So the question is -- would writing an 'ear' style plug-in help simplify my server builds? </p> <p>Also of note, I'm currently using resin-pro-3.0.25 but planning on switching to another server container soon (next couple of months), which brings me to a tangent question - are other folks using similar approaches when building server artifacts for tomcat / jetty?</p> <p>Your thoughts are greatly appreciated! </p>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload