April 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24348) Docker New and Noteworthy for 4.4.4.Final

by Jeff Johnston (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24348?page=com.atlassian.jira.plugi... ] Jeff Johnston closed JBIDE-24348. --------------------------------- Resolution: Rejected > Docker New and Noteworthy for 4.4.4.Final > ----------------------------------------------------- > > Key: JBIDE-24348 > URL: https://issues.jboss.org/browse/JBIDE-24348 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: docker > Reporter: Jeff MAURY > Assignee: Jeff Johnston > Priority: Critical > > Jeff Johnston, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Docker 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 Docker, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Docker 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 Docker 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 Docker 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 Docker, 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

1
0
0 / 0

[JBoss JIRA] (JBDS-4284) migrate _master jobs to CCI

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4284?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4284: ---------------------------------- Migrated these jobs: * buildflow x 2 * composite * core, coretests, central/EA * versionwatch * integration tests * parent * discovery * locus * tycho plugins Left to do (23 jobs): * jbosstools-* projects (including browsersim-standalone & templates) = 19 * openshift rest client * java-lang-server * reddeer x 2 > migrate _master jobs to CCI > --------------------------- > > Key: JBDS-4284 > URL: https://issues.jboss.org/browse/JBDS-4284 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Sub-task > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 11.0.0.AM1 > > > Migrate all jobs in this view to CCI: > http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24368) Visual Editor New and Noteworthy for 4.4.4.Final

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24368?page=com.atlassian.jira.plugi... ] Ilya Buziuk updated JBIDE-24368: -------------------------------- Fix Version/s: 4.4.4.Final > Visual Editor New and Noteworthy for 4.4.4.Final > ----------------------------------------------------- > > Key: JBIDE-24368 > URL: https://issues.jboss.org/browse/JBIDE-24368 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: visual-page-editor-core, visual-page-editor-templates > Reporter: Jeff MAURY > Assignee: Ilya Buziuk > Priority: Critical > Fix For: 4.4.4.Final > > > Ilya Buziuk, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Visual Editor 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 Visual Editor, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Visual Editor 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 Visual Editor 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 Visual Editor 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 Visual Editor, 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-24368) Visual Editor New and Noteworthy for 4.4.4.Final

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24368?page=com.atlassian.jira.plugi... ] Ilya Buziuk closed JBIDE-24368. ------------------------------- Resolution: Rejected No N&N for 4.4.4.Final > Visual Editor New and Noteworthy for 4.4.4.Final > ----------------------------------------------------- > > Key: JBIDE-24368 > URL: https://issues.jboss.org/browse/JBIDE-24368 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: visual-page-editor-core, visual-page-editor-templates > Reporter: Jeff MAURY > Assignee: Ilya Buziuk > Priority: Critical > Fix For: 4.4.4.Final > > > Ilya Buziuk, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Visual Editor 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 Visual Editor, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Visual Editor 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 Visual Editor 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 Visual Editor 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 Visual Editor, 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-24356) BrowserSim New and Noteworthy for 4.4.4.Final

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24356?page=com.atlassian.jira.plugi... ] Ilya Buziuk closed JBIDE-24356. ------------------------------- Resolution: Rejected No N&N for 4.4.4.Final > BrowserSim New and Noteworthy for 4.4.4.Final > ----------------------------------------------------- > > Key: JBIDE-24356 > URL: https://issues.jboss.org/browse/JBIDE-24356 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: browsersim > Reporter: Jeff MAURY > Assignee: Ilya Buziuk > Priority: Critical > Fix For: 4.4.4.Final > > > Ilya Buziuk, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed BrowserSim 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 BrowserSim, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for BrowserSim 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 BrowserSim 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 BrowserSim 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 BrowserSim, 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-24356) BrowserSim New and Noteworthy for 4.4.4.Final

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24356?page=com.atlassian.jira.plugi... ] Ilya Buziuk updated JBIDE-24356: -------------------------------- Fix Version/s: 4.4.4.Final > BrowserSim New and Noteworthy for 4.4.4.Final > ----------------------------------------------------- > > Key: JBIDE-24356 > URL: https://issues.jboss.org/browse/JBIDE-24356 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: browsersim > Reporter: Jeff MAURY > Assignee: Ilya Buziuk > Priority: Critical > Fix For: 4.4.4.Final > > > Ilya Buziuk, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed BrowserSim 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 BrowserSim, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for BrowserSim 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 BrowserSim 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 BrowserSim 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 BrowserSim, 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

1
0
0 / 0

[JBoss JIRA] (JBDS-4377) installer jar does not contain both the patched and unpatched version of org.eclipse.wst.common.modulecore

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4377?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4377: ----------------------------- Workaround Description: List all three IUs when installing via commanline: {code}... -i com.jboss.devstudio.core.package,org.testng.eclipse.feature.group,org.eclipse.wst.common_core_EBZ511793.feature.patch.feature.group ... {code} Workaround: Workaround Exists > installer jar does not contain both the patched and unpatched version of org.eclipse.wst.common.modulecore > ---------------------------------------------------------------------------------------------------------- > > Key: JBDS-4377 > URL: https://issues.jboss.org/browse/JBDS-4377 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build, installer, target-platform > Affects Versions: 10.4.0.AM3 > Environment: Windows: DevSuite Installer v1.4 AM3 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 10.4.0.GA > > Attachments: devstudio104am3-installer-missing-unpatched-plugin.png > > > Denis reports a problem using the installer jar in automated mode (using .xml script). > Works fine when run `java -jar \*installer\*.jar` and `echo 1 | java -jar \*installer\*.jar -console` but fails when run against an xml install script. > Seems to be caused by the fact that the installer only contains the patched version of org.eclipse.wst.common.modulecore 1.2.501, and not the 1.2.500 version that's in the TP as well. > !devstudio104am3-installer-missing-unpatched-plugin.png|thumbnail! > So we need to figure out how to include BOTH versions in the installer jar. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4377) installer jar does not contain both the patched and unpatched version of org.eclipse.wst.common.modulecore

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4377?page=com.atlassian.jira.plugin.... ] Nick Boldt reassigned JBDS-4377: -------------------------------- Assignee: Denis Golovin (was: Nick Boldt) > installer jar does not contain both the patched and unpatched version of org.eclipse.wst.common.modulecore > ---------------------------------------------------------------------------------------------------------- > > Key: JBDS-4377 > URL: https://issues.jboss.org/browse/JBDS-4377 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build, installer, target-platform > Affects Versions: 10.4.0.AM3 > Environment: Windows: DevSuite Installer v1.4 AM3 > Reporter: Nick Boldt > Assignee: Denis Golovin > Fix For: 10.4.0.GA > > Attachments: devstudio104am3-installer-missing-unpatched-plugin.png > > > Denis reports a problem using the installer jar in automated mode (using .xml script). > Works fine when run `java -jar \*installer\*.jar` and `echo 1 | java -jar \*installer\*.jar -console` but fails when run against an xml install script. > Seems to be caused by the fact that the installer only contains the patched version of org.eclipse.wst.common.modulecore 1.2.501, and not the 1.2.500 version that's in the TP as well. > !devstudio104am3-installer-missing-unpatched-plugin.png|thumbnail! > So we need to figure out how to include BOTH versions in the installer jar. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4377) installer jar does not contain both the patched and unpatched version of org.eclipse.wst.common.modulecore

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4377?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4377: ----------------------------- Issue Type: Bug (was: Feature Request) > installer jar does not contain both the patched and unpatched version of org.eclipse.wst.common.modulecore > ---------------------------------------------------------------------------------------------------------- > > Key: JBDS-4377 > URL: https://issues.jboss.org/browse/JBDS-4377 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build, installer, target-platform > Affects Versions: 10.4.0.AM3 > Environment: Windows: DevSuite Installer v1.4 AM3 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 10.4.0.GA > > Attachments: devstudio104am3-installer-missing-unpatched-plugin.png > > > Denis reports a problem using the installer jar in automated mode (using .xml script). > Works fine when run `java -jar \*installer\*.jar` and `echo 1 | java -jar \*installer\*.jar -console` but fails when run against an xml install script. > Seems to be caused by the fact that the installer only contains the patched version of org.eclipse.wst.common.modulecore 1.2.501, and not the 1.2.500 version that's in the TP as well. > !devstudio104am3-installer-missing-unpatched-plugin.png|thumbnail! > So we need to figure out how to include BOTH versions in the installer jar. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4364) Conflict org.testng.eclipse 6.9.13. vs 6.11.0.

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4364?page=com.atlassian.jira.plugin.... ] Nick Boldt reassigned JBDS-4364: -------------------------------- Assignee: Lukáš Valach (was: Nick Boldt) > Conflict org.testng.eclipse 6.9.13. vs 6.11.0. > ---------------------------------------------- > > Key: JBDS-4364 > URL: https://issues.jboss.org/browse/JBDS-4364 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: rpm > Affects Versions: 10.4.0.AM3 > Environment: OS: RHEL7 > RHSCL: http://download.eng.brq.redhat.com/rel-eng/RHSCL-2.4-RHEL-7-RC-1.0/compos... > Devstudio: rh-eclipse46-devstudio 10.4-0.20170421.0123.el7 > Reporter: Lukáš Valach > Assignee: Lukáš Valach > Fix For: 10.4.0.GA > > > It is possible to update TestNG via RH Central. > # RH Central -> Software/Update > # Enable Early Access > # *Show installed* > # Find "TestNG" there is written "Installed, update available" > # Select TestNG and install updates > # Restart > # Then this error message will appear in the log: > {code} > !ENTRY org.testng.eclipse 4 0 2017-04-21 05:21:07.715 > !MESSAGE FrameworkEvent ERROR > !STACK 0 > org.osgi.framework.BundleException: Could not resolve module: org.testng.eclipse [1649] > Another singleton bundle selected: osgi.identity; osgi.identity="org.testng.eclipse"; type="osgi.bundle"; version:Version="6.11.0.201703011520"; singleton:="true" > {code} > Log: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > Central constains org.testng.eclipse 6.11.0.201703011520, RPM contains 6.9.13.201701201452. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues April 2017