|
||||||||
|
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)

Well, first of all no plugin I know of that generates stuff mark these are read-only. So why should this plugin? Also, some OS will likely have problems cleaning (mvn clean) if the files are read-only.![]()
Maven users should now that stuff in the output target folder (which is where generated files should go) is not to be modified as they will be re-generated. If not, he/she will learn the hard way and then know it.