[JBoss JIRA] (JBTIS-1137) Update Drools TP for Oxygen
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBTIS-1137?page=com.atlassian.jira.plugin... ]
Andrej Podhradsky closed JBTIS-1137.
------------------------------------
Verified. The Drools plugin now uses JBTIS TP 4.5.1.Final.
> Update Drools TP for Oxygen
> ---------------------------
>
> Key: JBTIS-1137
> URL: https://issues.jboss.org/browse/JBTIS-1137
> Project: JBoss Tools Integration Stack
> Issue Type: Task
> Components: drools/ jBPM
> Affects Versions: 11.1.0.GA
> Reporter: Paul Leacu
> Assignee: Paul Leacu
> Fix For: 4.5.1.Final, 11.1.0.GA
>
>
> Update the Drools IS TP to 4.5.0.Final when available.
> Kris:
> Regarding the target platform, it's fine to update the community master to that (assuming it's a stable / released target platform, not a snapshot). We should have another community release by Aug hopefully ;)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 11 months
[JBoss JIRA] (JBIDE-25306) Remove OpenShift2 plugins and features
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25306?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-25306:
-------------------------------------
[~rpdavis] As I recall, the last time we tried was the change from openshift 1 to openshift 2 (unless you're referring to something else?)
The code base is much more segmented now, and openshift v2 contributed almost all of its functionality through extension points. It had its own core and ui, as well as its own client plugin. So this should be pretty safe, bc the v2 plugins do not contribute any functionality for v3.
[~jkopriva] Can you test the PR? https://github.com/jbosstools/jbosstools-openshift/pull/1633
I manually tested it but i admit I don't cover all usecases, so it'd be best to get a few more eyes on this. That said, I would be very surprised if the removal of v2 broke v3 at all.
> Remove OpenShift2 plugins and features
> --------------------------------------
>
> Key: JBIDE-25306
> URL: https://issues.jboss.org/browse/JBIDE-25306
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: openshift
> Affects Versions: 4.5.1.Final
> Reporter: Jeff MAURY
> Assignee: Nick Boldt
> Fix For: 4.5.2.AM3
>
>
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 11 months
[JBoss JIRA] (JBIDE-24111) Verify EAP 7.1 compatibility from EAP team
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24111?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-24111:
-------------------------------------
EAP 7.1 final has following jars:
jboss-dmr-1.4.1.Final-redhat-1.jar
jboss-logging-3.3.1.Final-redhat-1.jar
jboss-remoting-5.0.5.Final-redhat-1.jar
jboss-threads-2.2.1.Final-redhat-1.jar
wildfly-client-config-1.0.0.Final-redhat-1.jar
wildfly-common-1.2.0.Final-redhat-1.jar
wildfly-controller-client-3.0.10.Final-redhat-1.jar
wildfly-elytron-integration-3.0.10.Final-redhat-1.jar
wildfly-elytron-1.1.7.Final-redhat-1.jar
wildfly-protocol-3.0.10.Final-redhat-1.jar
xnio-api-3.5.4.Final-redhat-1.jar
xnio-nio-3.5.4.Final-redhat-1.jar
This is different than current bundled libs:
- wildfly-controller-client-3.0.8.Final.jar
- wildfly-elytron-1.1.6.Final.jar
- wildfly-protocol-3.0.8.Final.jar
+ wildfly-controller-client-3.0.10.Final.jar
+ wildfly-elytron-1.1.7.Final.jar
+ wildfly-protocol-3.0.10.Final.jar
Since these are all micro changes, it should be fine whether we update or don't update.
> Verify EAP 7.1 compatibility from EAP team
> ------------------------------------------
>
> Key: JBIDE-24111
> URL: https://issues.jboss.org/browse/JBIDE-24111
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.4.4.AM1
> Reporter: Jeff MAURY
> Assignee: Rob Stryker
> Labels: eap, server
> Fix For: 4.5.x
>
>
> We should check the problems got from the EAP team. See linked issues
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 11 months