[JBoss JIRA] (JBIDE-24352) Aerogear New and Noteworthy for 4.4.4.Final
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24352?page=com.atlassian.jira.plugi... ]
Jeff MAURY commented on JBIDE-24352:
------------------------------------
[~gercan] can you process it ?
> Aerogear New and Noteworthy for 4.4.4.Final
> -----------------------------------------------------
>
> Key: JBIDE-24352
> URL: https://issues.jboss.org/browse/JBIDE-24352
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: aerogear-hybrid, cordovasim
> Reporter: Jeff MAURY
> Assignee: Gorkem Ercan
> Priority: Critical
>
> 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-24345 #comment Create N&N for Aerogear 4.4.4.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.4.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.4.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.4.Final.adoc file, adding: {code}page-include-previous: false{code}.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBDS-4385) For JBDS 10.4.0.GA: Find Missing Commits From master for jbosstools-4.4.x
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBDS-4385?page=com.atlassian.jira.plugin.... ]
Jeff MAURY commented on JBDS-4385:
----------------------------------
[~dgolovin] can you process it ?
> For JBDS 10.4.0.GA: Find Missing Commits From master for jbosstools-4.4.x
> -------------------------------------------------------------------------
>
> Key: JBDS-4385
> URL: https://issues.jboss.org/browse/JBDS-4385
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Task
> Components: installer
> Reporter: Jeff MAURY
> Assignee: Denis Golovin
> Priority: Blocker
> Labels: task
> Fix For: 10.4.0.GA
>
>
> For JBDS 10.4.0.GA: Ensure all commits pushed to master have either been made in jbosstools-4.4.x, or are intentionally excluded from jbosstools-4.4.x.
> Below are listed all commits made to master that have not been found in jbosstools-4.4.x. It is possible these commits do exist in jbosstools-4.4.x, but the patches are not identical. It is also possible that the commits made in master are not relevant to jbosstools-4.4.x or should not be applied.
> If there are no commits listed below, please close (do not resolve) this issue.
> Otherwise:
> 1) Click on each link below.
> 2) Evaluate whether the given commit *should* be in jbosstools-4.4.x
> 3) If it should be in jbosstools-4.4.x, please find out why it is not in jbosstools-4.4.x. You may need to browse jbosstools-4.4.x's commit log to find a commit that should match.
> 4) If you cannot find a matching commit, and it *should* be committed to jbosstools-4.4.x, please cherry-pick that commit to jbosstools-4.4.x or otherwise merge it in.
> 5) In comments, please indicate any suspicious commits (ie, commits not related to simple version changes), whether it exists in jbosstools-4.4.x, whether you have successfully merged it in now, or whether it is not intended to be committed to jbosstools-4.4.x or is inappropriate for jbosstools-4.4.x.
> 6) When all complete, please close (do not resolve) this issue.
>
> [Search for all task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBDS-4385) For JBDS 10.4.0.GA: Find Missing Commits From master for jbosstools-4.4.x
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBDS-4385?page=com.atlassian.jira.plugin.... ]
Jeff MAURY reassigned JBDS-4385:
--------------------------------
Assignee: Denis Golovin (was: Jeff MAURY)
> For JBDS 10.4.0.GA: Find Missing Commits From master for jbosstools-4.4.x
> -------------------------------------------------------------------------
>
> Key: JBDS-4385
> URL: https://issues.jboss.org/browse/JBDS-4385
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Task
> Components: installer
> Reporter: Jeff MAURY
> Assignee: Denis Golovin
> Priority: Blocker
> Labels: task
> Fix For: 10.4.0.GA
>
>
> For JBDS 10.4.0.GA: Ensure all commits pushed to master have either been made in jbosstools-4.4.x, or are intentionally excluded from jbosstools-4.4.x.
> Below are listed all commits made to master that have not been found in jbosstools-4.4.x. It is possible these commits do exist in jbosstools-4.4.x, but the patches are not identical. It is also possible that the commits made in master are not relevant to jbosstools-4.4.x or should not be applied.
> If there are no commits listed below, please close (do not resolve) this issue.
> Otherwise:
> 1) Click on each link below.
> 2) Evaluate whether the given commit *should* be in jbosstools-4.4.x
> 3) If it should be in jbosstools-4.4.x, please find out why it is not in jbosstools-4.4.x. You may need to browse jbosstools-4.4.x's commit log to find a commit that should match.
> 4) If you cannot find a matching commit, and it *should* be committed to jbosstools-4.4.x, please cherry-pick that commit to jbosstools-4.4.x or otherwise merge it in.
> 5) In comments, please indicate any suspicious commits (ie, commits not related to simple version changes), whether it exists in jbosstools-4.4.x, whether you have successfully merged it in now, or whether it is not intended to be committed to jbosstools-4.4.x or is inappropriate for jbosstools-4.4.x.
> 6) When all complete, please close (do not resolve) this issue.
>
> [Search for all task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBTIS-1105) Fix tests for Camel configurations tab
by Dominik Jelinek (JIRA)
[ https://issues.jboss.org/browse/JBTIS-1105?page=com.atlassian.jira.plugin... ]
Dominik Jelinek updated JBTIS-1105:
-----------------------------------
Description:
{code:java}
ConfigurationsEditorDataFormatsTest.testDataFormatAvailability:186 gzip - GZip compression data format
ConfigurationsEditorDataFormatsTest.testDataFormatAvailability:186 json-johnzon - Camel Johnzon support
ConfigurationsEditorDataFormatsTest.testDataFormatAvailability:186 protobuf - Camel Google Protobuf data format support
ConfigurationsEditorDataFormatsTest.testDataFormatAvailability:186 serialization - Java Object Serialization data format
ConfigurationsEditorDataFormatsTest.testDataFormatAvailability:186 string - String (text based) data format
ConfigurationsEditorDataFormatsTest.testDataFormatAvailability:186 zip - Zip compression data format (not for zip files)
ConfigurationsEditorDataFormatsTest.testSourceXML:302 zipfile - Camel Zip file support
{code}
{code:java}
ConfigurationsEditorEndpointsTest.testEditEndpoint:247 CXF - The cxf component is used for SOAP WebServices using Apache CXF.
ConfigurationsEditorEndpointsTest.testCreateEndpoint:212 IMAPS - To send or receive emails using imap/pop3 or stmp protocols.
ConfigurationsEditorEndpointsTest.testCreateEndpoint:212 JDBC - The jdbc component enables you to access databases through JDBC where SQL queries are sent in the message body.
ConfigurationsEditorEndpointsTest.testEditEndpoint:247 Linkedin - The linkedin component is uses for retrieving LinkedIn user profiles connections companies groups posts etc.
ConfigurationsEditorEndpointsTest.testCreateEndpoint:212 Linkedin - The linkedin component is uses for retrieving LinkedIn user profiles connections companies groups posts etc.
ConfigurationsEditorEndpointsTest.testEditEndpoint:247 MVEL - Transforms the message using a MVEL template.
ConfigurationsEditorEndpointsTest.testCreateEndpoint:212 Quartz2 - Provides a scheduled delivery of messages using the Quartz 2.x scheduler.
ConfigurationsEditorEndpointsTest.testCreateEndpoint:212 SFTP - The sftp (FTP over SSH) component is used for uploading or downloading files from SFTP servers.
ConfigurationsEditorEndpointsTest.testEndpointAvailability:188 SQL - The sql component allows you to work with databases using JDBC Stored Procedure queries.
{code}
was:
ConfigurationsEditorDataFormatsTest.testDataFormatAvailability:186 gzip - GZip compression data format
ConfigurationsEditorDataFormatsTest.testDataFormatAvailability:186 json-johnzon - Camel Johnzon support
ConfigurationsEditorDataFormatsTest.testDataFormatAvailability:186 protobuf - Camel Google Protobuf data format support
ConfigurationsEditorDataFormatsTest.testDataFormatAvailability:186 serialization - Java Object Serialization data format
ConfigurationsEditorDataFormatsTest.testDataFormatAvailability:186 string - String (text based) data format
ConfigurationsEditorDataFormatsTest.testDataFormatAvailability:186 zip - Zip compression data format (not for zip files)
ConfigurationsEditorDataFormatsTest.testSourceXML:302 zipfile - Camel Zip file support
ConfigurationsEditorEndpointsTest.testEditEndpoint:247 CXF - The cxf component is used for SOAP WebServices using Apache CXF.
ConfigurationsEditorEndpointsTest.testCreateEndpoint:212 IMAPS - To send or receive emails using imap/pop3 or stmp protocols.
ConfigurationsEditorEndpointsTest.testCreateEndpoint:212 JDBC - The jdbc component enables you to access databases through JDBC where SQL queries are sent in the message body.
ConfigurationsEditorEndpointsTest.testEditEndpoint:247 Linkedin - The linkedin component is uses for retrieving LinkedIn user profiles connections companies groups posts etc.
ConfigurationsEditorEndpointsTest.testCreateEndpoint:212 Linkedin - The linkedin component is uses for retrieving LinkedIn user profiles connections companies groups posts etc.
ConfigurationsEditorEndpointsTest.testEditEndpoint:247 MVEL - Transforms the message using a MVEL template.
ConfigurationsEditorEndpointsTest.testCreateEndpoint:212 Quartz2 - Provides a scheduled delivery of messages using the Quartz 2.x scheduler.
ConfigurationsEditorEndpointsTest.testCreateEndpoint:212 SFTP - The sftp (FTP over SSH) component is used for uploading or downloading files from SFTP servers.
ConfigurationsEditorEndpointsTest.testEndpointAvailability:188 SQL - The sql component allows you to work with databases using JDBC Stored Procedure queries.
> Fix tests for Camel configurations tab
> --------------------------------------
>
> Key: JBTIS-1105
> URL: https://issues.jboss.org/browse/JBTIS-1105
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: Fuse IDE, QE
> Affects Versions: 4.4.3.CR1
> Environment: 10.3.0.CR1-v20170429-2214-B9
> Reporter: Dominik Jelinek
> Assignee: Dominik Jelinek
> Fix For: 4.4.3.Final
>
>
> {code:java}
> ConfigurationsEditorDataFormatsTest.testDataFormatAvailability:186 gzip - GZip compression data format
> ConfigurationsEditorDataFormatsTest.testDataFormatAvailability:186 json-johnzon - Camel Johnzon support
> ConfigurationsEditorDataFormatsTest.testDataFormatAvailability:186 protobuf - Camel Google Protobuf data format support
> ConfigurationsEditorDataFormatsTest.testDataFormatAvailability:186 serialization - Java Object Serialization data format
> ConfigurationsEditorDataFormatsTest.testDataFormatAvailability:186 string - String (text based) data format
> ConfigurationsEditorDataFormatsTest.testDataFormatAvailability:186 zip - Zip compression data format (not for zip files)
> ConfigurationsEditorDataFormatsTest.testSourceXML:302 zipfile - Camel Zip file support
> {code}
> {code:java}
> ConfigurationsEditorEndpointsTest.testEditEndpoint:247 CXF - The cxf component is used for SOAP WebServices using Apache CXF.
> ConfigurationsEditorEndpointsTest.testCreateEndpoint:212 IMAPS - To send or receive emails using imap/pop3 or stmp protocols.
> ConfigurationsEditorEndpointsTest.testCreateEndpoint:212 JDBC - The jdbc component enables you to access databases through JDBC where SQL queries are sent in the message body.
> ConfigurationsEditorEndpointsTest.testEditEndpoint:247 Linkedin - The linkedin component is uses for retrieving LinkedIn user profiles connections companies groups posts etc.
> ConfigurationsEditorEndpointsTest.testCreateEndpoint:212 Linkedin - The linkedin component is uses for retrieving LinkedIn user profiles connections companies groups posts etc.
> ConfigurationsEditorEndpointsTest.testEditEndpoint:247 MVEL - Transforms the message using a MVEL template.
> ConfigurationsEditorEndpointsTest.testCreateEndpoint:212 Quartz2 - Provides a scheduled delivery of messages using the Quartz 2.x scheduler.
> ConfigurationsEditorEndpointsTest.testCreateEndpoint:212 SFTP - The sftp (FTP over SSH) component is used for uploading or downloading files from SFTP servers.
> ConfigurationsEditorEndpointsTest.testEndpointAvailability:188 SQL - The sql component allows you to work with databases using JDBC Stored Procedure queries.
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBTIS-1107) Revision of JBTIS-758, it fails only on fedora24
by Dominik Jelinek (JIRA)
Dominik Jelinek created JBTIS-1107:
--------------------------------------
Summary: Revision of JBTIS-758, it fails only on fedora24
Key: JBTIS-1107
URL: https://issues.jboss.org/browse/JBTIS-1107
Project: JBoss Tools Integration Stack
Issue Type: Task
Components: Fuse IDE, QE
Affects Versions: 4.4.3.CR1
Reporter: Dominik Jelinek
Assignee: Andrej Podhradsky
JBTIS-758: Add test for collapse/expand feature in Camel Editor
* test passed on fedora25, win10 and mac, but only on fedora24 (verification job) it still fails
the verification job has failed due to
{code:java}
Error Message
expected:<34> but was:<228>
Stacktrace
java.lang.AssertionError: expected:<34> but was:<228>
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:834)
at org.junit.Assert.assertEquals(Assert.java:645)
at org.junit.Assert.assertEquals(Assert.java:631)
at org.jboss.tools.fuse.ui.bot.test.CamelEditorTest.testCollapseExpandFeature(CamelEditorTest.java:291)
{code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBTIS-1106) Create structure for using different versions of Camel catalog in tests
by Dominik Jelinek (JIRA)
Dominik Jelinek created JBTIS-1106:
--------------------------------------
Summary: Create structure for using different versions of Camel catalog in tests
Key: JBTIS-1106
URL: https://issues.jboss.org/browse/JBTIS-1106
Project: JBoss Tools Integration Stack
Issue Type: Task
Components: Fuse IDE, QE
Affects Versions: 4.4.3.CR1
Reporter: Dominik Jelinek
Assignee: Dominik Jelinek
For example, when develop test for Camel editor (Configurations tab), there are available different components (endpoints, data formats) for different Camel versions (different camel catalogs) ...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months