[
https://issues.apache.org/jira/browse/DELTASPIKE-1175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15331940#comment-15331940
]
Matej Novotny commented on DELTASPIKE-1175:
-------------------------------------------
It cannot even detect Weld profiles because the parent of {{cdictrl}} is
{{parent}} ({{../parent/pom.xml}}) and Weld profiles are defined in
{{parent-code}} ({{../parent/code/pom.xml}}).
Besides {{cdictrl}} defines its own profile named {{Weld}}.
I suppose altering the parent to {{parent-code}} would give access to those
profiles and then you could extend those profiles by adding adequate
{{<module>}} subsections?
> Weld(1|2|3) profiles do not activate Weld profile in cdictrl
> ------------------------------------------------------------
>
> Key: DELTASPIKE-1175
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1175
> Project: DeltaSpike
> Issue Type: Bug
> Components: CdiControl
> Affects Versions: 1.7.0
> Reporter: John D. Ament
>
> If you run the build with {{mvn clean install -PWeld1
> -Dweld.version=1.1.28.Final}} you'll see the OWB container control module get
> built. It should build the Weld module. To get it to activate properly you
> need to do {{mvn clean install -PWeld -PWeld1 -Dweld.version=1.1.28.Final}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
