[JBoss JIRA] (WFLY-11646) Upgrade antlr to more current release
by Scott Marlow (Jira)
[ https://issues.jboss.org/browse/WFLY-11646?page=com.atlassian.jira.plugin... ]
Scott Marlow resolved WFLY-11646.
---------------------------------
Resolution: Rejected
[~zabee] thanks for reporting this issue, good to bring awareness to the need (e.g. improvements in newer Antlr for running under Java security manager).
The Hibernate master branch is still using Antlr 2.7.7. Despite the comments in [HHH -10028|https://hibernate.atlassian.net/browse/HHH-10028], typically the Hibernate project does an upgrade first, during an upstream (e.g. latest [http://github.com/hibernate/hibernate-orm] master branch) and WildFly does a subsequent upgrade later when integrating the released Hibernate ORM release into WildFly.
The reasoning is that the Hibernate project contains the unit tests that must prove that the upgraded Antlr libraries, still work correctly.
If you feel like contributing to Hibernate, you could clone the [http://github.com/hibernate/hibernate-orm], upgrade the ANTLR version (in Hibernate gradle/libraries.gradle) and run tests (via something like /gradlew clean publishToMavenLocal test). Also see the [http://hibernate.org/orm/contribute/] about how to contribute to Hibernate.
I'm closing this issue since we cannot upgrade the Antlr version until Hibernate ORM has upgraded to it. After Hibernate ORM (master branch) has upgraded to the newer Antlr version, please reopen this jira, so we can track the issue.
> Upgrade antlr to more current release
> -------------------------------------
>
> Key: WFLY-11646
> URL: https://issues.jboss.org/browse/WFLY-11646
> Project: WildFly
> Issue Type: Component Upgrade
> Components: JPA / Hibernate
> Reporter: Zabee Ulla
> Assignee: Scott Marlow
> Priority: Minor
>
> As per the bug that was reported here - https://hibernate.atlassian.net/browse/HHH-10028, Hibernate stays in-step with Wildfly and EAP dependency versions to ensure compatibility.
> This task is a request to upgrade antlr to its latest version available against WildFly so that Hibernate also can pick the latest to be in synch with WildFly.
> Hibernate (hibernate-core to be more specific) latest version is still using antlr version 2.7.7 released on Jan 13, 2007. The latest available, built and maintained version is antlr-4-Runtime 4.7.2. Another reason for going with latest of antlr is to avoid any security vulnerabilities that the library is exposed to.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (SWSQE-557) Kiali-on-Openshift - Support Section To Rebase PR With Master Or Not
by Matt Mahoney (Jira)
[ https://issues.jboss.org/browse/SWSQE-557?page=com.atlassian.jira.plugin.... ]
Matt Mahoney closed SWSQE-557.
------------------------------
Resolution: Done
> Kiali-on-Openshift - Support Section To Rebase PR With Master Or Not
> --------------------------------------------------------------------
>
> Key: SWSQE-557
> URL: https://issues.jboss.org/browse/SWSQE-557
> Project: Kiali QE
> Issue Type: QE Task
> Reporter: Matt Mahoney
> Assignee: Michael Foley
> Priority: Major
>
> With the Kiali build strategy now changed to rebase the PR with Master prior to the build, there is a developer request for the Jenkins build job to have a selection to NOT do the PR rebase with master.
> The reason for this request is for those PRs such as kieli-ui 864 (React lib upgrade) where the developer has no way to validate that the build/deployed-kiali is for that PR, because the kiali-ui version will not match any PR commits tags + no new visual differences in the UI.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (DROOLS-3667) [DMN Designer] Included Models - Architectural discussions and new UI entity
by Guilherme Carreiro (Jira)
[ https://issues.jboss.org/browse/DROOLS-3667?page=com.atlassian.jira.plugi... ]
Guilherme Carreiro updated DROOLS-3667:
---------------------------------------
Description:
Create a common UI entity, that will be used in the "Included Models" tabs.
Considering Liz mockups:
!1.0.png|thumbnail!
The entity will be something like this:
!1.1.png|thumbnail!
However, consider test scenario context + DMN context to create a reusable entity with appropriate fields.
was:
Create a common UI entity, that will be used in the "Included Models" tabs.
Considering Liz mockups:
!1.0.png|thumbnail!
The entity will be something like this:
!1.1.png|thumbnail!
However, consider test scenario context + DMN context to create a reusable entity with appropriate fields.
⚠️ Notice: This task comprehends changes in the {{DataTypeManager}} and {{DataType}} (adding the new field).
> [DMN Designer] Included Models - Architectural discussions and new UI entity
> ----------------------------------------------------------------------------
>
> Key: DROOLS-3667
> URL: https://issues.jboss.org/browse/DROOLS-3667
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Guilherme Carreiro
> Assignee: Guilherme Carreiro
> Priority: Major
> Labels: drools-tools
> Attachments: 1.0.png, 1.1.png
>
>
> Create a common UI entity, that will be used in the "Included Models" tabs.
> Considering Liz mockups:
> !1.0.png|thumbnail!
> The entity will be something like this:
> !1.1.png|thumbnail!
> However, consider test scenario context + DMN context to create a reusable entity with appropriate fields.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months