|
||||||||
|
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] (MJAXB-70) Deprecate the readOnly o... Anders Hammar (JIRA)
- [mojo-dev] [jira] (MJAXB-70) Deprecate the readO... Anders Hammar (JIRA)
- [mojo-dev] [jira] (MJAXB-70) Deprecate the readO... Anders Hammar (JIRA)
- [mojo-dev] [jira] (MJAXB-70) Deprecate the readO... Anders Hammar (JIRA)
- [mojo-dev] [jira] (MJAXB-70) Deprecate the readO... Carlin Scott (JIRA)
- [mojo-dev] [jira] (MJAXB-70) Deprecate the readO... Anders Hammar (JIRA)
- [mojo-dev] [jira] (MJAXB-70) Deprecate the readO... Carlin Scott (JIRA)

The person who set up jaxb2 for my group had it output to our src folder instead of generated-sources since we're using eclipse. After reading your comment I decided to do some research and found this solution for eclipse integration on StackOverflow to get eclipse to recognize source files in generated-sources. What's really nice about this solution is that the source folder inherits the "derived" attribute from the target folder so eclipse now warns people about modifying any of the generated sources.
You were quite right about "mvn clean" not liking the read-only attribute.