August 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24797) Code formatter: define and hook code formatting enforcement for github PRs

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24797?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24797: ------------------------------------- Description: Code formatting differs across developers. The most prominent differences I am aware of are * use spaces vs tabs * differences in formatting "if statements" (as displayed [here|https://github.com/jbosstools/jbosstools-openshift/pull/1536/files#d...] : {code} if(XX){ {code} vs {code} if (XX) { {code} * insonsitent code identations like displayed [here|https://github.com/jbosstools/jbosstools-openshift/pull/1535/files#d...] * odd identations of braces for anonymous classes as displayed [here|https://github.com/jbosstools/jbosstools-openshift/pull/1531/files#d...] {code} class Listener { int i = 0; public void method() { } } {code} was: Code formatting differs across developers. The most prominent differences I am aware of are * use spaces vs tabs * differences in formatting "if statements" (as displayed [here|https://github.com/jbosstools/jbosstools-openshift/pull/1536/files#d...] : {code} if(XX){ {code} vs {code} if (XX) { {code} * insonsitent code identations like displayed [here|https://github.com/jbosstools/jbosstools-openshift/pull/1535/files#d...] * odd identations of braces for anonymous classes {code} class Listener { int i = 0; public void method() { } } {code} > Code formatter: define and hook code formatting enforcement for github PRs > -------------------------------------------------------------------------- > > Key: JBIDE-24797 > URL: https://issues.jboss.org/browse/JBIDE-24797 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.5.0.Final > Reporter: Andre Dietisheim > Fix For: 4.5.1.AM1 > > > Code formatting differs across developers. > The most prominent differences I am aware of are > * use spaces vs tabs > * differences in formatting "if statements" (as displayed [here|https://github.com/jbosstools/jbosstools-openshift/pull/1536/files#d...] : > {code} > if(XX){ > {code} > vs > {code} > if (XX) { > {code} > * insonsitent code identations like displayed [here|https://github.com/jbosstools/jbosstools-openshift/pull/1535/files#d...] > * odd identations of braces for anonymous classes as displayed [here|https://github.com/jbosstools/jbosstools-openshift/pull/1531/files#d...] > {code} > class Listener { > int i = 0; > public void method() { > } > } > {code} > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24797) Code formatter: define and hook code formatting enforcement for github PRs

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24797?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24797: ------------------------------------- Description: Code formatting differs across developers. The most prominent differences I am aware of are * use spaces vs tabs * differences in formatting "if statements" (as displayed [here|https://github.com/jbosstools/jbosstools-openshift/pull/1536/files#d...] : {code} if(XX){ {code} vs {code} if (XX) { {code} * insonsitent code identations like displayed [here|https://github.com/jbosstools/jbosstools-openshift/pull/1535/files#d...] * odd identations of braces for anonymous classes {code} class Listener { int i = 0; public void method() { } } {code} was: Code formatting differs across developers. The most prominent differences I am aware of are * use spaces vs tabs * if statements: {code} if(XX){ {code} vs {code} if (XX) { {code} * insonsitent code identations * odd identations of braces for anonymous classes {code} class Listener { int i = 0; public void method() { } } {code} > Code formatter: define and hook code formatting enforcement for github PRs > -------------------------------------------------------------------------- > > Key: JBIDE-24797 > URL: https://issues.jboss.org/browse/JBIDE-24797 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.5.0.Final > Reporter: Andre Dietisheim > Fix For: 4.5.1.AM1 > > > Code formatting differs across developers. > The most prominent differences I am aware of are > * use spaces vs tabs > * differences in formatting "if statements" (as displayed [here|https://github.com/jbosstools/jbosstools-openshift/pull/1536/files#d...] : > {code} > if(XX){ > {code} > vs > {code} > if (XX) { > {code} > * insonsitent code identations like displayed [here|https://github.com/jbosstools/jbosstools-openshift/pull/1535/files#d...] > * odd identations of braces for anonymous classes > {code} > class Listener { > int i = 0; > public void method() { > } > } > {code} > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24652) update target platform & Central to Oxygen.0+

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24652?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-24652: ------------------------------------ Note. Because Oxygen.0 depends on Jetty 9.4.5 and we're including 9.4.6 (CVE fix) therefore there are an extra large number of dupe IUs in the TP: {code} [WARNING] Found 29 duplicate jbosstools plugins: [WARNING] [1] jbosstools-multiple.target.repo/plugins/ch.qos.logback.classic_1.0.7.v20121108-1250.jar [WARNING] [1] jbosstools-multiple.target.repo/plugins/ch.qos.logback.classic_1.1.2.v20160208-0839.jar [WARNING] [2] jbosstools-multiple.target.repo/plugins/ch.qos.logback.core_1.0.7.v20121108-1250.jar [WARNING] [2] jbosstools-multiple.target.repo/plugins/ch.qos.logback.core_1.1.2.v20160208-0839.jar [WARNING] [3] jbosstools-multiple.target.repo/plugins/com.google.guava_21.0.0.v20170206-1425.jar [WARNING] [3] jbosstools-multiple.target.repo/plugins/com.google.guava_18.0.0.v20161115-1643.jar [WARNING] [3] jbosstools-multiple.target.repo/plugins/com.google.guava_15.0.0.v201403281430.jar [WARNING] [4] jbosstools-multiple.target.repo/plugins/javax.wsdl_1.5.1.v201012040544.jar [WARNING] [4] jbosstools-multiple.target.repo/plugins/javax.wsdl_1.6.2.v201012040545.jar [WARNING] [5] jbosstools-multiple.target.repo/plugins/javax.xml.soap_1.2.0.v201005080501.jar [WARNING] [5] jbosstools-multiple.target.repo/plugins/javax.xml.soap_1.3.0.v201105210645.jar [WARNING] [6] jbosstools-multiple.target.repo/plugins/org.apache.batik.css_1.7.0.v201011041433.jar [WARNING] [6] jbosstools-multiple.target.repo/plugins/org.apache.batik.css_1.8.0.v20170214-1941.jar [WARNING] [7] jbosstools-multiple.target.repo/plugins/org.apache.batik.util_1.7.0.v201011041433.jar [WARNING] [7] jbosstools-multiple.target.repo/plugins/org.apache.batik.util_1.8.0.v20170214-1941.jar [WARNING] [8] jbosstools-multiple.target.repo/plugins/org.apache.batik.util.gui_1.8.0.v20170214-1941.jar [WARNING] [8] jbosstools-multiple.target.repo/plugins/org.apache.batik.util.gui_1.7.0.v200903091627.jar [WARNING] [9] jbosstools-multiple.target.repo/plugins/org.apache.commons.codec_1.6.0.v201305230611.jar [WARNING] [9] jbosstools-multiple.target.repo/plugins/org.apache.commons.codec_1.9.0.v20170208-1614.jar [WARNING] [10] jbosstools-multiple.target.repo/plugins/org.apache.commons.logging_1.1.1.v201101211721.jar [WARNING] [10] jbosstools-multiple.target.repo/plugins/org.apache.commons.logging_1.0.4.v201101211617.jar [WARNING] [11] jbosstools-multiple.target.repo/plugins/org.apache.httpcomponents.httpclient_4.5.2.v20170210-0925.jar [WARNING] [11] jbosstools-multiple.target.repo/plugins/org.apache.httpcomponents.httpclient_4.3.6.v201511171540.jar [WARNING] [12] jbosstools-multiple.target.repo/plugins/org.apache.httpcomponents.httpcore_4.4.6.v20170210-0925.jar [WARNING] [12] jbosstools-multiple.target.repo/plugins/org.apache.httpcomponents.httpcore_4.3.3.v201411290715.jar [WARNING] [13] jbosstools-multiple.target.repo/plugins/org.apache.lucene.core_5.2.1.v20160301-1110.jar [WARNING] [13] jbosstools-multiple.target.repo/plugins/org.apache.lucene.core_3.5.0.v20120725-1805.jar [WARNING] [13] jbosstools-multiple.target.repo/plugins/org.apache.lucene.core_6.1.0.v20161115-1612.jar [WARNING] [14] jbosstools-multiple.target.repo/plugins/org.eclipse.jdt.annotation_2.1.100.v20170511-1408.jar [WARNING] [14] jbosstools-multiple.target.repo/plugins/org.eclipse.jdt.annotation_1.1.100.v20160418-1457.jar [WARNING] [15] jbosstools-multiple.target.repo/plugins/org.eclipse.jetty.continuation_9.4.5.v20170502.jar [WARNING] [15] jbosstools-multiple.target.repo/plugins/org.eclipse.jetty.continuation_9.4.6.v20170531.jar [WARNING] [16] jbosstools-multiple.target.repo/plugins/org.eclipse.jetty.http_9.4.6.v20170531.jar [WARNING] [16] jbosstools-multiple.target.repo/plugins/org.eclipse.jetty.http_9.4.5.v20170502.jar [WARNING] [17] jbosstools-multiple.target.repo/plugins/org.eclipse.jetty.io_9.4.5.v20170502.jar [WARNING] [17] jbosstools-multiple.target.repo/plugins/org.eclipse.jetty.io_9.4.6.v20170531.jar [WARNING] [18] jbosstools-multiple.target.repo/plugins/org.eclipse.jetty.security_9.4.5.v20170502.jar [WARNING] [18] jbosstools-multiple.target.repo/plugins/org.eclipse.jetty.security_9.4.6.v20170531.jar [WARNING] [19] jbosstools-multiple.target.repo/plugins/org.eclipse.jetty.server_9.4.5.v20170502.jar [WARNING] [19] jbosstools-multiple.target.repo/plugins/org.eclipse.jetty.server_9.4.6.v20170531.jar [WARNING] [20] jbosstools-multiple.target.repo/plugins/org.eclipse.jetty.servlet_9.4.5.v20170502.jar [WARNING] [20] jbosstools-multiple.target.repo/plugins/org.eclipse.jetty.servlet_9.4.6.v20170531.jar [WARNING] [21] jbosstools-multiple.target.repo/plugins/org.eclipse.jetty.util_9.4.6.v20170531.jar [WARNING] [21] jbosstools-multiple.target.repo/plugins/org.eclipse.jetty.util_9.4.5.v20170502.jar [WARNING] [22] jbosstools-multiple.target.repo/plugins/org.eclipse.jetty.webapp_9.4.5.v20170502.jar [WARNING] [22] jbosstools-multiple.target.repo/plugins/org.eclipse.jetty.webapp_9.4.6.v20170531.jar [WARNING] [23] jbosstools-multiple.target.repo/plugins/org.eclipse.jetty.xml_9.4.5.v20170502.jar [WARNING] [23] jbosstools-multiple.target.repo/plugins/org.eclipse.jetty.xml_9.4.6.v20170531.jar [WARNING] [24] jbosstools-multiple.target.repo/plugins/org.objectweb.asm_5.2.0.v20170126-0011.jar [WARNING] [24] jbosstools-multiple.target.repo/plugins/org.objectweb.asm_4.0.0.v201302062210.jar [WARNING] [24] jbosstools-multiple.target.repo/plugins/org.objectweb.asm_5.0.1.v201404251740.jar [WARNING] [25] jbosstools-multiple.target.repo/plugins/org.objectweb.asm.analysis_5.0.1.v201505121915.jar [WARNING] [25] jbosstools-multiple.target.repo/plugins/org.objectweb.asm.analysis_5.2.0.v20170126-0011.jar [WARNING] [26] jbosstools-multiple.target.repo/plugins/org.objectweb.asm.tree_5.2.0.v20170126-0011.jar [WARNING] [26] jbosstools-multiple.target.repo/plugins/org.objectweb.asm.tree_5.0.1.v201404251740.jar [WARNING] [27] jbosstools-multiple.target.repo/plugins/org.objectweb.asm.util_5.2.0.v20170126-0011.jar [WARNING] [27] jbosstools-multiple.target.repo/plugins/org.objectweb.asm.util_5.0.1.v201404251740.jar [WARNING] [28] jbosstools-multiple.target.repo/plugins/org.slf4j.api_1.7.10.v20170428-1633.jar [WARNING] [28] jbosstools-multiple.target.repo/plugins/org.slf4j.api_1.7.2.v20121108-1250.jar [WARNING] [29] jbosstools-multiple.target.repo/plugins/org.w3c.dom.smil_1.0.1.v200903091627.jar [WARNING] [29] jbosstools-multiple.target.repo/plugins/org.w3c.dom.smil_1.0.0.v200806040011.jar {code} > update target platform & Central to Oxygen.0+ > --------------------------------------------- > > Key: JBIDE-24652 > URL: https://issues.jboss.org/browse/JBIDE-24652 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.5.0.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.0.Final > > > Issue to track changes to target platform after AM1. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24797) Code formatter: define and hook code formatting enforcement for github PRs

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-24797: ---------------------------------------- Summary: Code formatter: define and hook code formatting enforcement for github PRs Key: JBIDE-24797 URL: https://issues.jboss.org/browse/JBIDE-24797 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: openshift Affects Versions: 4.5.0.Final Reporter: Andre Dietisheim Fix For: 4.5.1.AM1 Code formatting differs across developers. The most prominent differences I am aware of are * use spaces vs tabs * if statements: ``` if(XX){ ``` vs ``` if (XX) { ``` * insonsitent code identations * odd identations of braces for anonymous classes ``` class Listener { int i = 0; public void method() { } } ``` -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24797) Code formatter: define and hook code formatting enforcement for github PRs

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24797?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24797: ------------------------------------- Description: Code formatting differs across developers. The most prominent differences I am aware of are * use spaces vs tabs * if statements: {code} if(XX){ {code} vs {code} if (XX) { {code} * insonsitent code identations * odd identations of braces for anonymous classes {code} class Listener { int i = 0; public void method() { } } {code} was: Code formatting differs across developers. The most prominent differences I am aware of are * use spaces vs tabs * if statements: ``` if(XX){ ``` vs ``` if (XX) { ``` * insonsitent code identations * odd identations of braces for anonymous classes ``` class Listener { int i = 0; public void method() { } } ``` > Code formatter: define and hook code formatting enforcement for github PRs > -------------------------------------------------------------------------- > > Key: JBIDE-24797 > URL: https://issues.jboss.org/browse/JBIDE-24797 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.5.0.Final > Reporter: Andre Dietisheim > Fix For: 4.5.1.AM1 > > > Code formatting differs across developers. > The most prominent differences I am aware of are > * use spaces vs tabs > * if statements: > {code} > if(XX){ > {code} > vs > {code} > if (XX) { > {code} > * insonsitent code identations > * odd identations of braces for anonymous classes > {code} > class Listener { > int i = 0; > public void method() { > } > } > {code} > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1151) Section 508 - VPAT Compatibility

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1151?page=com.atlassian.jira.plugin... ] Paul Leacu updated JBTIS-1151: ------------------------------ Description: Provide Section 508 - VPAT compliance Integration Stack product if possible in a next GA release. Ref: https://mojo.redhat.com/docs/DOC-28860 Some useful info before going to a formal evaluation: https://mojo.redhat.com/docs/DOC-175787 https://docs.google.com/document/d/1bLF8ryUfURbf8AT3qb0-FcKj6QNFXwYktFEM7... https://eclipse.org/actf/ https://wiki.eclipse.org/SimRel/Simultaneous_Release_Requirements/Appendi... : https://access.redhat.com/articles/2918071#section-508-8 https://www.redhat.com/en/files/resources/en-rhjb-section-508-vpat-jboss-... https://www.redhat.com/en/files/resources/cl-openshift-3-vpat.pdf https://access.redhat.com/help/accessibility http://www.itic.org/public-policy/accessibility/ http://www.section508.gov/ http://www.w3.org/TR/WCAG/ was: Provide Section 508 - VPAT compliance Integration Stack product if possible in a next GA release. Ref: https://mojo.redhat.com/docs/DOC-28860 Some useful info before going to a formal evaluation: https://mojo.redhat.com/docs/DOC-175787 https://docs.google.com/document/d/1bLF8ryUfURbf8AT3qb0-FcKj6QNFXwYktFEM7... https://eclipse.org/actf/ https://wiki.eclipse.org/SimRel/Simultaneous_Release_Requirements/Appendi... : https://access.redhat.com/articles/2918071#section-508-8 https://www.redhat.com/en/files/resources/en-rhjb-section-508-vpat-jboss-... https://www.redhat.com/en/files/resources/cl-openshift-3-vpat.pdf https://access.redhat.com/help/accessibility > Section 508 - VPAT Compatibility > -------------------------------- > > Key: JBTIS-1151 > URL: https://issues.jboss.org/browse/JBTIS-1151 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: distribution > Affects Versions: 10.3.0.GA > Environment: > Reporter: Wagner Queiroz > Assignee: Paul Leacu > Priority: Minor > > Provide Section 508 - VPAT compliance Integration Stack product if possible in a next GA release. > Ref: https://mojo.redhat.com/docs/DOC-28860 > Some useful info before going to a formal evaluation: > https://mojo.redhat.com/docs/DOC-175787 > https://docs.google.com/document/d/1bLF8ryUfURbf8AT3qb0-FcKj6QNFXwYktFEM7... > https://eclipse.org/actf/ > https://wiki.eclipse.org/SimRel/Simultaneous_Release_Requirements/Appendi... : > https://access.redhat.com/articles/2918071#section-508-8 > https://www.redhat.com/en/files/resources/en-rhjb-section-508-vpat-jboss-... > https://www.redhat.com/en/files/resources/cl-openshift-3-vpat.pdf > https://access.redhat.com/help/accessibility > http://www.itic.org/public-policy/accessibility/ > http://www.section508.gov/ > http://www.w3.org/TR/WCAG/ -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4444) [DevSuite Installer] Move Account step after Confirmation step

by Catherine Robson (JIRA)

[ https://issues.jboss.org/browse/JBDS-4444?page=com.atlassian.jira.plugin.... ] Catherine Robson commented on JBDS-4444: ---------------------------------------- You can find a background image you can use for this here: https://github.com/fabric8-ui/fabric8-ui/blob/master/src/assets/images/Lo... We'd be interested in seeing what this looks like as it gets applied so we can tweak it if needed. > [DevSuite Installer] Move Account step after Confirmation step > -------------------------------------------------------------- > > Key: JBDS-4444 > URL: https://issues.jboss.org/browse/JBDS-4444 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: platform-installer > Affects Versions: 11.0.0.AM1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Labels: New_and_noteworthy, ui > Fix For: 11.0.0.GA > > Attachments: about-update1.png, devsuite-installer-1.4.0-workflow.png, devsuite-installer-2.0.0-workflow.png, install-step-3-1.png, install-step-3-2.png, install-step-4.png, install-step-5-1.png, install-step-5-2.png, install-step-6-1.png, install-step-6.png, install-step1.png, install-step2.png > > > As a user I would like to avoid entering login/password on a first page of installer, so I can explore and see what can be installed and then provide my credentials if I decided to proceed with installation. > Current workflow is > !devsuite-installer-1.4.0-workflow.png|thumbnail! > should be transformed to > !devsuite-installer-2.0.0-workflow.png|thumbnail! > This would require to change starting page to show only generic information about DevSuite Installer and whole first page 'Account' should appear after confirmation page in case any of Red Hat Products is selected for installation. > Here are screenshots for how it could look like for scenario when Red Hat Product Selected: > !install-step1.png|thumbnail! !install-step2.png|thumbnail! !install-step-3-1.png|thumbnail! !install-step-4.png|thumbnail! !install-step-5-2.png|thumbnail! !install-step-6-1.png|thumbnail! > and when community or 3rd party components only selected: > !install-step1.png|thumbnail! !install-step2.png|thumbnail! !install-step-3-2.png|thumbnail! !install-step-5-1.png|thumbnail! !install-step-6.png|thumbnail! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24648) update target platform to include jetty 9.4.6 (CVE issue)

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24648?page=com.atlassian.jira.plugi... ] Lukáš Valach closed JBIDE-24648. -------------------------------- Verified, TP includes jetty 9.4.6. It also includes jetty 9.4.5 but it shouldn't be a problem. Our standart tests should catch possible issue if any. Closing. > update target platform to include jetty 9.4.6 (CVE issue) > --------------------------------------------------------- > > Key: JBIDE-24648 > URL: https://issues.jboss.org/browse/JBIDE-24648 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform, upstream > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.0.Final > > > Fedora and RHEL have updated to Jetty 9.4.6 due to this CVE: > * https://bugzilla.redhat.com/show_bug.cgi?id=1464158 > Currently, JBT/devstudio target platform includes Jetty 9.4.5, as that's what was in Oxygen.0.RC4. > But we could move to a newer version if we want to have the same version in linux and in windows/OSX versions of JBT/devstudio. > Affected manifest files (which require jetty bundles from *[9.4.0,9.5.0)*) > * [1] ./jbosstools-aerogear/cordovasim/plugins/org.jboss.tools.cordovasim.eclipse/META-INF/MANIFEST.MF > * [2] ./jbosstools-aerogear/cordovasim/plugins/org.jboss.tools.cordovasim/META-INF/MANIFEST.MF > * [3] ./jbosstools-aerogear/cordovasim/tests/org.jboss.tools.cordovasim.eclipse.test/META-INF/MANIFEST.MF > * [4] ./jbosstools-base/foundation/tests/org.jboss.tools.foundation.core.test/META-INF/MANIFEST.MF > * [5] ./jbosstools-browsersim/plugins/org.jboss.tools.browsersim.ui/META-INF/MANIFEST.MF > * [6] ./jbosstools-central/central/tests/org.jboss.tools.central.test/META-INF/MANIFEST.MF > * [7] ./jbosstools-livereload/plugins/org.jboss.tools.livereload.core/META-INF/MANIFEST.MF > * [8] ./jbosstools-livereload/tests/org.jboss.tools.livereload.test/META-INF/MANIFEST.MF > * [9] ./jbosstools-server/jmx/tests/org.jboss.tools.jmx.jolokia.test/META-INF/MANIFEST.MF -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1151) Section 508 - VPAT Compatibility

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1151?page=com.atlassian.jira.plugin... ] Paul Leacu updated JBTIS-1151: ------------------------------ Description: Provide Section 508 - VPAT compliance Integration Stack product if possible in a next GA release. Ref: https://mojo.redhat.com/docs/DOC-28860 Some useful info before going to a formal evaluation: https://mojo.redhat.com/docs/DOC-175787 https://docs.google.com/document/d/1bLF8ryUfURbf8AT3qb0-FcKj6QNFXwYktFEM7... https://eclipse.org/actf/ https://wiki.eclipse.org/SimRel/Simultaneous_Release_Requirements/Appendi... : https://access.redhat.com/articles/2918071#section-508-8 https://www.redhat.com/en/files/resources/en-rhjb-section-508-vpat-jboss-... https://www.redhat.com/en/files/resources/cl-openshift-3-vpat.pdf https://access.redhat.com/help/accessibility was: Provide Section 508 - VPAT compliance Integration Stack product if possible in a next GA release. Ref: https://mojo.redhat.com/docs/DOC-28860 Some useful info before going to a formal evaluation: https://mojo.redhat.com/docs/DOC-175787 > Section 508 - VPAT Compatibility > -------------------------------- > > Key: JBTIS-1151 > URL: https://issues.jboss.org/browse/JBTIS-1151 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: distribution > Affects Versions: 10.3.0.GA > Environment: > Reporter: Wagner Queiroz > Assignee: Paul Leacu > Priority: Minor > > Provide Section 508 - VPAT compliance Integration Stack product if possible in a next GA release. > Ref: https://mojo.redhat.com/docs/DOC-28860 > Some useful info before going to a formal evaluation: > https://mojo.redhat.com/docs/DOC-175787 > https://docs.google.com/document/d/1bLF8ryUfURbf8AT3qb0-FcKj6QNFXwYktFEM7... > https://eclipse.org/actf/ > https://wiki.eclipse.org/SimRel/Simultaneous_Release_Requirements/Appendi... : > https://access.redhat.com/articles/2918071#section-508-8 > https://www.redhat.com/en/files/resources/en-rhjb-section-508-vpat-jboss-... > https://www.redhat.com/en/files/resources/cl-openshift-3-vpat.pdf > https://access.redhat.com/help/accessibility -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4493) Virtualization detection never terminates on powershell version <= 2

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4493?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-4493: ------------------------------------- It was my suspect too, considering it is the major difference between 1.3.0 which is working fine and 1.4.X where it was implemented. Thanks Jan for looking into it and identifying the problem. > Virtualization detection never terminates on powershell version <= 2 > --------------------------------------------------------------------- > > Key: JBDS-4493 > URL: https://issues.jboss.org/browse/JBDS-4493 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 11.0.0.AM2 > Reporter: Jan Richter > Assignee: Denis Golovin > Priority: Critical > Fix For: 11.0.0.GA > > > Follow up on the mail thread about detection not finishing on win 7. > Namely methods from the Platform class that call powershell commands: > - isVirtualizationEnabled > - getHypervisorVersion > - isHypervisorEnabled > For some reason when called instead of erroring (since these commands dont work on older powershell) they don't terminate and block the detection. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues August 2017