[JBoss JIRA] (JBIDE-23975) Aerogear New and Noteworthy for 4.4.3.Final
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23975?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-23975:
-------------------------------
Fix Version/s: 4.4.3.Final
> Aerogear New and Noteworthy for 4.4.3.Final
> -----------------------------------------------------
>
> Key: JBIDE-23975
> URL: https://issues.jboss.org/browse/JBIDE-23975
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: aerogear-hybrid, cordovasim
> Reporter: Jeff MAURY
> Assignee: Gorkem Ercan
> Priority: Critical
> Fix For: 4.4.3.Final
>
>
> Gorkem Ercan,
> Search for your component's New and Noteworthy issues:
> Queries:
> * [Completed Aerogear JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...]
> * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...]
> * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...]
> * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...]
> If no N&N issues are found for Aerogear, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them.
> Document the ones relevant for Aerogear by submitting a pull request against:
> * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio...
> If your PR's commit comment is of the form... {code}JBIDE-23968 #comment Create N&N for Aerogear 4.4.3.Final #close{code}... and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied.
> If there is nothing new or noteworthy for Aerogear for this milestone, please *reject* and *close* this issue.
> ----
> If there is nothing new or noteworthy for 4.4.3.Final since the AM3 release of Aerogear, please *reject* and *close* this issue. The final N&N page will be aggregated from all previous N&N documents.
> If you want to _add a comment to the final document_ then submit a PR to create a separate <component>-news-4.4.3.Final.adoc file here:
> * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio...
> The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc.
> However, if you want to _replace all previous N&Ns by a *new* document_, then submit a PR to create a *new* <component>-news-4.4.3.Final.adoc file, adding: {code}page-include-previous: false{code}.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBIDE-23981) Central New and Noteworthy for 4.4.3.Final
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23981?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-23981:
-------------------------------
Fix Version/s: 4.4.3.Final
> Central New and Noteworthy for 4.4.3.Final
> -----------------------------------------------------
>
> Key: JBIDE-23981
> URL: https://issues.jboss.org/browse/JBIDE-23981
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: central, maven, project-examples
> Reporter: Jeff MAURY
> Assignee: Fred Bricon
> Priority: Critical
> Fix For: 4.4.3.Final
>
>
> Fred Bricon,
> Search for your component's New and Noteworthy issues:
> Queries:
> * [Completed Central JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...]
> * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...]
> * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...]
> * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...]
> If no N&N issues are found for Central, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them.
> Document the ones relevant for Central by submitting a pull request against:
> * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio...
> If your PR's commit comment is of the form... {code}JBIDE-23968 #comment Create N&N for Central 4.4.3.Final #close{code}... and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied.
> If there is nothing new or noteworthy for Central for this milestone, please *reject* and *close* this issue.
> ----
> If there is nothing new or noteworthy for 4.4.3.Final since the AM3 release of Central, please *reject* and *close* this issue. The final N&N page will be aggregated from all previous N&N documents.
> If you want to _add a comment to the final document_ then submit a PR to create a separate <component>-news-4.4.3.Final.adoc file here:
> * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio...
> The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc.
> However, if you want to _replace all previous N&Ns by a *new* document_, then submit a PR to create a *new* <component>-news-4.4.3.Final.adoc file, adding: {code}page-include-previous: false{code}.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBIDE-23869) ClassCastException with Jolokia connection
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23869?page=com.atlassian.jira.plugi... ]
Jeff MAURY commented on JBIDE-23869:
------------------------------------
This is an upstream problem. The JSON payload is generated by OpenShift (because you're not authorized) and assumes the status field is always an integer. I opened an upstream issue.
> ClassCastException with Jolokia connection
> ------------------------------------------
>
> Key: JBIDE-23869
> URL: https://issues.jboss.org/browse/JBIDE-23869
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jmx, openshift
> Reporter: Aurélien Pupier
> Assignee: Jeff MAURY
> Labels: jmx, jolokia, openshift
> Fix For: 4.4.4.AM1
>
> Attachments: image-2017-02-06-13-54-27-708.png
>
>
> !image-2017-02-06-13-54-27-708.png|thumbnail!
> {noformat}
> !ENTRY org.eclipse.core.jobs 4 2 2017-02-06 13:52:39.767
> !MESSAGE An internal error occurred during: "Connect Job".
> !STACK 0
> java.lang.ClassCastException: java.lang.String cannot be cast to java.lang.Long
> at org.jolokia.client.request.ValidatingResponseExtractor.extract(ValidatingResponseExtractor.java:58)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:195)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:168)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:117)
> at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:315)
> at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.connect(JolokiaConnectionWrapper.java:111)
> at org.jboss.tools.jmx.core.ConnectJob.run(ConnectJob.java:29)
> at org.jboss.tools.jmx.ui.internal.actions.DoubleClickAction$1.run(DoubleClickAction.java:71)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBTIS-1051) Return CDI features to JBTIS TP for use by SwitchYard/Fuse Tooling
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-1051?page=com.atlassian.jira.plugin... ]
Paul Leacu updated JBTIS-1051:
------------------------------
Description:
The effort to remove unneeded JBT core requirements removed CDI which is needed by SwitchYard. Return:
org.jboss.tools.cdi.deltaspike.feature.feature.group
org.jboss.tools.cdi.feature.feature.group
org.jboss.tools.cdi.seam.feature.feature.group
ref:
Fuse Tooling there are 3 git repos:
- Fuse Tooling itself
- SAP Tooling, because it contains proprietary dependencies
- SwitchYard Tooling because historically a different project and it enters in maintenance mode so we don't make an effort to merge it with Fuse Tooling git repository
*Reason:* Replace removed CDI dependencies
*Project page/sources:*
*Version:* 4.4.2.AM1
*License and owner:* EPL
*Original p2 repo:*
*JBoss mirror:*
*Include Sources:* Yes
*Affected JBoss Tools components:Integration Stack
*Include in JBDS:* Yes
*Type of dependency:* testing|central-only|distribution
*List of bundles added/removed:*
{code}
{code}
was:
The effort to remove unneeded JBT core requirements removed CDI which is needed by SwitchYard. Return:
org.jboss.tools.cdi.deltaspike.feature.feature.group
org.jboss.tools.cdi.feature.feature.group
org.jboss.tools.cdi.seam.feature.feature.group
ref:
Fuse Tooling there are 3 git repos:
- Fuse Tooling itself
- SAP Tooling, because it contains proprietary dependencies
- SwitchYard Tooling because historically a different project and it enters in maintenance mode so we don't make an effort to merge it with Fuse Tooling git repository
> Return CDI features to JBTIS TP for use by SwitchYard/Fuse Tooling
> ------------------------------------------------------------------
>
> Key: JBTIS-1051
> URL: https://issues.jboss.org/browse/JBTIS-1051
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: target-platform
> Affects Versions: 10.2.0.CR1, 4.4.2.CR1
> Reporter: Paul Leacu
> Assignee: Paul Leacu
> Priority: Blocker
>
> The effort to remove unneeded JBT core requirements removed CDI which is needed by SwitchYard. Return:
> org.jboss.tools.cdi.deltaspike.feature.feature.group
> org.jboss.tools.cdi.feature.feature.group
> org.jboss.tools.cdi.seam.feature.feature.group
> ref:
> Fuse Tooling there are 3 git repos:
> - Fuse Tooling itself
> - SAP Tooling, because it contains proprietary dependencies
> - SwitchYard Tooling because historically a different project and it enters in maintenance mode so we don't make an effort to merge it with Fuse Tooling git repository
> *Reason:* Replace removed CDI dependencies
> *Project page/sources:*
> *Version:* 4.4.2.AM1
> *License and owner:* EPL
> *Original p2 repo:*
> *JBoss mirror:*
> *Include Sources:* Yes
> *Affected JBoss Tools components:Integration Stack
> *Include in JBDS:* Yes
> *Type of dependency:* testing|central-only|distribution
> *List of bundles added/removed:*
> {code}
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBTIS-1051) Return CDI features to JBTIS TP for use by SwitchYard/Fuse Tooling
by Paul Leacu (JIRA)
Paul Leacu created JBTIS-1051:
---------------------------------
Summary: Return CDI features to JBTIS TP for use by SwitchYard/Fuse Tooling
Key: JBTIS-1051
URL: https://issues.jboss.org/browse/JBTIS-1051
Project: JBoss Tools Integration Stack
Issue Type: Bug
Components: target-platform
Affects Versions: 10.2.0.CR1, 4.4.2.CR1
Reporter: Paul Leacu
Assignee: Paul Leacu
Priority: Blocker
The effort to remove unneeded JBT core requirements removed CDI which is needed by SwitchYard. Return:
org.jboss.tools.cdi.deltaspike.feature.feature.group
org.jboss.tools.cdi.feature.feature.group
org.jboss.tools.cdi.seam.feature.feature.group
ref:
Fuse Tooling there are 3 git repos:
- Fuse Tooling itself
- SAP Tooling, because it contains proprietary dependencies
- SwitchYard Tooling because historically a different project and it enters in maintenance mode so we don't make an effort to merge it with Fuse Tooling git repository
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBTIS-1050) Move MWAE Jenkins jobs to Central CI
by Paul Leacu (JIRA)
Paul Leacu created JBTIS-1050:
---------------------------------
Summary: Move MWAE Jenkins jobs to Central CI
Key: JBTIS-1050
URL: https://issues.jboss.org/browse/JBTIS-1050
Project: JBoss Tools Integration Stack
Issue Type: Task
Components: distribution
Affects Versions: 10.0.0.GA
Reporter: Paul Leacu
Assignee: Paul Leacu
The middleware Jenkins jobs need to be mograted to Central CI
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months