[
https://issues.apache.org/jira/browse/DELTASPIKE-130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13239314#comment-13239314
]
Mark Struberg commented on DELTASPIKE-130:
------------------------------------------
I've now took a deep look into our impl again and I think I know where the
misunderstanding comes from (as I fell into the same hole).
There must be only 1 CDI producer for our ProjectStage. It doesn't make sense
to provide a 'custom' CDI producer for the ProjectStage.
But it might make sense to provide a way to configure the SOURCE of the
ProjectStage, means the mechanism which does the ProjectStage calculation. I'd
just split this part out and move it to a separate class. Or we just document
this stuff better.
I agree that in 98% of all cases we do not need this (but still might be handy).
> Remove custom ProjectStageProducer logic
> ----------------------------------------
>
> Key: DELTASPIKE-130
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-130
> Project: DeltaSpike
> Issue Type: Improvement
> Components: Core
> Affects Versions: 0.1-incubating
> Reporter: Jason Porter
> Assignee: Gerhard Petracek
> Priority: Minor
> Fix For: 0.2-incubating
>
>
> Right now we have the ability to register a custom ProjectStageProducer which
> then overrides the default one in DeltaSpike. I don't think this is really
> necessary and our default ProjectStageProducer should be able to pick up any
> custom stages and use them accordingly. The extra configuration is cool, but
> I think at the end of the day it's not necessary.
--
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
