Hello,
my company develops applications for the SAP enterprise portal. Since SAP
has recently relased version 7.3 of its platform "NetWeaver", we now have
two different build paths:
dependencies: NetWeaver 7.0 libraries
output: a "portal archive", something like a zip file with a specific folder
structure inside
and
dependencies: NetWeaver 7.3 libraries
output: an EAR file
How do I map these two paths to a gradle project? I actually have three
solutions in mind:
a) define different configurations, for example compile70, runtime70 and
compile73, runtime70
b) drive the build with a command line parameter, e.g. gradle
-Dtargetrelease=73 build, and evaluate that property at the appropriate
positions, e.g. if targetrelease = '73' { apply plugin: 'ear' }
c) define rules (tasks.addRule) so that tasks like build<release> are
available
Are there other possibilities?
Is there a recommended way to approach this problem?
I would actually go for the approach a), since this would allow to build
both relases with one gradle run...
Best regards,
Björn
--
View this message in context:
http://gradle.1045684.n5.nabble.com/How-to-create-distributions-with-different-dependencies-and-different-outputs-tp4741969p4741969.html
Sent from the gradle-user mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
