[mojo-dev] [jira] (MLICENSE-106) Allow to filter dependencies by scope

Title: Message Title chris snow created an issue

[mojo-dev] [jira] (MANIMALSNIFFER-42) Fails to detect Java API generic type addition

Title: Message Title Kevin Condon created an issue

[mojo-dev] [jira] (MANIMALSNIFFER-42) Fails to detect Java API generic type addition

Title: Message Title Kevin Condon commented on an issue

[mojo-dev] [jira] (MCOBERTURA-188) Not supported following method call "this.test()"

Title: Message Title Eugene Gligalov commented on an issue

[mojo-dev] [jira] (MMOCKRM-13) downloading /favicon.ico throws an emptyStackException

Title: Message Title Robert Scholte created an issue

[mojo-dev] [jira] (MJAXB-90) schemagen prints "null" on screen and creates empty "schemagen" target folder

Title: Message Title Alejandro E commented on an issue

[mojo-dev] [jira] (MWEBSTART-203) Problem copying dependent jar files

Title: Message Title Rick Herrick updated an issue

Re: [mojo-dev] Re: [mojo-scm] [19715] trunk/mojo/flatten-maven-plugin/src/site/xdoc/usage.xml: MOJO-2027: added documentation

Hi there, I did not get any feedback yet. Meanwhile I refactored the Mojo and invented FlattenDescriptor that can be configured like this: KeepOrAdd KeepIfExists Remove ... I added all optional elements of the POM that make sense in this context. So far I added a first

Re[2]: [mojo-dev] Re: [mojo-scm] [19715] trunk/mojo/flatten-maven-plugin/src/site/xdoc/usage.xml: MOJO-2027: added documentation

Hello Jörg, I have two minor suggestions: 1. Rename flattenDescriptor to pomSections (or pomElements) 2. Start enumerated constants with a lower case letter, e.g. keepIfExists, so that they are consistent with other mojos' configuration The reason for the above is that I think it reads better th

[mojo-dev] [jira] (MVERSIONS-257) add includes/excludes to update-parent

Title: Message Title James Levinson created an issue