[JBoss JIRA] (DROOLS-3030) [DMN Designer] Expand / Collapse all
by Guilherme Carreiro (Jira)
[ https://issues.jboss.org/browse/DROOLS-3030?page=com.atlassian.jira.plugi... ]
Guilherme Carreiro updated DROOLS-3030:
---------------------------------------
Story Points: 3
> [DMN Designer] Expand / Collapse all
> ------------------------------------
>
> Key: DROOLS-3030
> URL: https://issues.jboss.org/browse/DROOLS-3030
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Affects Versions: 7.12.0.Final
> Reporter: Jozef Marko
> Assignee: Guilherme Carreiro
> Priority: Major
> Labels: UX, drools-tools
>
> User should have possibility to easily expand / collapse all data types in the *manage custom data type* dialog.
> h2. Manual acceptance test
> - Expand
> -- All collapsed initially
> -- Something collapsed initially, something expanded already
> -- All expanded already
> - Collapse
> -- All expanded initially
> -- Something expanded initially, something collapsed already
> -- All collapsed already
> - No error warning in browser console log
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-3236) Unable to open KJAR project in eclipse due to "Missing parameter for pluginExecutionFilter"
by Matteo Mortari (Jira)
[ https://issues.jboss.org/browse/DROOLS-3236?page=com.atlassian.jira.plugi... ]
Matteo Mortari commented on DROOLS-3236:
----------------------------------------
My wild guess is that since 7.10.0.Final for some reason the kie-maven-plugin is passing an empty-set (that {{goals = '[]'}}) as the execution information metadata to Maven, hence m2eclipse is reporting the error.
I believe the line is: https://github.com/eclipse/m2e-core/blob/c304dad55ce0f80d2cfcf75497280148...
The full error is:
{code:java}
ENTRY org.eclipse.core.resources 4 75 2018-11-05 14:19:41.206
!MESSAGE Errors occurred during the build.
!SUBENTRY 1 org.eclipse.m2e.core 4 75 2018-11-05 14:19:41.206
!MESSAGE Errors running builder 'Maven Project Builder' on project 'test-generateModel-kjararchetype'.
!STACK 0
java.lang.IllegalArgumentException: Missing parameter for pluginExecutionFilter. groupId, artifactId, versionRange and goals must be specificed, but found: groupId = 'org.kie'
artifactId = 'kie-maven-plugin'
versionRange = '7.14.0-SNAPSHOT'
goals = '[]'
at org.eclipse.m2e.core.internal.lifecyclemapping.model.PluginExecutionFilter.checkAllFieldsSet(PluginExecutionFilter.java:320)
at org.eclipse.m2e.core.internal.lifecyclemapping.model.PluginExecutionFilter.match(PluginExecutionFilter.java:331)
at org.eclipse.m2e.core.internal.lifecyclemapping.SimpleMappingMetadataSource.getPluginExecutionMetadata(SimpleMappingMetadataSource.java:79)
at org.eclipse.m2e.core.internal.lifecyclemapping.LifecycleMappingFactory.calculateEffectiveLifecycleMappingMetadata0(LifecycleMappingFactory.java:599)
at org.eclipse.m2e.core.internal.lifecyclemapping.LifecycleMappingFactory.calculateEffectiveLifecycleMappingMetadata(LifecycleMappingFactory.java:535)
at org.eclipse.m2e.core.internal.lifecyclemapping.LifecycleMappingFactory.calculateEffectiveLifecycleMappingMetadata(LifecycleMappingFactory.java:249)
at org.eclipse.m2e.core.internal.lifecyclemapping.LifecycleMappingFactory.calculateLifecycleMapping(LifecycleMappingFactory.java:181)
at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.setupLifecycleMapping(ProjectRegistryManager.java:594)
at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.refreshPhase2(ProjectRegistryManager.java:513)
at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager$3.call(ProjectRegistryManager.java:492)
at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager$3.call(ProjectRegistryManager.java:1)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:177)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:151)
at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.refresh(ProjectRegistryManager.java:496)
at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.refresh(ProjectRegistryManager.java:351)
at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.refresh(ProjectRegistryManager.java:298)
at org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod.getProjectFacade(MavenBuilder.java:155)
at org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod$1.call(MavenBuilder.java:90)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:177)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:151)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:99)
at org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod.execute(MavenBuilder.java:87)
at org.eclipse.m2e.core.internal.builder.MavenBuilder.build(MavenBuilder.java:201)
at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:798)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:45)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:219)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:262)
at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:315)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:45)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:318)
at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:370)
at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:391)
at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:145)
at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:235)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)
{code}
> Unable to open KJAR project in eclipse due to "Missing parameter for pluginExecutionFilter"
> -------------------------------------------------------------------------------------------
>
> Key: DROOLS-3236
> URL: https://issues.jboss.org/browse/DROOLS-3236
> Project: Drools
> Issue Type: Bug
> Components: tools
> Affects Versions: 7.10.0.Final, 7.11.0.Final, 7.12.0.Final, 7.13.0.Final
> Environment: Eclipse photon, Eclipse 2018 09, no special plugin
> m2eclipse configured to do-not-manage/ignore any unknown plugin goal (easiest choice)
> Reporter: Matteo Mortari
> Assignee: Mario Fusco
> Priority: Major
> Attachments: image-2018-11-05-10-28-50-255.png
>
>
> Since 7.10.0.Final the following error occurs when opening a KJAR project in Eclipse:
> !image-2018-11-05-10-28-50-255.png!
> Errors occurred during the build.
> Errors running builder 'Maven Project Builder' on project '...'.
> Missing parameter for pluginExecutionFilter. groupId, artifactId, versionRange and goals must be specificed, but found: groupId = 'org.kie'
> artifactId = 'kie-maven-plugin'
> versionRange = '7.10.0.Final'
> goals = '[]'
> Please notice kie-maven-plugin 7.9.0.Final and earlier do NOT exhibit this issue.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFLY-5966) Validate requirement for modules previously exported by javax.ejb.api
by Yeray Borges (Jira)
[ https://issues.jboss.org/browse/WFLY-5966?page=com.atlassian.jira.plugin.... ]
Yeray Borges updated WFLY-5966:
-------------------------------
Description:
The WFLY-5922 fix removed the exporting of a number of modules from javax.ejb.api. That introduced some problems with modules that depended on those exported packages no longer having visibility to needed classes, so to prevent problems I blindly added a commit to the module.xml for each module that depended upon javax.ejb.api to add a dependency set like this:
{code}
<!-- TODO validate the need for these and remove if not needed.
Prior to WFLY-5922 they were exported by javax.ejb.api. -->
<module name="javax.api"/>
<module name="javax.transaction.api"/>
<module name="javax.xml.rpc.api"/>
<module name="javax.rmi.api"/>
<module name="org.omg.api"/>
{code}
If a module already had a dep on one of those, it's not in the block.
This task is to check each of these modules and replace that block with normal dependency declarations for any that are truly needed.
Affected modules:
feature-pack/src/main/resources/modules/system/layers/base/javaee/api/main/module.xml
feature-pack/src/main/resources/modules/system/layers/base/javax/management/j2ee/api/main/module.xml
feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/ejb3/main/module.xml
-feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/jsr77/main/module.xml-
feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/webservices/main/module.xml
feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/weld/main/module.xml
-feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/xts/main/module.xml-
feature-pack/src/main/resources/modules/system/layers/base/org/jboss/ejb-client/main/module.xml
feature-pack/src/main/resources/modules/system/layers/base/org/jboss/ejb3/main/module.xml
feature-pack/src/main/resources/modules/system/layers/base/org/jboss/iiop-client/main/module.xml
feature-pack/src/main/resources/modules/system/layers/base/org/jboss/metadata/appclient/main/module.xml
feature-pack/src/main/resources/modules/system/layers/base/org/jboss/metadata/ejb/main/module.xml
-feature-pack/src/main/resources/modules/system/layers/base/org/jboss/narayana/compensations/main/module.xml-
-feature-pack/src/main/resources/modules/system/layers/base/org/jboss/narayana/rts/main/module.xml-
feature-pack/src/main/resources/modules/system/layers/base/org/jboss/narayana/txframework/main/module.xml
feature-pack/src/main/resources/modules/system/layers/base/org/jboss/weld/core/main/module.xml
feature-pack/src/main/resources/modules/system/layers/base/org/jboss/ws/common/main/module.xml
-feature-pack/src/main/resources/modules/system/layers/base/org/jboss/xts/main/module.xml-
-feature-pack/src/main/resources/modules/system/layers/base/org/wildfly/extension/rts/main/module.xml-
The following modules were indirectly affected via their dependency on javaee.api, which in turn exports javax.ejb.api:
feature-pack/src/main/resources/modules/system/layers/base/com/sun/jsf-impl/main/module.xml
feature-pack/src/main/resources/modules/system/layers/base/org/jberet/jberet-core/main/module.xml
feature-pack/src/main/resources/modules/system/layers/base/org/wildfly/jberet/main/module.xml
jsf/multi-jsf-installer/src/main/resources/mojarra-impl-module.xml
jsf/multi-jsf-installer/src/main/resources/myfaces-impl-module.xml
The following modules were fixed or verified as correct (moved from the first list):
feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/jpa/main/module.xml
feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/jpa/spi/main/module.xml
was:
The WFLY-5922 fix removed the exporting of a number of modules from javax.ejb.api. That introduced some problems with modules that depended on those exported packages no longer having visibility to needed classes, so to prevent problems I blindly added a commit to the module.xml for each module that depended upon javax.ejb.api to add a dependency set like this:
{code}
<!-- TODO validate the need for these and remove if not needed.
Prior to WFLY-5922 they were exported by javax.ejb.api. -->
<module name="javax.api"/>
<module name="javax.transaction.api"/>
<module name="javax.xml.rpc.api"/>
<module name="javax.rmi.api"/>
<module name="org.omg.api"/>
{code}
If a module already had a dep on one of those, it's not in the block.
This task is to check each of these modules and replace that block with normal dependency declarations for any that are truly needed.
Affected modules:
feature-pack/src/main/resources/modules/system/layers/base/javaee/api/main/module.xml
feature-pack/src/main/resources/modules/system/layers/base/javax/management/j2ee/api/main/module.xml
feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/ejb3/main/module.xml
-feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/jsr77/main/module.xml-
feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/webservices/main/module.xml
feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/weld/main/module.xml
-feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/xts/main/module.xml-
feature-pack/src/main/resources/modules/system/layers/base/org/jboss/ejb-client/main/module.xml
feature-pack/src/main/resources/modules/system/layers/base/org/jboss/ejb3/main/module.xml
feature-pack/src/main/resources/modules/system/layers/base/org/jboss/iiop-client/main/module.xml
feature-pack/src/main/resources/modules/system/layers/base/org/jboss/metadata/appclient/main/module.xml
feature-pack/src/main/resources/modules/system/layers/base/org/jboss/metadata/ejb/main/module.xml
-feature-pack/src/main/resources/modules/system/layers/base/org/jboss/narayana/compensations/main/module.xml-
feature-pack/src/main/resources/modules/system/layers/base/org/jboss/narayana/rts/main/module.xml
feature-pack/src/main/resources/modules/system/layers/base/org/jboss/narayana/txframework/main/module.xml
feature-pack/src/main/resources/modules/system/layers/base/org/jboss/weld/core/main/module.xml
feature-pack/src/main/resources/modules/system/layers/base/org/jboss/ws/common/main/module.xml
-feature-pack/src/main/resources/modules/system/layers/base/org/jboss/xts/main/module.xml-
-feature-pack/src/main/resources/modules/system/layers/base/org/wildfly/extension/rts/main/module.xml-
The following modules were indirectly affected via their dependency on javaee.api, which in turn exports javax.ejb.api:
feature-pack/src/main/resources/modules/system/layers/base/com/sun/jsf-impl/main/module.xml
feature-pack/src/main/resources/modules/system/layers/base/org/jberet/jberet-core/main/module.xml
feature-pack/src/main/resources/modules/system/layers/base/org/wildfly/jberet/main/module.xml
jsf/multi-jsf-installer/src/main/resources/mojarra-impl-module.xml
jsf/multi-jsf-installer/src/main/resources/myfaces-impl-module.xml
The following modules were fixed or verified as correct (moved from the first list):
feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/jpa/main/module.xml
feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/jpa/spi/main/module.xml
> Validate requirement for modules previously exported by javax.ejb.api
> ---------------------------------------------------------------------
>
> Key: WFLY-5966
> URL: https://issues.jboss.org/browse/WFLY-5966
> Project: WildFly
> Issue Type: Task
> Components: Server
> Reporter: Brian Stansberry
> Assignee: Yeray Borges
> Priority: Major
>
> The WFLY-5922 fix removed the exporting of a number of modules from javax.ejb.api. That introduced some problems with modules that depended on those exported packages no longer having visibility to needed classes, so to prevent problems I blindly added a commit to the module.xml for each module that depended upon javax.ejb.api to add a dependency set like this:
> {code}
> <!-- TODO validate the need for these and remove if not needed.
> Prior to WFLY-5922 they were exported by javax.ejb.api. -->
> <module name="javax.api"/>
> <module name="javax.transaction.api"/>
> <module name="javax.xml.rpc.api"/>
> <module name="javax.rmi.api"/>
> <module name="org.omg.api"/>
> {code}
> If a module already had a dep on one of those, it's not in the block.
> This task is to check each of these modules and replace that block with normal dependency declarations for any that are truly needed.
> Affected modules:
> feature-pack/src/main/resources/modules/system/layers/base/javaee/api/main/module.xml
> feature-pack/src/main/resources/modules/system/layers/base/javax/management/j2ee/api/main/module.xml
> feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/ejb3/main/module.xml
> -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/jsr77/main/module.xml-
> feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/webservices/main/module.xml
> feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/weld/main/module.xml
> -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/xts/main/module.xml-
> feature-pack/src/main/resources/modules/system/layers/base/org/jboss/ejb-client/main/module.xml
> feature-pack/src/main/resources/modules/system/layers/base/org/jboss/ejb3/main/module.xml
> feature-pack/src/main/resources/modules/system/layers/base/org/jboss/iiop-client/main/module.xml
> feature-pack/src/main/resources/modules/system/layers/base/org/jboss/metadata/appclient/main/module.xml
> feature-pack/src/main/resources/modules/system/layers/base/org/jboss/metadata/ejb/main/module.xml
> -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/narayana/compensations/main/module.xml-
> -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/narayana/rts/main/module.xml-
> feature-pack/src/main/resources/modules/system/layers/base/org/jboss/narayana/txframework/main/module.xml
> feature-pack/src/main/resources/modules/system/layers/base/org/jboss/weld/core/main/module.xml
> feature-pack/src/main/resources/modules/system/layers/base/org/jboss/ws/common/main/module.xml
> -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/xts/main/module.xml-
> -feature-pack/src/main/resources/modules/system/layers/base/org/wildfly/extension/rts/main/module.xml-
> The following modules were indirectly affected via their dependency on javaee.api, which in turn exports javax.ejb.api:
> feature-pack/src/main/resources/modules/system/layers/base/com/sun/jsf-impl/main/module.xml
> feature-pack/src/main/resources/modules/system/layers/base/org/jberet/jberet-core/main/module.xml
> feature-pack/src/main/resources/modules/system/layers/base/org/wildfly/jberet/main/module.xml
> jsf/multi-jsf-installer/src/main/resources/mojarra-impl-module.xml
> jsf/multi-jsf-installer/src/main/resources/myfaces-impl-module.xml
> The following modules were fixed or verified as correct (moved from the first list):
> feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/jpa/main/module.xml
> feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/jpa/spi/main/module.xml
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFLY-5966) Validate requirement for modules previously exported by javax.ejb.api
by Yeray Borges (Jira)
[ https://issues.jboss.org/browse/WFLY-5966?page=com.atlassian.jira.plugin.... ]
Yeray Borges updated WFLY-5966:
-------------------------------
Description:
The WFLY-5922 fix removed the exporting of a number of modules from javax.ejb.api. That introduced some problems with modules that depended on those exported packages no longer having visibility to needed classes, so to prevent problems I blindly added a commit to the module.xml for each module that depended upon javax.ejb.api to add a dependency set like this:
{code}
<!-- TODO validate the need for these and remove if not needed.
Prior to WFLY-5922 they were exported by javax.ejb.api. -->
<module name="javax.api"/>
<module name="javax.transaction.api"/>
<module name="javax.xml.rpc.api"/>
<module name="javax.rmi.api"/>
<module name="org.omg.api"/>
{code}
If a module already had a dep on one of those, it's not in the block.
This task is to check each of these modules and replace that block with normal dependency declarations for any that are truly needed.
Affected modules:
feature-pack/src/main/resources/modules/system/layers/base/javaee/api/main/module.xml
feature-pack/src/main/resources/modules/system/layers/base/javax/management/j2ee/api/main/module.xml
feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/ejb3/main/module.xml
-feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/jsr77/main/module.xml-
feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/webservices/main/module.xml
feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/weld/main/module.xml
-feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/xts/main/module.xml-
feature-pack/src/main/resources/modules/system/layers/base/org/jboss/ejb-client/main/module.xml
feature-pack/src/main/resources/modules/system/layers/base/org/jboss/ejb3/main/module.xml
feature-pack/src/main/resources/modules/system/layers/base/org/jboss/iiop-client/main/module.xml
feature-pack/src/main/resources/modules/system/layers/base/org/jboss/metadata/appclient/main/module.xml
feature-pack/src/main/resources/modules/system/layers/base/org/jboss/metadata/ejb/main/module.xml
-feature-pack/src/main/resources/modules/system/layers/base/org/jboss/narayana/compensations/main/module.xml-
feature-pack/src/main/resources/modules/system/layers/base/org/jboss/narayana/rts/main/module.xml
feature-pack/src/main/resources/modules/system/layers/base/org/jboss/narayana/txframework/main/module.xml
feature-pack/src/main/resources/modules/system/layers/base/org/jboss/weld/core/main/module.xml
feature-pack/src/main/resources/modules/system/layers/base/org/jboss/ws/common/main/module.xml
-feature-pack/src/main/resources/modules/system/layers/base/org/jboss/xts/main/module.xml-
-feature-pack/src/main/resources/modules/system/layers/base/org/wildfly/extension/rts/main/module.xml-
The following modules were indirectly affected via their dependency on javaee.api, which in turn exports javax.ejb.api:
feature-pack/src/main/resources/modules/system/layers/base/com/sun/jsf-impl/main/module.xml
feature-pack/src/main/resources/modules/system/layers/base/org/jberet/jberet-core/main/module.xml
feature-pack/src/main/resources/modules/system/layers/base/org/wildfly/jberet/main/module.xml
jsf/multi-jsf-installer/src/main/resources/mojarra-impl-module.xml
jsf/multi-jsf-installer/src/main/resources/myfaces-impl-module.xml
The following modules were fixed or verified as correct (moved from the first list):
feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/jpa/main/module.xml
feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/jpa/spi/main/module.xml
was:
The WFLY-5922 fix removed the exporting of a number of modules from javax.ejb.api. That introduced some problems with modules that depended on those exported packages no longer having visibility to needed classes, so to prevent problems I blindly added a commit to the module.xml for each module that depended upon javax.ejb.api to add a dependency set like this:
{code}
<!-- TODO validate the need for these and remove if not needed.
Prior to WFLY-5922 they were exported by javax.ejb.api. -->
<module name="javax.api"/>
<module name="javax.transaction.api"/>
<module name="javax.xml.rpc.api"/>
<module name="javax.rmi.api"/>
<module name="org.omg.api"/>
{code}
If a module already had a dep on one of those, it's not in the block.
This task is to check each of these modules and replace that block with normal dependency declarations for any that are truly needed.
Affected modules:
feature-pack/src/main/resources/modules/system/layers/base/javaee/api/main/module.xml
feature-pack/src/main/resources/modules/system/layers/base/javax/management/j2ee/api/main/module.xml
feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/ejb3/main/module.xml
-feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/jsr77/main/module.xml-
feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/webservices/main/module.xml
feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/weld/main/module.xml
-feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/xts/main/module.xml-
feature-pack/src/main/resources/modules/system/layers/base/org/jboss/ejb-client/main/module.xml
feature-pack/src/main/resources/modules/system/layers/base/org/jboss/ejb3/main/module.xml
feature-pack/src/main/resources/modules/system/layers/base/org/jboss/iiop-client/main/module.xml
feature-pack/src/main/resources/modules/system/layers/base/org/jboss/metadata/appclient/main/module.xml
feature-pack/src/main/resources/modules/system/layers/base/org/jboss/metadata/ejb/main/module.xml
-feature-pack/src/main/resources/modules/system/layers/base/org/jboss/narayana/compensations/main/module.xml-
feature-pack/src/main/resources/modules/system/layers/base/org/jboss/narayana/rts/main/module.xml
feature-pack/src/main/resources/modules/system/layers/base/org/jboss/narayana/txframework/main/module.xml
feature-pack/src/main/resources/modules/system/layers/base/org/jboss/weld/core/main/module.xml
feature-pack/src/main/resources/modules/system/layers/base/org/jboss/ws/common/main/module.xml
feature-pack/src/main/resources/modules/system/layers/base/org/jboss/xts/main/module.xml
-feature-pack/src/main/resources/modules/system/layers/base/org/wildfly/extension/rts/main/module.xml-
The following modules were indirectly affected via their dependency on javaee.api, which in turn exports javax.ejb.api:
feature-pack/src/main/resources/modules/system/layers/base/com/sun/jsf-impl/main/module.xml
feature-pack/src/main/resources/modules/system/layers/base/org/jberet/jberet-core/main/module.xml
feature-pack/src/main/resources/modules/system/layers/base/org/wildfly/jberet/main/module.xml
jsf/multi-jsf-installer/src/main/resources/mojarra-impl-module.xml
jsf/multi-jsf-installer/src/main/resources/myfaces-impl-module.xml
The following modules were fixed or verified as correct (moved from the first list):
feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/jpa/main/module.xml
feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/jpa/spi/main/module.xml
> Validate requirement for modules previously exported by javax.ejb.api
> ---------------------------------------------------------------------
>
> Key: WFLY-5966
> URL: https://issues.jboss.org/browse/WFLY-5966
> Project: WildFly
> Issue Type: Task
> Components: Server
> Reporter: Brian Stansberry
> Assignee: Yeray Borges
> Priority: Major
>
> The WFLY-5922 fix removed the exporting of a number of modules from javax.ejb.api. That introduced some problems with modules that depended on those exported packages no longer having visibility to needed classes, so to prevent problems I blindly added a commit to the module.xml for each module that depended upon javax.ejb.api to add a dependency set like this:
> {code}
> <!-- TODO validate the need for these and remove if not needed.
> Prior to WFLY-5922 they were exported by javax.ejb.api. -->
> <module name="javax.api"/>
> <module name="javax.transaction.api"/>
> <module name="javax.xml.rpc.api"/>
> <module name="javax.rmi.api"/>
> <module name="org.omg.api"/>
> {code}
> If a module already had a dep on one of those, it's not in the block.
> This task is to check each of these modules and replace that block with normal dependency declarations for any that are truly needed.
> Affected modules:
> feature-pack/src/main/resources/modules/system/layers/base/javaee/api/main/module.xml
> feature-pack/src/main/resources/modules/system/layers/base/javax/management/j2ee/api/main/module.xml
> feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/ejb3/main/module.xml
> -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/jsr77/main/module.xml-
> feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/webservices/main/module.xml
> feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/weld/main/module.xml
> -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/xts/main/module.xml-
> feature-pack/src/main/resources/modules/system/layers/base/org/jboss/ejb-client/main/module.xml
> feature-pack/src/main/resources/modules/system/layers/base/org/jboss/ejb3/main/module.xml
> feature-pack/src/main/resources/modules/system/layers/base/org/jboss/iiop-client/main/module.xml
> feature-pack/src/main/resources/modules/system/layers/base/org/jboss/metadata/appclient/main/module.xml
> feature-pack/src/main/resources/modules/system/layers/base/org/jboss/metadata/ejb/main/module.xml
> -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/narayana/compensations/main/module.xml-
> feature-pack/src/main/resources/modules/system/layers/base/org/jboss/narayana/rts/main/module.xml
> feature-pack/src/main/resources/modules/system/layers/base/org/jboss/narayana/txframework/main/module.xml
> feature-pack/src/main/resources/modules/system/layers/base/org/jboss/weld/core/main/module.xml
> feature-pack/src/main/resources/modules/system/layers/base/org/jboss/ws/common/main/module.xml
> -feature-pack/src/main/resources/modules/system/layers/base/org/jboss/xts/main/module.xml-
> -feature-pack/src/main/resources/modules/system/layers/base/org/wildfly/extension/rts/main/module.xml-
> The following modules were indirectly affected via their dependency on javaee.api, which in turn exports javax.ejb.api:
> feature-pack/src/main/resources/modules/system/layers/base/com/sun/jsf-impl/main/module.xml
> feature-pack/src/main/resources/modules/system/layers/base/org/jberet/jberet-core/main/module.xml
> feature-pack/src/main/resources/modules/system/layers/base/org/wildfly/jberet/main/module.xml
> jsf/multi-jsf-installer/src/main/resources/mojarra-impl-module.xml
> jsf/multi-jsf-installer/src/main/resources/myfaces-impl-module.xml
> The following modules were fixed or verified as correct (moved from the first list):
> feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/jpa/main/module.xml
> feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/jpa/spi/main/module.xml
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-3241) [DMN Designer] Improve the Data Types support
by Guilherme Carreiro (Jira)
[ https://issues.jboss.org/browse/DROOLS-3241?page=com.atlassian.jira.plugi... ]
Guilherme Carreiro updated DROOLS-3241:
---------------------------------------
Epic Name: [DMN Designer] Improve the Data Types support (was: [DMN Designer] Add support to define data-types (7.3))
> [DMN Designer] Improve the Data Types support
> ---------------------------------------------
>
> Key: DROOLS-3241
> URL: https://issues.jboss.org/browse/DROOLS-3241
> Project: Drools
> Issue Type: Epic
> Components: DMN Editor
> Reporter: Guilherme Carreiro
> Assignee: Guilherme Carreiro
> Priority: Major
> Labels: drools-tools
>
> As a practitioner, I want to be able to define Data Types in the UI, so that when the DMN engine evaluates a decision table input/output it will check if the type of the value matches the specified type.
> Verification conditions:
> Support added for the User to define data-types ({{ItemDefinition}}).
> This may become a top-level task when I get to work on it; as the requirement is quite large and encompasses nested data-types (a whole new grid will be required); and definition of enums, constrains on values etc.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-3241) [DMN Designer] Improve the Data Types support
by Guilherme Carreiro (Jira)
[ https://issues.jboss.org/browse/DROOLS-3241?page=com.atlassian.jira.plugi... ]
Guilherme Carreiro updated DROOLS-3241:
---------------------------------------
Summary: [DMN Designer] Improve the Data Types support (was: [DMN Designer] Add support to define data-types (7.3))
> [DMN Designer] Improve the Data Types support
> ---------------------------------------------
>
> Key: DROOLS-3241
> URL: https://issues.jboss.org/browse/DROOLS-3241
> Project: Drools
> Issue Type: Epic
> Components: DMN Editor
> Reporter: Guilherme Carreiro
> Assignee: Guilherme Carreiro
> Priority: Major
> Labels: drools-tools
>
> As a practitioner, I want to be able to define Data Types in the UI, so that when the DMN engine evaluates a decision table input/output it will check if the type of the value matches the specified type.
> Verification conditions:
> Support added for the User to define data-types ({{ItemDefinition}}).
> This may become a top-level task when I get to work on it; as the requirement is quite large and encompasses nested data-types (a whole new grid will be required); and definition of enums, constrains on values etc.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (SWSQE-476) PRT Output Improve
by Hayk Hovsepyan (Jira)
[ https://issues.jboss.org/browse/SWSQE-476?page=com.atlassian.jira.plugin.... ]
Hayk Hovsepyan resolved SWSQE-476.
----------------------------------
Resolution: Done
> PRT Output Improve
> ------------------
>
> Key: SWSQE-476
> URL: https://issues.jboss.org/browse/SWSQE-476
> Project: Kiali QE
> Issue Type: QE Task
> Reporter: Hayk Hovsepyan
> Assignee: Hayk Hovsepyan
> Priority: Major
>
> Feedback from developers.
> When PRT fails because of some internal reason, e.g. bookinfo install fails, devs are confused. Or if e2e tests fail for some other reason.
> What we need to do, when PRT fails due to other reason that e2e tests broken by PR, then the bot should comment in PR that "PRT is broken, contact to QE".
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months