|
||||||||
|
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-71) Ensure no exception whe... Anders Hammar (JIRA)
- [mojo-dev] [jira] (MJAXB-71) Ensure no exception whe... Robert Scholte (JIRA)
- [mojo-dev] [jira] (MJAXB-71) Ensure no exception whe... JIRA
- [mojo-dev] [jira] (MJAXB-71) Ensure no exception whe... JIRA
- [mojo-dev] [jira] (MJAXB-71) Ensure no exception whe... Anders Hammar (JIRA)
- [mojo-dev] [jira] (MJAXB-71) Ensure no exception whe... Robert Scholte (JIRA)
- [mojo-dev] [jira] (MJAXB-71) Ensure no exception whe... Anders Hammar (JIRA)
- [mojo-dev] [jira] (MJAXB-71) Ensure no exception whe... Robert Scholte (JIRA)
- [mojo-dev] [jira] (MJAXB-71) Ensure no exception whe... JIRA
- [mojo-dev] [jira] (MJAXB-71) Ensure no exception whe... Anders Hammar (JIRA)
- [mojo-dev] [jira] (MJAXB-71) Ensure no exception whe... Anders Hammar (JIRA)

After doing some thinking, this is my call on this ticket:
We keep the implemented behavior where non-existing source folders are ignored with an INFO log statement. I've studied how the m-resources-p handles non-exisiting resources folders (actually how maven-filtering does this) and it is the same behavior. I simply don't think misconfiguration etc is a problem. If they have something misconfigured, the should see the log output or their tests should catch this.
Adding an extra config parameter for this is not a good idea I think, we don't need more parameters and more options.
Should this turn out to be a bad call, we could always change it in the future. If it is a problem people will file tickets. However, as the m-resources-p has a similar behavior I don't think this will be a problem.