I was trying to look at my applications dependency tree and noticed that it
appears that wildcard expressions in exclusions do not get reflected in the
tree, is that the case or is there a special usage to have the
dependency:tree reflect these?
Thanks. I managed to figure this out. Sorry I didn't reply before.
On 01/15/2016 11:28 AM, Andreas Gudian wrote:
The clean way would be to skip the plugin execution using something like
this at the appropriate level in your pom / parent-pom hierarchy:
org.apache.ma
The clean way would be to skip the plugin execution using something like
this at the appropriate level in your pom / parent-pom hierarchy:
org.apache.maven.plugins
maven-javadoc-plugin
..
true
2016-01-14 23:38 GMT+01
On 01/14/2016 04:37 PM, e...@zusammenkunft.net wrote:
Hello,
Most likely the source directory is (incorrectly) overwritten at the compile
plugin (or it is compiled by the parent pom or some other strange mechanisms
like an ant plugin). The -X output (together with the effective pom) should
I was wrong, as I noted elsewhere. 2.18 good, 2.19.x bad.
On Thu, Jan 14, 2016 at 7:57 PM, Benson Margulies wrote:
> 2.19.1 is just as broken in these cases.
>
> On Tue, Jan 12, 2016 at 3:57 PM, Andreas Gudian
> wrote:
>> You might wanna try 2.19.1, where Tibor fixed a couple of issues regardin
I have a rather complex project using pax-exam that works fine with
2.18 and not with 2.19 or 2.19.1, contrary to some confused email I
sent the other day. Setting forkCount to 0 makes the immediate problem
go away, but messes up other things for me because of the different
working directory when r
I am out of the office until 01/18/2016.
Hello,
I am out of the office Friday Jan 15, returning Monday. Please contact
Erwin Mendoza for any urgent requests..
thx,
Warren
Note: This is an automated response to your message "Re: Filtering
resources" sent on 1/15/2016 1:55:54 AM.
This is th
