Thanks, that worked. It appears that any changes I make using the deploymentDescriptor closure are merged in with the automatically generated application.xml. I'd rather completely replace the automatically generated application.xml, is there an easy way to do this? I put my own application.xml file at src/main/META-INF/application.xml but it does not get included when I generate a ear file.
On 7/7/11, David Gileadi <[email protected]> wrote: > On 7/7/11 11:38 AM, Jared Stofflett wrote: >> I’m trying to view a list of modules Gradle will add to the deployment >> descriptor for an ear file during my build. When I access the >> deploymentDescriptor property in my build file though it appears I >> always get a blank deployment descriptor. How can I access the >> deployment descriptor Gradle will add to my generated ear? I’ve pasted >> a sample build file below. When I call println descriptor.getModules() >> I get an empty array. >> >> apply plugin: 'ear' >> >> repositories { >> mavenRepo urls: "http://urltoourcorporitmirror"; >> } >> dependencies { >> deploy project(':Project1') >> deploy project(':Project2Client') >> } >> println deploymentDescriptor.getModules() > > The modules to deploy are only added after all dependencies have been > resolved. As you've discovered, during the configuration phase of the > build this list isn't available. > > This means that unfortunately I don't know of a way to print out the > list of deployed modules until after the ear has been created. You > might try printing them after the fact using .doLast {} on the ear task. > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
