You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@deltaspike.apache.org by "John D. Ament (JIRA)" <ji...@apache.org> on 2015/01/19 11:26:34 UTC
[jira] [Commented] (DELTASPIKE-821) check compatibility with gradle
[ https://issues.apache.org/jira/browse/DELTASPIKE-821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14282357#comment-14282357 ]
John D. Ament commented on DELTASPIKE-821:
------------------------------------------
You're probably hitting the issue that came up in this thread, if i had to guess: http://mail-archives.apache.org/mod_mbox/deltaspike-users/201411.mbox/%3CCAJw%2B4NCecnWwE4GnMbHOc8zsFMt4uSeGpc%2BMg0G%2Be8q6pqBZcA%40mail.gmail.com%3E
Seems like in general gradle OOTB doesn't work well with CDI. Here's an example config I did in that thread to make the CDI archive known during a gradle build
{code}
sourceSets {
main {
//if you truly want to override the defaults:
output.resourcesDir = 'build/out'
output.classesDir = 'build/out'
}
}
{code}
probably you can swap main with test to get the appropriate behavior for tests.
> check compatibility with gradle
> -------------------------------
>
> Key: DELTASPIKE-821
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-821
> Project: DeltaSpike
> Issue Type: Task
> Components: TestControl
> Reporter: Mario-Leander Reimer
> Fix For: 1.2.2
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)