The ear plugin bug is not fixed since 2011?


(Seto) #1

I’m trying to use the ear plugin with war. This is the instruction.

dependencies {
// The following dependencies will be the ear modules and
// will be placed in the ear root
deploy project(’:war’)

// The following dependencies will become ear libs and will
// be placed in a dir configured via the libDirName property
// earlib group: 'log4j', name: 'log4j'

}

But instead, I have to use this from the threads in the forum.

deploy project(path:’:war’,configuration:‘archives’)


(Stefan Oehme) #2

Could you please provide a reproducible example project or point me to the bug report? :slight_smile:


(Seto) #3


Here’s the discussion for the bug. There’s a workaround.
https://issues.gradle.org/browse/GRADLE-1912
And here’s the bug reporting 5 years ago. And it’s never fixed.


(Stefan Oehme) #4

Thank you for the pointer Seto! This is unfortunately not easy to fix. It will require usage-aware dependency resolution, so we can tell apart the case “I want to compile against this project” from “I want to package this project for deployment”.

I’ve corrected the user guide to use the workaround discussed in the bug report.


(Seto) #5

Where did you update the user guide? I found it’s not fixed yet. Or does it apply to the next version user guide?


(Stefan Oehme) #6

The updated user guide will be part of the Gradle 3.1 release.


(Seto) #7

Hi. I found the example in 3.1 doc is still “deploy project(’:war’)”. Or do I miss something?


(Stefan Oehme) #8

Thanks for the heads-up! I had missed that second sample project and only changed the first one. Fixed for 3.2.