Re: rewrite StatelessXmlReporter fo JAXB

2017-04-17 Thread Tibor Digana
memory usage. > > >>>> > > >>>> Michael > > >>>> > > >>>> BTW: this should go to dev@ > > >>>> > > >>>> [1] https://github.com/highsource/maven-jaxb2-plugin > > >>>> >

Re: rewrite StatelessXmlReporter fo JAXB

2017-04-17 Thread Andreas Gudian
t; [1] https://github.com/highsource/maven-jaxb2-plugin > >>>> > >>>> ------------- > >>>> To unsubscribe, e-mail: [hidden email] > >>>> <http:///u

Re: rewrite StatelessXmlReporter fo JAXB

2017-04-16 Thread Michael Osipov
b.template.NodeNamesp ace&breadcrumbs=notify_subscribers%21nabble%3Aemail. naml-instant_emails%21nabble%3Aemail.naml-send_instant_ email%21nabble%3Aemail.naml> -- View this message in context: http://maven.40175.n5.nabble.c om/Re-rewrite-StatelessXmlRepo

Re: rewrite StatelessXmlReporter fo JAXB

2017-04-16 Thread Tibor Digana
175.n5.nabble.com/Re-rewrite-StatelessXmlRepo >>> rter-fo-JAXB- >>> tp5906482.html >>> To start a new topic under Maven Developers, email >>> ml-node+s40175n142166...@n5.nabble.com >>> To unsubscribe from Maven Developers, click here >>> <http:/

Re: rewrite StatelessXmlReporter fo JAXB

2017-04-16 Thread Michael Osipov
d to the discussion below: http://maven.40175.n5.nabble.com/Re-rewrite-StatelessXmlReporter-fo-JAXB- tp5906482.html To start a new topic under Maven Developers, email ml-node+s40175n142166...@n5.nabble.com To unsubscribe from Maven Developers, click here <http://maven.40175.n5.nabble.com/templ

Re: rewrite StatelessXmlReporter fo JAXB

2017-04-16 Thread Tibor Digana
source/maven-jaxb2-plugin > > - > To unsubscribe, e-mail: [hidden email] > <http:///user/SendEmail.jtp?type=node&node=5906482&i=0> > For additional commands, e-mail: [hidden email] > <http:///user/SendEma

Re: rewrite StatelessXmlReporter fo JAXB

2017-04-16 Thread Michael Osipov
Am 2017-04-16 um 14:21 schrieb Tibor Digana: Hi, I want to first talk with you about XML marshaller StatelessXmlReporter [1] in Surefire which is built on the top of SharedUtils' PrettyPrintXMLWriter. I found out issues after a contributor opened this issue [2]. The problem is that we are usin