|
||||||||
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
- [mojo-dev] [jira] (MCOBERTURA-179) JAXB and XmlPars... Steve Storey (JIRA)
- [mojo-dev] [jira] (MCOBERTURA-179) JAXB and Xm... JIRA
- [mojo-dev] [jira] (MCOBERTURA-179) JAXB and Xm... JIRA
- [mojo-dev] [jira] (MCOBERTURA-179) JAXB and Xm... JIRA
- [mojo-dev] [jira] (MCOBERTURA-179) JAXB and Xm... Steven Christou (JIRA)
- [mojo-dev] [jira] (MCOBERTURA-179) JAXB and Xm... JIRA
- [mojo-dev] [jira] (MCOBERTURA-179) JAXB and Xm... JIRA
- [mojo-dev] [jira] (MCOBERTURA-179) JAXB and Xm... JIRA
- [mojo-dev] [jira] (MCOBERTURA-179) JAXB and Xm... JIRA
- [mojo-dev] [jira] (MCOBERTURA-179) JAXB and Xm... JIRA
I agree, and I thought it was kinda strange to rename the Main classes. While I can understand the usability and point of not having them all be called "Main", I do believe we should re-introduce some shadow classes (essentially bouncing the call from one public static void main(String[] args) to another (in order to preserve compatibility).
The change seems to have been done in the
commit a few months ago.
Meanwhile, I have started experimenting with a slightly different implementation to the Cobertura-Maven-Plugin which copes with the change in Main class name, and adapts itself to the newest version available. I'll show you in a week or two when I feel decently complete with the test.