headers
Anders Hammar (JIRA | 3 Aug 2012 21:40

[jira] (MJAXB-70) Deprecate the readOnly option
Issue Type: Improvement
Affects Versions: 1.4
Assignee: Unassigned
Created: 03/Aug/12 2:39 PM
Description:

The plugin supports generating files that are in read-only mode. This doesn't really make sense in a Maven project and isn't (IMHO) best practice in any way. Also, having read-only files in the target folder (where the generated sources should be) would cause "mvn clean" to fail.
Thus, the readOnly option should be deprecated. It should still be supported for backwards compatibility, but users would be recommended not to use it.
Environment: n/a
Project: JAXB-2 Maven Plugin
Priority: Major
Reporter: Anders Hammar
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
--------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
Permalink | Reply |
headers
Anders Hammar (JIRA | 15 Aug 2012 11:07

[jira] (MJAXB-70) Deprecate the readOnly option
Change By: Anders Hammar (15/Aug/12 4:06 AM)
Fix Version/s: 1.5
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
--------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
Permalink | Reply |
headers
Anders Hammar (JIRA | 15 Aug 2012 16:21

[jira] (MJAXB-70) Deprecate the readOnly option
Change By: Anders Hammar (15/Aug/12 9:19 AM)
Assignee: Anders Hammar
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
--------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
Permalink | Reply |
headers
Anders Hammar (JIRA | 15 Aug 2012 16:23

[jira] (MJAXB-70) Deprecate the readOnly option

Anders Hammar closed MJAXB-70 as Fixed

Fixed in r17319
Change By: Anders Hammar (15/Aug/12 9:22 AM)
Resolution: Fixed
Status: Open Closed
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
--------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
Permalink | Reply |
headers
Carlin Scott (JIRA | 21 Dec 2012 20:19

[jira] (MJAXB-70) Deprecate the readOnly option

Carlin Scott commented on MJAXB-70

Generating source files which shouldn't be modified without the read-only attribute doesn't make sense to me. What's the alternative solution to preventing developers from accidentally modifying generated source files?
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
--------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
Permalink | Reply |
headers
Anders Hammar (JIRA | 23 Dec 2012 22:55

[jira] (MJAXB-70) Deprecate the readOnly option

Anders Hammar commented on MJAXB-70

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.

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
--------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
Permalink | Reply |
headers
Carlin Scott (JIRA | 27 Dec 2012 01:39

[jira] (MJAXB-70) Deprecate the readOnly option

Carlin Scott commented on MJAXB-70

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.
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
--------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
Permalink | Reply |

Gmane