Sure, I guess I could file a ticket. Just checking why you can't do it yourself? I'm thinking that as you know the issue it would be than me being a proxy. I don't have any extra privs in the Kenai JIRA that I know of.
/Anders On Wed, Jan 14, 2015 at 7:58 PM, Lennart Jörelid <lennart.jore...@gmail.com> wrote: > Hello all, > > I'm getting my fair share of finding odd behaviour with the JAXB tools. > Refer to the SchemaGen odd ByteCode generation > <https://jira.codehaus.org/browse/MJAXB-113> problem described in our > JIRA. > > Fow now, I'll simply delete the schemagen-generated bytecode files from > the generated-resources (and generated-test-resources) directories > respectively, implying that the schemagen goal does not create an extra > suite of compiled bytecode in addition to the standard compiled bytecode. > > *Anders:* I wonder if you could create an issue in the Kenai JIRA for > creation of a new schemagen option ("-dontWriteBytecodeToOutputDir" or > similar) which would prevent schemagen from emitting the generated bytecode > to the "-d" directory where it dumps XSDs. > > -- > > -- > +==============================+ > | Bästa hälsningar, > | [sw. "Best regards"] > | > | Lennart Jörelid > | EAI Architect & Integrator > | > | jGuru Europe AB > | Mölnlycke - Kista > | > | Email: l...@jguru.se > | URL: www.jguru.se > | Phone > | (skype): jgurueurope > | (intl): +46 708 507 603 > | (domestic): 0708 - 507 603 > +==============================+ > >
