[
https://issues.apache.org/jira/browse/DELTASPIKE-215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13406372#comment-13406372
]
Romain Manni-Bucau commented on DELTASPIKE-215:
-----------------------------------------------
What about scanning? DS seems to become a container light and the
deltaspike.properties could get a scanning = some packages and this way the
conf could simply be scanned (i know that's not CDi compliant but since we
can't use CDI to get such information for extension that's maybe a good
compromise answering both cases).
> 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
> Assignee: Mark Struberg
> Attachments: DELTASPIKE-215-interface.patch
>
>
> 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
