Russel Winder wrote:
>
> The parameterization problem is of the jar{ manifest { . . . } } section
> in each of the project specifications.
>
Here is one way to factor out the commonalities:
subprojects {
...
jar.doFirst { // delay configuration until execution phase to make sure
manifestName and manifestTitle have been set
manifest {
...
name = manifestName
symbolicName = manifestName
instruction 'Extension-Name', manifestName
instruction 'Specification-Title' , manifestTitle
instruction 'Implementation-Title' , manifestTitle
}
}
}
project ( ':jsr166' ) {
...
manifestName = 'jsr166'
manifestTitle = 'JSR166'
}
project ( ':jsr166tck' ) {
...
manifestName = 'jsr166tck'
manifestTitle = 'JSR166 TCK'
}
...
--
Peter Niederwieser
Developer, Gradle
http://www.gradle.org
Trainer & Consultant, Gradle Inc.
http://www.gradle.biz
Creator, Spock Framework
http://spockframework.org
--
View this message in context:
http://gradle.1045684.n5.nabble.com/OSGi-fying-a-multiproject-build-tp3402033p3404173.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
