[JBoss JIRA] (DROOLS-3944) DMN Editor: Data type usability study
by Elizabeth Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3944?page=com.atlassian.jira.plugi... ]
Elizabeth Clayton updated DROOLS-3944:
--------------------------------------
Sprint: 2019 Week 23-25
> DMN Editor: Data type usability study
> -------------------------------------
>
> Key: DROOLS-3944
> URL: https://issues.jboss.org/browse/DROOLS-3944
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Environment: Version 7.4
> Reporter: Elizabeth Clayton
> Assignee: Sarahjane Clark
> Priority: Major
> Labels: UX, UXTeam, Usability, drools-tools
>
> Lightweight usability study to test the ease of use in viewing, creating, editing and deleting data types, particularly structured data types.
> GOALS: Access the Data Type editor in terms of productivity and usability.
> * Ease of use when creating a complex type (concern: minimizing the mouse usage.)
> * Ease of use when saving a basic data type (e.g. age: number)
> * Discoverability of actions in the kebab menu, especially, insert nested, delete.
> * Ease of use/accuracy: Type-ahead of the data type selector.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
1 month, 3 weeks
[JBoss JIRA] (WFLY-12461) Can't use smallrye-health without weld extension
by Florian Sailer (Jira)
Florian Sailer created WFLY-12461:
-------------------------------------
Summary: Can't use smallrye-health without weld extension
Key: WFLY-12461
URL: https://issues.jboss.org/browse/WFLY-12461
Project: WildFly
Issue Type: Bug
Components: MP Health
Affects Versions: 17.0.1.Final
Reporter: Florian Sailer
Assignee: Jeff Mesnil
Since this commit in the smallrye implementation it was possible to use smallrye without CDI.
https://github.com/smallrye/smallrye-health/commit/a6a7812877d74d2c3f5b29...
I'm trying to migrate from Wildfly 15.0.1-Final to 17.0.1-Final, where the smallrye-health extension unfortunately needs weld to startup. It's not possbible for me to activate weld on my sever, because there are some problems using the org.apache.cxf.jaxrs framework with weld.
I am getting the following exception while starting:
14:16:04,960 ERROR [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0362: Capabilities required by resource '/subsystem=microprofile-health-smallrye' are not available:
org.wildfly.weld; There are no known registration points which can provide this capability.
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
1 year, 8 months
[JBoss JIRA] (SWSQE-1039) Fix publish_jenkins_console.py
by Filip Brychta (Jira)
[ https://issues.redhat.com/browse/SWSQE-1039?page=com.atlassian.jira.plugi... ]
Filip Brychta updated SWSQE-1039:
---------------------------------
Sprint: Kiali Sprint #30, Kiali Sprint #32 (was: Kiali Sprint #30)
> Fix publish_jenkins_console.py
> ------------------------------
>
> Key: SWSQE-1039
> URL: https://issues.redhat.com/browse/SWSQE-1039
> Project: Kiali QE
> Issue Type: QE Task
> Reporter: Filip Brychta
> Assignee: Filip Brychta
> Priority: Major
> Labels: infrastructure
>
> Job Filter pattern: "[\w-]+ #\d+"
> Output Filter pattern: ""
> Jenkins Version: 2.190.2
> OrderedDict([('python-ui-test-pr', set([472])), ('upstream-pipeline', set([544])), ('build-kiali', set([871])), ('install-maistra', set([1377])), ('clean-environment', set([3240, 3241, 3242, 3239])), ('istio-kiali-mesh-checker', set([1864, 1865, 1866])), ('install-bookinfo', set([1619, 1620])), ('install-kiali-test-mesh-operator', set([881])), ('run-kiali-ui-tests-parallel', set([454])), ('run-kiali-ui-tests', set([7630, 7631, 7632, 7633, 7634, 7635, 7636, 7637, 7638, 7639, 7640, 7641, 7642, 7643, 7644, 7645, 7646]))])
> {'run-kiali-ui-tests-parallel': 'UNSTABLE', 'python-ui-test-pr': 'UNSTABLE', 'build-kiali': 'SUCCESS', 'istio-kiali-mesh-checker': 'SUCCESS', 'upstream-pipeline': 'UNSTABLE', 'clean-environment': 'SUCCESS', 'run-kiali-ui-tests': 'UNSTABLE', 'install-bookinfo': 'SUCCESS', 'install-maistra': 'SUCCESS', 'install-kiali-test-mesh-operator': 'SUCCESS'}
> Traceback (most recent call last):
> File "publish_jenkins_console.py", line 150, in <module>
> _url = _upload_console_log(_name, _ids_list)
> File "publish_jenkins_console.py", line 126, in _upload_console_log
> _url = _response.json()['url']
> File "/usr/lib/python2.7/site-packages/requests/models.py", line 897, in json
> return complexjson.loads(self.text, **kwargs)
> File "/usr/lib64/python2.7/json/__init__.py", line 338, in loads
> return _default_decoder.decode(s)
> File "/usr/lib64/python2.7/json/decoder.py", line 366, in decode
> obj, end = self.raw_decode(s, idx=_w(s, 0).end())
> File "/usr/lib64/python2.7/json/decoder.py", line 384, in raw_decode
> raise ValueError("No JSON object could be decoded")
> ValueError: No JSON object could be decoded
> cat: /home/jenkins/agent/workspace/python-ui-test-pr/build_comment_log.md: No such file or directory
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 9 months
[JBoss JIRA] (WFLY-12917) Optimize builders for JMS Client BOM
by Eduardo Martins (Jira)
Eduardo Martins created WFLY-12917:
--------------------------------------
Summary: Optimize builders for JMS Client BOM
Key: WFLY-12917
URL: https://issues.redhat.com/browse/WFLY-12917
Project: WildFly
Issue Type: Enhancement
Components: BOM
Reporter: Eduardo Martins
Assignee: Eduardo Martins
The builders for JMS Client BOM should be optimized, changing inherit exclusion mode to UNMANAGED, and removing artifacts which are just transitive dependencies of top level BOM artifacts.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 9 months
[JBoss JIRA] (WFLY-12916) Optimize builders for EJB Client BOMs
by Eduardo Martins (Jira)
[ https://issues.redhat.com/browse/WFLY-12916?page=com.atlassian.jira.plugi... ]
Eduardo Martins updated WFLY-12916:
-----------------------------------
Description: The builders for EJB Client and EJB Legacy Client BOMs should be optimized, changing inherit exclusion mode to UNMANAGED, and removing artifacts which are just transitive dependencies of top level BOM artifacts. (was: The builders for EJB Client and EJB Legacy Client BOMs should be optimized, changing inherit exclusion mode to UNMANAGED and removing artifacts which are just transitive dependencies of top level BOM artifacts.)
> Optimize builders for EJB Client BOMs
> -------------------------------------
>
> Key: WFLY-12916
> URL: https://issues.redhat.com/browse/WFLY-12916
> Project: WildFly
> Issue Type: Enhancement
> Components: BOM
> Reporter: Eduardo Martins
> Assignee: Eduardo Martins
> Priority: Major
>
> The builders for EJB Client and EJB Legacy Client BOMs should be optimized, changing inherit exclusion mode to UNMANAGED, and removing artifacts which are just transitive dependencies of top level BOM artifacts.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 9 months
[JBoss JIRA] (WFLY-12916) Optimize builders for EJB Client BOMs
by Eduardo Martins (Jira)
Eduardo Martins created WFLY-12916:
--------------------------------------
Summary: Optimize builders for EJB Client BOMs
Key: WFLY-12916
URL: https://issues.redhat.com/browse/WFLY-12916
Project: WildFly
Issue Type: Enhancement
Components: BOM
Reporter: Eduardo Martins
Assignee: Eduardo Martins
The builders for EJB Client and EJB Legacy Client BOMs should be optimized, changing inherit exclusion mode to UNMANAGED and removing artifacts which are just transitive dependencies of top level BOM artifacts.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 9 months
[JBoss JIRA] (WFLY-12914) Upgrade Galleon to 4.2.1.Final and the wildfly-galleon-plugins to 4.2.2.Final
by Brian Stansberry (Jira)
[ https://issues.redhat.com/browse/WFLY-12914?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFLY-12914:
------------------------------------
Summary: Upgrade Galleon to 4.2.1.Final and the wildfly-galleon-plugins to 4.2.2.Final (was: Upgrade Galleon to 4.2.1.Final and the wildfly-galleon-plugins to 4.2.2.Final; clean out unneeded provisioning boilerplate)
> Upgrade Galleon to 4.2.1.Final and the wildfly-galleon-plugins to 4.2.2.Final
> -----------------------------------------------------------------------------
>
> Key: WFLY-12914
> URL: https://issues.redhat.com/browse/WFLY-12914
> Project: WildFly
> Issue Type: Component Upgrade
> Components: Build System
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Priority: Major
> Fix For: 19.0.0.Beta1
>
>
> Upgrade Galleon to match the versions used in core.
> The current versions should allow trimming quite a bit of boilerplate from all the places where we provision servers:
> Alexey Loubyansky 5:07 PM
> I did a bit more work on this, fixed a couple of issues and just released Galleon 4.2.1.Final and WFGP 4.2.1.Final
> Alexey Loubyansky 5:07 PM
> also opened a PR to upgrade WildFly Core to these releases https://github.com/wildfly/wildfly-core/pull/4025
> 5:08 PM
> upgrading doesn't affect anything, except the bug fixes contained in those versions
> 5:10 PM
> however, for wildfly, i think we should use GAVs as feature-pack locations for feature-pack dependencies, in place of Galleon FPL
> 5:11 PM
> the benefit would be to avoid the universe resolver in maven builds
> 5:11 PM
> and also a simplified (mojo) provisioning config
> Brian Stansberry 5:14 PM
> good timing; I'm working on how to add a new f-p to wildfly (for microprofile stuff) so i should use best practices :)
> Alexey Loubyansky 5:16 PM
> by simplified provisioning config i mean that the selected block should be removed completely https://github.com/wildfly/wildfly/blob/master/build/pom.xml#L84-L97
> 5:16 PM
> the only reason it is there is to avoid resolution from the universe
> 5:17 PM
> with GAVs for dependencies, it won't be necessary anymore
> Brian Stansberry 5:17 PM
> what about <inheritConfigs>false</inheritConfigs> ?
> Alexey Loubyansky 5:18 PM
> that was there to workaround a bug which was fixed in 4.2.0.Final
> Brian Stansberry 5:18 PM
> how about
> 5:18 PM
> <included-packages>
> <name>docs.examples.configs</name>
> </included-packages>
> 5:19 PM
> assuming that's not in the top level f-p
> Alexey Loubyansky 5:19 PM
> that should definitely stay, it's not in the selected block
> 5:19 PM
> ah, then you can have that
> 5:20 PM
> then there would be a real reason to mention the transitive dependency
> 5:20 PM
> i.e. you want something from it
> Brian Stansberry 5:20 PM
> could it be declared in the top level block, even though the package is in the transitive dep?
> 5:20 PM
> i'm going off on tangents, but first i should have said...
> 5:21 PM
> Nice!
> Alexey Loubyansky 5:21 PM (EDITED)
> unless the package is installed by default, it has to be included explicitly using transitive element
>
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 9 months
[JBoss JIRA] (WFLY-12914) Upgrade Galleon to 4.2.1.Final and the wildfly-galleon-plugins to 4.2.2.Final
by Brian Stansberry (Jira)
[ https://issues.redhat.com/browse/WFLY-12914?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFLY-12914:
------------------------------------
Description:
Upgrade Galleon to match the versions used in core.
was:
Upgrade Galleon to match the versions used in core.
The current versions should allow trimming quite a bit of boilerplate from all the places where we provision servers:
Alexey Loubyansky 5:07 PM
I did a bit more work on this, fixed a couple of issues and just released Galleon 4.2.1.Final and WFGP 4.2.1.Final
Alexey Loubyansky 5:07 PM
also opened a PR to upgrade WildFly Core to these releases https://github.com/wildfly/wildfly-core/pull/4025
5:08 PM
upgrading doesn't affect anything, except the bug fixes contained in those versions
5:10 PM
however, for wildfly, i think we should use GAVs as feature-pack locations for feature-pack dependencies, in place of Galleon FPL
5:11 PM
the benefit would be to avoid the universe resolver in maven builds
5:11 PM
and also a simplified (mojo) provisioning config
Brian Stansberry 5:14 PM
good timing; I'm working on how to add a new f-p to wildfly (for microprofile stuff) so i should use best practices :)
Alexey Loubyansky 5:16 PM
by simplified provisioning config i mean that the selected block should be removed completely https://github.com/wildfly/wildfly/blob/master/build/pom.xml#L84-L97
5:16 PM
the only reason it is there is to avoid resolution from the universe
5:17 PM
with GAVs for dependencies, it won't be necessary anymore
Brian Stansberry 5:17 PM
what about <inheritConfigs>false</inheritConfigs> ?
Alexey Loubyansky 5:18 PM
that was there to workaround a bug which was fixed in 4.2.0.Final
Brian Stansberry 5:18 PM
how about
5:18 PM
<included-packages>
<name>docs.examples.configs</name>
</included-packages>
5:19 PM
assuming that's not in the top level f-p
Alexey Loubyansky 5:19 PM
that should definitely stay, it's not in the selected block
5:19 PM
ah, then you can have that
5:20 PM
then there would be a real reason to mention the transitive dependency
5:20 PM
i.e. you want something from it
Brian Stansberry 5:20 PM
could it be declared in the top level block, even though the package is in the transitive dep?
5:20 PM
i'm going off on tangents, but first i should have said...
5:21 PM
Nice!
Alexey Loubyansky 5:21 PM (EDITED)
unless the package is installed by default, it has to be included explicitly using transitive element
> Upgrade Galleon to 4.2.1.Final and the wildfly-galleon-plugins to 4.2.2.Final
> -----------------------------------------------------------------------------
>
> Key: WFLY-12914
> URL: https://issues.redhat.com/browse/WFLY-12914
> Project: WildFly
> Issue Type: Component Upgrade
> Components: Build System
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Priority: Major
> Fix For: 19.0.0.Beta1
>
>
> Upgrade Galleon to match the versions used in core.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 9 months
[JBoss JIRA] (WFLY-12915) Clean out unneeded provisioning boilerplate
by Brian Stansberry (Jira)
[ https://issues.redhat.com/browse/WFLY-12915?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFLY-12915:
------------------------------------
Issue Type: Task (was: Component Upgrade)
> Clean out unneeded provisioning boilerplate
> -------------------------------------------
>
> Key: WFLY-12915
> URL: https://issues.redhat.com/browse/WFLY-12915
> Project: WildFly
> Issue Type: Task
> Components: Build System
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Priority: Major
>
> Upgrade Galleon to match the versions used in core.
> The current versions should allow trimming quite a bit of boilerplate from all the places where we provision servers:
> Alexey Loubyansky 5:07 PM
> I did a bit more work on this, fixed a couple of issues and just released Galleon 4.2.1.Final and WFGP 4.2.1.Final
> Alexey Loubyansky 5:07 PM
> also opened a PR to upgrade WildFly Core to these releases https://github.com/wildfly/wildfly-core/pull/4025
> 5:08 PM
> upgrading doesn't affect anything, except the bug fixes contained in those versions
> 5:10 PM
> however, for wildfly, i think we should use GAVs as feature-pack locations for feature-pack dependencies, in place of Galleon FPL
> 5:11 PM
> the benefit would be to avoid the universe resolver in maven builds
> 5:11 PM
> and also a simplified (mojo) provisioning config
> Brian Stansberry 5:14 PM
> good timing; I'm working on how to add a new f-p to wildfly (for microprofile stuff) so i should use best practices :)
> Alexey Loubyansky 5:16 PM
> by simplified provisioning config i mean that the selected block should be removed completely https://github.com/wildfly/wildfly/blob/master/build/pom.xml#L84-L97
> 5:16 PM
> the only reason it is there is to avoid resolution from the universe
> 5:17 PM
> with GAVs for dependencies, it won't be necessary anymore
> Brian Stansberry 5:17 PM
> what about <inheritConfigs>false</inheritConfigs> ?
> Alexey Loubyansky 5:18 PM
> that was there to workaround a bug which was fixed in 4.2.0.Final
> Brian Stansberry 5:18 PM
> how about
> 5:18 PM
> <included-packages>
> <name>docs.examples.configs</name>
> </included-packages>
> 5:19 PM
> assuming that's not in the top level f-p
> Alexey Loubyansky 5:19 PM
> that should definitely stay, it's not in the selected block
> 5:19 PM
> ah, then you can have that
> 5:20 PM
> then there would be a real reason to mention the transitive dependency
> 5:20 PM
> i.e. you want something from it
> Brian Stansberry 5:20 PM
> could it be declared in the top level block, even though the package is in the transitive dep?
> 5:20 PM
> i'm going off on tangents, but first i should have said...
> 5:21 PM
> Nice!
> Alexey Loubyansky 5:21 PM (EDITED)
> unless the package is installed by default, it has to be included explicitly using transitive element
>
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 9 months
[JBoss JIRA] (WFLY-12915) Clean out unneeded provisioning boilerplate
by Brian Stansberry (Jira)
Brian Stansberry created WFLY-12915:
---------------------------------------
Summary: Clean out unneeded provisioning boilerplate
Key: WFLY-12915
URL: https://issues.redhat.com/browse/WFLY-12915
Project: WildFly
Issue Type: Component Upgrade
Components: Build System
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Upgrade Galleon to match the versions used in core.
The current versions should allow trimming quite a bit of boilerplate from all the places where we provision servers:
Alexey Loubyansky 5:07 PM
I did a bit more work on this, fixed a couple of issues and just released Galleon 4.2.1.Final and WFGP 4.2.1.Final
Alexey Loubyansky 5:07 PM
also opened a PR to upgrade WildFly Core to these releases https://github.com/wildfly/wildfly-core/pull/4025
5:08 PM
upgrading doesn't affect anything, except the bug fixes contained in those versions
5:10 PM
however, for wildfly, i think we should use GAVs as feature-pack locations for feature-pack dependencies, in place of Galleon FPL
5:11 PM
the benefit would be to avoid the universe resolver in maven builds
5:11 PM
and also a simplified (mojo) provisioning config
Brian Stansberry 5:14 PM
good timing; I'm working on how to add a new f-p to wildfly (for microprofile stuff) so i should use best practices :)
Alexey Loubyansky 5:16 PM
by simplified provisioning config i mean that the selected block should be removed completely https://github.com/wildfly/wildfly/blob/master/build/pom.xml#L84-L97
5:16 PM
the only reason it is there is to avoid resolution from the universe
5:17 PM
with GAVs for dependencies, it won't be necessary anymore
Brian Stansberry 5:17 PM
what about <inheritConfigs>false</inheritConfigs> ?
Alexey Loubyansky 5:18 PM
that was there to workaround a bug which was fixed in 4.2.0.Final
Brian Stansberry 5:18 PM
how about
5:18 PM
<included-packages>
<name>docs.examples.configs</name>
</included-packages>
5:19 PM
assuming that's not in the top level f-p
Alexey Loubyansky 5:19 PM
that should definitely stay, it's not in the selected block
5:19 PM
ah, then you can have that
5:20 PM
then there would be a real reason to mention the transitive dependency
5:20 PM
i.e. you want something from it
Brian Stansberry 5:20 PM
could it be declared in the top level block, even though the package is in the transitive dep?
5:20 PM
i'm going off on tangents, but first i should have said...
5:21 PM
Nice!
Alexey Loubyansky 5:21 PM (EDITED)
unless the package is installed by default, it has to be included explicitly using transitive element
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 9 months