Hi Karl Heinz! On 26 Nov 2014, Karl Heinz Marbaise wrote:
> Hi Martin, > > first can you create a project which reproduces the problem...otherwise > it's really hard to drill down the issue... I don't know if I can create such a project. I'll try and start with a simple project as described in my original post. We'll see if this suffices... > Furthermore have you defined the dependencies in your ear module which > should be skinnyfied... I just checked and I do have most of the dependencies listed in the EAR but some are missing. I'll fix this and see if this changes anything. > Does you ear module contain other dependencies which could have the jars > you don't like to have in your ear as a transitive dependency? Sorry, I don't get you. I want JARs *to be* in the EAR and no to "not be in the EAR". > Can you post your pom file ? Well, the actual project has more than 150 modules without the dependencies. I don't think posting the whole pom makes sense. I'll try to create a sample project instead (could take me some time). If you just want some m-ear-p configuration or the like, just let me know. I could of course post this. [...] > > I'd be happy to provide a sample project but I'm not sure how to > > provide this as it also seems to depend on the infrastructure. > > Hm...you say on one side it's a bug of maven-ear-plugin but here you say > different... ?... As changing the version of the m-ear-p is enough to fix the problem I really do think it's a bug in the ear plugin. But the bug only triggers in situations that depend on the infrastructure. Does this make more sens to you? - martin
signature.asc
Description: PGP signature
