Issue 11 in maven-overview-plugin: plugin configuration <excludes> does not exclude

[codesite...@google.com]

Comment #2 on issue 11 by hubert.iwaniuk: plugin configuration <excludes>
does not exclude
http://code.google.com/p/maven-overview-plugin/issues/detail?id=11

Excludes works but I'm going to rebuild it now.
So it is going to be much more intuitive in use.

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

[codesite...@google.com]

Updates:
Blockedon: 13

Comment #3 on issue 11 by hubert.iwaniuk: plugin configuration <excludes>

does not exclude
http://code.google.com/p/maven-overview-plugin/issues/detail?id=11

(No comment was entered for this change.)

[codesite...@google.com]

Comment #4 on issue 11 by jens.gas...@gmx.de: plugin configuration

<excludes> does not exclude
http://code.google.com/p/maven-overview-plugin/issues/detail?id=11

We changed the focus of our project using the overview plugin. A sample
pom.xml
couldn't be provided. I suggest to close this issue. If we happen to have
difficulties again we can reopen a "bug".

[codesite...@google.com]

Comment #5 on issue 11 by hubert.iwaniuk: plugin configuration <excludes>

does not exclude
http://code.google.com/p/maven-overview-plugin/issues/detail?id=11

Hi Jens,

I still think that having exclusions with syntax as close as possible to
one provided
by Maven dependency would be a lot friendlier for users.
And exclusions are not working if you provide inclusions this needs to be
fixed.
I think that artifacts should end-up in graph if artifact in inclusions and
not
artifact not in exclusion. That seems intuitive, would you agree?

Also if you would like to have a graph of runtime and compile scope, for
now you
would have to do a lot of manual labor (see Issue 13).

Thanks for your feedback,
Hubert.