[
http://jira.jboss.com/jira/browse/JBESB-573?page=comments#action_12362844 ]
Kurt Stam commented on JBESB-573:
---------------------------------
I actually allready was using a patched verion to get rid of code warnings :). So you may
want to apply that fix too:
https://issues.apache.org/jira/browse/XMLBEANS-309
We're using xmlbeans b/c scout uses it too. I'm currently working on converting it
over to JAXB. JBossAS is using JAXB too. So maybe this is a good point to generate the
bindings using JAXB. It generates much cleaner java, and java 6 h as it build in.
Tidy up javadocs warnings in build
----------------------------------
Key: JBESB-573
URL:
http://jira.jboss.com/jira/browse/JBESB-573
Project: JBoss ESB
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Documentation
Reporter: Daniel Bevenius
Assigned To: Daniel Bevenius
Priority: Trivial
The current ant target javadoc generetes serveral hundred warnings. Most of them are due
to a minor bug in xmlbean (
https://issues.apache.org/jira/browse/XMLBEANS-170 )
These warnings makes it difficult to spot the ones that the ESB project generates. I have
corrected the warnings in my workspace and would like to check them into the main branch.
It would be nice if we could "patch" the xmlbeans version to get rid the rest
of the warnings. I tried this locally and the "fix" looks harmless enough. Let
me know if this is something we would like to do.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira