[
https://issues.apache.org/jira/browse/DELTASPIKE-750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14301213#comment-14301213
]
Gerhard Petracek commented on DELTASPIKE-750:
---------------------------------------------
dep. on the perspective - that interface was just broken before that change,
because there was no way to express it and it just failed silently.
-1 for an annotation or a 2nd interface, because that way it's consistent with
other interfaces we have and we clearly did a jump in the version-number. if we
need to ensure binary compatibility across minor versions, we need to create
major releases in case of such trivial api-changes to avoid a messy api and we
need to setup e.g. clirr.
> No error message if the filename provided PropertyFileConfig implementation
> isn't found.
> ----------------------------------------------------------------------------------------
>
> Key: DELTASPIKE-750
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-750
> Project: DeltaSpike
> Issue Type: Bug
> Components: Configuration
> Affects Versions: 1.0.3
> Reporter: Corey Puffalt
> Assignee: Gerhard Petracek
> Fix For: 1.2.0
>
>
> As per summary, I have a simple PropertyFileConfig implementation class
> providing a configuration filename for the configuration module to pick up,
> but I've been frustrated by the lack of error handling because it just
> quietly ignores invalid/missing filenames instead of providing an error
> message.
> Ideally, an issue like this would prevent bootstrapping and fail-fast with a
> relevant error message.
> I'm not familiar enough with the code base to be sure but it looks to me like
> this should be fixed in PropertyFileUtils.resolvePropertyFiles() which
> should throw a FileNotFoundException if it doesn't find the given file on the
> classpath?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
