[JBoss JIRA] (WFLY-13433) Improve capability support in EJB3 subsystem
by Richard Achmatowicz (Jira)
[ https://issues.redhat.com/browse/WFLY-13433?page=com.atlassian.jira.plugi... ]
Richard Achmatowicz edited comment on WFLY-13433 at 7/20/20 9:58 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.
And is there a test plan for any of this stuff? Does anyone know which tests are being run or why?
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.
And is there a test plan for any of this stuff? Does anyone know which tests are being run?
> 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)
5 years, 12 months
[JBoss JIRA] (WFLY-13433) Improve capability support in EJB3 subsystem
by Richard Achmatowicz (Jira)
[ https://issues.redhat.com/browse/WFLY-13433?page=com.atlassian.jira.plugi... ]
Richard Achmatowicz edited comment on WFLY-13433 at 7/20/20 9:56 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.
And is there a test plan for any of this stuff? Does anyone know which tests are being run?
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)
5 years, 12 months
[JBoss JIRA] (WFLY-13575) Remove all hard coded references to Artemis default values
by Emmanuel Hugonnet (Jira)
[ https://issues.redhat.com/browse/WFLY-13575?page=com.atlassian.jira.plugi... ]
Emmanuel Hugonnet commented on WFLY-13575:
------------------------------------------
The test is there to detect configuration changes in artemis so that we may know about it and decide what to do.
> Remove all hard coded references to Artemis default values
> ----------------------------------------------------------
>
> Key: WFLY-13575
> URL: https://issues.redhat.com/browse/WFLY-13575
> Project: WildFly
> Issue Type: Enhancement
> Components: JMS
> Affects Versions: 20.0.0.Final
> Reporter: Emmanuel Hugonnet
> Assignee: Michal Petrov
> Priority: Major
>
> There are still attributes that use Artemis default configuration valuues from FileConfiguration for example.
> Remove those values so that they are not updated behind the scene and add a test to know when our default values don't align with Artemis ones.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 12 months
[JBoss JIRA] (WFLY-6597) IJ020017: Invalid archive deploying activemq-rar
by Tomasz Adamski (Jira)
[ https://issues.redhat.com/browse/WFLY-6597?page=com.atlassian.jira.plugin... ]
Tomasz Adamski commented on WFLY-6597:
--------------------------------------
My fix for that issue was merged to ActiveMQ so it should be solved after upgrading.
> IJ020017: Invalid archive deploying activemq-rar
> ------------------------------------------------
>
> Key: WFLY-6597
> URL: https://issues.redhat.com/browse/WFLY-6597
> Project: WildFly
> Issue Type: Bug
> Components: JCA
> Affects Versions: 10.0.0.Final
> Environment: CentOS 6
> Oracle Java 1.8.0_92-b14
> Wildfly 10.0.0.Final
> ActiveMQ RAR 5.13.3
> Reporter: Brett Delle Grazie
> Assignee: Tomasz Adamski
> Priority: Major
>
> Deploying ActiveMQ RAR via 'deploy' command:
> deploy /opt/activemq/activemq-rar-5.13.3.rar
> Results in the following log entry:
> 2016-05-09 08:07:20,788 WARN [org.jboss.as.connector.deployers.RADeployer] (MSC service thread 1-1) IJ020017: Invalid archive: file:/tmp/wildfly/vfs/temp/temp3cb3b15524db2617/content-d69689ded82e9101/contents/
> repeated slightly later:
> 2016-05-09 08:07:20,983 WARN [org.jboss.as.connector.deployers.RaXmlDeployer] (MSC service thread 1-1) IJ020017: Invalid archive: file:/tmp/wildfly/vfs/temp/temp3cb3b15524db2617/content-d69689ded82e9101/contents/
> However deployment is successful
> Note that if a runtime-name is provided the RAR is *not* registered correctly.
> See also previous issue raised WFLY-4431 (minimal info)
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 12 months
[JBoss JIRA] (WFLY-13433) Improve capability support in EJB3 subsystem
by Richard Achmatowicz (Jira)
[ https://issues.redhat.com/browse/WFLY-13433?page=com.atlassian.jira.plugi... ]
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)
5 years, 12 months
[JBoss JIRA] (WFLY-13433) Improve capability support in EJB3 subsystem
by Richard Achmatowicz (Jira)
[ https://issues.redhat.com/browse/WFLY-13433?page=com.atlassian.jira.plugi... ]
Richard Achmatowicz edited comment on WFLY-13433 at 7/20/20 8:52 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)
5 years, 12 months
[JBoss JIRA] (WFLY-13433) Improve capability support in EJB3 subsystem
by Richard Achmatowicz (Jira)
[ https://issues.redhat.com/browse/WFLY-13433?page=com.atlassian.jira.plugi... ]
Richard Achmatowicz edited comment on WFLY-13433 at 7/20/20 8:50 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, which is another setup step.
> 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)
5 years, 12 months
[JBoss JIRA] (WFLY-13433) Improve capability support in EJB3 subsystem
by Richard Achmatowicz (Jira)
[ https://issues.redhat.com/browse/WFLY-13433?page=com.atlassian.jira.plugi... ]
Richard Achmatowicz edited comment on WFLY-13433 at 7/20/20 8:40 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, which is another setup step.
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.
> 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)
5 years, 12 months
[JBoss JIRA] (WFLY-13433) Improve capability support in EJB3 subsystem
by Richard Achmatowicz (Jira)
[ https://issues.redhat.com/browse/WFLY-13433?page=com.atlassian.jira.plugi... ]
Richard Achmatowicz edited comment on WFLY-13433 at 7/20/20 8:26 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.
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. Just more wasted time.
> 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)
5 years, 12 months