[jboss-jira] [JBoss JIRA] (WFLY-13433) Improve capability support in EJB3 subsystem

[Richard Achmatowicz (Jira)]

    [ https://issues.redhat.com/browse/WFLY-13433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14261002#comment-14261002 ] 

Richard Achmatowicz edited comment on WFLY-13433 at 7/20/20 8:54 AM:
---------------------------------------------------------------------

Thanks for the tip. Its frustrating to have to kill yourself debugging the allTests target locally to then find there are a lot of other tests that get run as well in the CI besides allTests.  The tests that are now failing for me, mixed-domain, don't even have a shorthand listed in integration-tests.sh nor any entry in the online docs. Just more wasted time.

It looks like they are enabled by specifying a directory:
{noformat}
 <profile>
    <id>mixed-domain.module.profile</id>
    <activation><property><name>jboss.test.mixed.domain.dir</name></property></activation>
    <modules>
        <module>mixed-domain</module>
    </modules>
</profile>
{noformat}
and you have to place legacy versions in that directory, according to the documentation in the mixed-domain module itself. So which legacy versions are placed in there for the CI and why are they placed there for the CI?

I think we could use a bit more clarity on *which* tests we run in the CI and *why* we are running them and how to reproduce them locally. 


was (Author: rachmato):
Thanks for the tip. Its frustrating to have to kill yourself debugging the allTests target locally to then find there are a lot of other tests that get run as well in the CI besides allTests.  The tests that are now failing for me, mixed-domain, don't even have a shorthand listed in integration-tests.sh nor any entry in the online docs. Just more wasted time.

It looks like they are enabled by specifying a directory:
{noformat}
 <profile>
    <id>mixed-domain.module.profile</id>
    <activation><property><name>jboss.test.mixed.domain.dir</name></property></activation>
    <modules>
        <module>mixed-domain</module>
    </modules>
</profile>
{noformat}
and you have to place legacy versions in that directory, according to the documentation in the mixed-domain module itself. So which legacy versions are placed in there for the CI and why are they placed there for the CI?

I think we could use a bit more clarity on *which* tests we run in the CI and *why* we are running them and how to reproduce them locally. 

> Improve capability support in EJB3 subsystem
> --------------------------------------------
>
>                 Key: WFLY-13433
>                 URL: https://issues.redhat.com/browse/WFLY-13433
>             Project: WildFly
>          Issue Type: Enhancement
>          Components: EJB
>    Affects Versions: 20.0.0.Beta1
>            Reporter: Richard Achmatowicz
>            Assignee: Richard Achmatowicz
>            Priority: Major
>
> Survey all external subsystem dependencies and introduce capability based dependencies where required.



--
This message was sent by Atlassian Jira
(v7.13.8#713008)