[
https://issues.apache.org/jira/browse/DELTASPIKE-215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13405781#comment-13405781
]
Mark Struberg commented on DELTASPIKE-215:
------------------------------------------
currently doing exactly that :) just fiddling around with the details. Do we
like to pickup JNDI automatically as well, etc?
I'm also thinking about unifying META-INF/apache-deltaspike.properties vs
java:/comp/env/deltaspike/[key]. either 'apache-deltaspike' or 'deltaspike'.
> Add a new annotation to override the location of the
> apache-deltaspike.properties file
> --------------------------------------------------------------------------------------
>
> Key: DELTASPIKE-215
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-215
> Project: DeltaSpike
> Issue Type: New Feature
> Reporter: Charles Moulliard
>
> I don't see a property (or annotation) that we can use to override the name
> to be used to load the properties file
> (META-INF/apache-deltaspike.properties) and its location like we can do with
> Spring (@ContextConfiguration(locations = { "classpath:mycontext.xml" })).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
