[mojo-dev] [jira] (MWAGON-23) Array index out of bounds trying to use merge on a jenkins repository

Title: Message Title Benson Margulies assigned an issue to Unassigned

[mojo-dev] [jira] (MJAXB-113) Remove the generated bytecode files from SchemaGen when sources exist in normal compile scope

Title: Message Title Lennart Jörelid edited a comment on an issue

[mojo-dev] Best practises for manipulating the JUL Logger in a Plugin

Hello all, I'm in the final phase of revamping the Jaxb2-Maven-Plugin, and have encountered a (presumably) common problem. The plugin delegates most of its work to the JDK-distributed tools XJC and SchemaGen. These two tools use JUL for logging; and their respective outputs should be emitted onto

Re: [mojo-dev] Best practises for manipulating the JUL Logger in a Plugin

Should you really be using the JVM of maven to run these tools? I would argue no. You should be forking the toolchains specified JVM and using that forked JVM to do the work. If you do it that way you can completely control what logging those forked JVMs uses and route it to the Maven logger of ch

Re: [mojo-dev] Best practises for manipulating the JUL Logger in a Plugin

If I understand things correctly, it doesnt really matter Stephen. Maven plugins (at least the 2.2.1 API; I will take a look at upgrading the jaxb2-maven-plugin WRT the required maven version, but for this release we still support JDK 1.6/Maven 2.2.1) use the Maven Log framework, whereas XJC/Schem

[mojo-dev] [jira] (MCOBERTURA-195) Cobertura causing test failures and maven reports the build as success

Title: Message Title Alex O commented on an issue