[JBoss JIRA] (WFLY-11303) Unnecessary registration of a CDI portable extension in Smallrye micro profile config
by James Perkins (Jira)
[ https://issues.jboss.org/browse/WFLY-11303?page=com.atlassian.jira.plugin... ]
James Perkins updated WFLY-11303:
---------------------------------
Fix Version/s: 15.0.0.Final
> Unnecessary registration of a CDI portable extension in Smallrye micro profile config
> -------------------------------------------------------------------------------------
>
> Key: WFLY-11303
> URL: https://issues.jboss.org/browse/WFLY-11303
> Project: WildFly
> Issue Type: Bug
> Components: MP Config
> Reporter: Yeray Borges
> Assignee: Yeray Borges
> Priority: Major
> Fix For: 15.0.0.Beta1, 15.0.0.Final
>
>
> Smallrye micro profile is registering a ConfigExtension when it is already registered by Weld.
> This portable extension is brought in by io.smallrye:smallrye-config dependency in its META-INF folder, and Weld automatically registers a CDI portable extension if it is found in the application classpath. That means it is unnecesary to register it again by wildfly config-smallrye.
> It will allow also remove some unnecesary modules dependencies.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFLY-10954) Failing OnOffOpenTracingTestCase on IBM java
by James Perkins (Jira)
[ https://issues.jboss.org/browse/WFLY-10954?page=com.atlassian.jira.plugin... ]
James Perkins updated WFLY-10954:
---------------------------------
Fix Version/s: 15.0.0.Final
> Failing OnOffOpenTracingTestCase on IBM java
> --------------------------------------------
>
> Key: WFLY-10954
> URL: https://issues.jboss.org/browse/WFLY-10954
> Project: WildFly
> Issue Type: Bug
> Components: Test Suite
> Affects Versions: 14.0.0.Beta2
> Reporter: Jan Stourac
> Assignee: Jan Stourac
> Priority: Major
> Fix For: 15.0.0.Beta1, 15.0.0.Final
>
>
> The OnOffOpenTracingTestCase fails with IBM java due to the different stack trace output compared to the OpenJDK/OracleJDK. In the test there is checked
> {code}
> java.lang.NoClassDefFoundError: Lio/opentracing/Tracer
> {code}
> but IBM java provides slightly different variation
> {code}
> java.lang.NoClassDefFoundError: io.opentracing.Tracer
> {code}
> in the stacktrace.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFLY-11301) Banned dependencies not excluded
by James Perkins (Jira)
[ https://issues.jboss.org/browse/WFLY-11301?page=com.atlassian.jira.plugin... ]
James Perkins updated WFLY-11301:
---------------------------------
Fix Version/s: 15.0.0.Final
> Banned dependencies not excluded
> --------------------------------
>
> Key: WFLY-11301
> URL: https://issues.jboss.org/browse/WFLY-11301
> Project: WildFly
> Issue Type: Bug
> Components: Build System
> Reporter: Eduardo Martins
> Assignee: Eduardo Martins
> Priority: Major
> Fix For: 15.0.0.Beta1, 15.0.0.Final
>
>
> The following exclusions of banned dependencies should be added:
> {code}
> <dependency>
> <groupId>org.jboss.ws.cxf</groupId>
> <artifactId>jbossws-cxf-client</artifactId>
> <exclusions>
> <exclusion>
> <groupId>org.slf4j</groupId>
> <artifactId>slf4j-log4j12</artifactId>
> </exclusion>
> </exclusions>
> </dependency>
> <dependency>
> <groupId>org.apache.cxf</groupId>
> <artifactId>cxf-tools-java2ws</artifactId>
> <exclusions>
> <exclusion>
> <groupId>com.sun.xml.bind</groupId>
> <artifactId>jaxb-xjc</artifactId>
> </exclusion>
> <exclusion>
> <groupId>com.sun.xml.bind</groupId>
> <artifactId>jaxb-core</artifactId>
> </exclusion>
> </exclusions>
> </dependency>
> <dependency>
> <groupId>org.apache.cxf</groupId>
> <artifactId>cxf-tools-wsdlto-core</artifactId>
> <exclusions>
> <exclusion>
> <groupId>com.sun.xml.bind</groupId>
> <artifactId>jaxb-core</artifactId>
> </exclusion>
> </exclusions>
> </dependency>
> <dependency>
> <groupId>org.apache.cxf</groupId>
> <artifactId>cxf-tools-wsdlto-databinding-jaxb</artifactId>
> <exclusions>
> <exclusion>
> <groupId>com.sun.xml.bind</groupId>
> <artifactId>jaxb-core</artifactId>
> </exclusion>
> </exclusions>
> </dependency>
> <dependency>
> <groupId>org.apache.cxf</groupId>
> <artifactId>cxf-tools-validator</artifactId>
> <exclusions>
> <exclusion>
> <groupId>com.sun.xml.bind</groupId>
> <artifactId>jaxb-core</artifactId>
> </exclusion>
> </exclusions>
> </dependency>
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-3286) [DMN Designer] FunctionGrid: Move F, J, P selector to header
by Daniel José dos Santos (Jira)
[ https://issues.jboss.org/browse/DROOLS-3286?page=com.atlassian.jira.plugi... ]
Daniel José dos Santos updated DROOLS-3286:
-------------------------------------------
Description:
The {{FunctionGrid}} allows switching between FEEL, Java and PMML function definitions using the context menu. [~tirelli] has requested this be changed to a selector in the header. A new column needs to be added with the F, J, P selector in the new column header. The header should display F, J or P accordingly. Do not include row numbers (i.e. don't just add a {{RowNumberColumn}}!
Also, the default in classes should be String, not Undefined.
The cell that shows function parameters also needs to show the text "Select parameters" when there is none parameter added and the parameters when there is parameters.
was:
The {{FunctionGrid}} allows switching between FEEL, Java and PMML function definitions using the context menu. [~tirelli] has requested this be changed to a selector in the header. A new column needs to be added with the F, J, P selector in the new column header. The header should display F, J or P accordingly. Do not include row numbers (i.e. don't just add a {{RowNumberColumn}}!
Also, the default in classes should be String, not Undefined.
> [DMN Designer] FunctionGrid: Move F, J, P selector to header
> -------------------------------------------------------------
>
> Key: DROOLS-3286
> URL: https://issues.jboss.org/browse/DROOLS-3286
> Project: Drools
> Issue Type: Feature Request
> Components: DMN Editor
> Affects Versions: 7.14.0.Final
> Reporter: Michael Anstis
> Assignee: Daniel José dos Santos
> Priority: Major
> Labels: drools-tools
>
> The {{FunctionGrid}} allows switching between FEEL, Java and PMML function definitions using the context menu. [~tirelli] has requested this be changed to a selector in the header. A new column needs to be added with the F, J, P selector in the new column header. The header should display F, J or P accordingly. Do not include row numbers (i.e. don't just add a {{RowNumberColumn}}!
> Also, the default in classes should be String, not Undefined.
> The cell that shows function parameters also needs to show the text "Select parameters" when there is none parameter added and the parameters when there is parameters.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFLY-11325) The org.jdom module should be deprecated
by James Perkins (Jira)
[ https://issues.jboss.org/browse/WFLY-11325?page=com.atlassian.jira.plugin... ]
James Perkins updated WFLY-11325:
---------------------------------
Fix Version/s: 15.0.0.Final
> The org.jdom module should be deprecated
> ----------------------------------------
>
> Key: WFLY-11325
> URL: https://issues.jboss.org/browse/WFLY-11325
> Project: WildFly
> Issue Type: Bug
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Priority: Major
> Fix For: 15.0.0.Beta1, 15.0.0.Final
>
>
> The org.jdom module is jboss.api=unsupported in EAP and is not actually used by WF or added as a dependency by it to deployments. It looks like it probably should have been made private way back in 2012 when it was made 'unsupported' in EAP. The 'unsupported' is inappropriate in WF so it got removed, resulting in it becoming 'public'.
> The only module that depends on org.jdom is org.jaxen. Jaxen's pom declares it as an optional dependency. Here is the production code use of jdom by jaxen:
> {code}
> src/java/main/org/jaxen/jdom/DocumentNavigator.java:import org.jdom.Attribute;
> src/java/main/org/jaxen/jdom/DocumentNavigator.java:import org.jdom.CDATA;
> src/java/main/org/jaxen/jdom/DocumentNavigator.java:import org.jdom.Comment;
> src/java/main/org/jaxen/jdom/DocumentNavigator.java:import org.jdom.Document;
> src/java/main/org/jaxen/jdom/DocumentNavigator.java:import org.jdom.Element;
> src/java/main/org/jaxen/jdom/DocumentNavigator.java:import org.jdom.Namespace;
> src/java/main/org/jaxen/jdom/DocumentNavigator.java:import org.jdom.ProcessingInstruction;
> src/java/main/org/jaxen/jdom/DocumentNavigator.java:import org.jdom.Text;
> src/java/main/org/jaxen/jdom/DocumentNavigator.java:import org.jdom.input.SAXBuilder;
> src/java/main/org/jaxen/jdom/XPathNamespace.java:import org.jdom.Element;
> src/java/main/org/jaxen/jdom/XPathNamespace.java:import org.jdom.Namespace;
> {code}
> DocumentNavigator is nowhere used by WF or its libraries. XPathNamespace is only used by DocumentNavigator. So, our uses of jaxen don't require jdom. That dependency should be optional so galleon can skip provisioning it in optimized installations.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months