June 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22544) Redudant error report in Devstudio's Problems View

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22544?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich edited comment on JBIDE-22544 at 6/6/16 8:54 PM: ----------------------------------------------------------------------- org.eclipse.wst.xml.core.internal.validation.eclipse.Validator is called twice from org.eclipse.wst.validation.internal.ValManager and all results are summed. This happens not only for batch job xml, but for any xml file. It is shown in preferences Validation list as 'XML Validator'. If I disable all other validators, still error markers are duplicated. If I disable 'XML Validator', this kind of errors does not appear. But, the problem is not that the validator duplicates errors itself, but it is that the validator is called twice during the project validation. ValBuilderJob.runInWorkspace() has a loop in which it repeats validation until getRequest() returns null. Then ValManager.validate(IProject,...) calls delete markers, but it works only for the first call, it is designed to accumulate markers created in multiple calls from ValBuilderJob during the same build. Two 'complete' requests that make the same file to be validated twice come independently from 1) org.eclipse.wst.validation.internal.operations.ValidationBuilder 2) org.eclipse.wst.jsdt.internal.core.builder.JavaBuilder was (Author: scabanovich): org.eclipse.wst.xml.core.internal.validation.eclipse.Validator is called twice from org.eclipse.wst.validation.internal.ValManager and all results are summed. This happens not only for batch job xml, but for any xml file. It is shown in preferences Validation list as 'XML Validator'. If I disable all other validators, still error markers are duplicated. If I disable 'XML Validator', this kind of errors does not appear. But, the problem is not that the validator duplicates errors itself, but it is that the validator is called twice during the project validation. ValBuilderJob.runInWorkspace() has a loop in which it repeats validation until getRequest() returns null. Then ValManager.validate(IProject,...) calls delete markers, but it works only for the first call, it is designed to accumulate markers created in multiple calls from ValBuilderJob during the same build. Two 'complete' request that make the same file to be validated twice come independently from 1) org.eclipse.wst.validation.internal.operations.ValidationBuilder 2) org.eclipse.wst.jsdt.internal.core.builder.JavaBuilder > Redudant error report in Devstudio's Problems View > -------------------------------------------------- > > Key: JBIDE-22544 > URL: https://issues.jboss.org/browse/JBIDE-22544 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: batch, upstream > Reporter: Ondrej Dockal > Assignee: Viacheslav Kabanovich > Fix For: 4.4.x > > Attachments: org.jboss.tools.batch.ui.bot.test.editor.design.DesignChunkStepElementTest.createStep(7).png > > > Some test fails on checking number of errors in Problems View in devstudio. There are duplicated error reports. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-654) JBDSIS stand-alone installer

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBTIS-654?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBTIS-654: ------------------------------------- Paul, look at Unpacker.java. It is the class where I hacked in with p2 integration for devstudio. > JBDSIS stand-alone installer > ---------------------------- > > Key: JBTIS-654 > URL: https://issues.jboss.org/browse/JBTIS-654 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: distribution > Affects Versions: 9.0.0.GA > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 9.0.1.GA > > Attachments: Capture.JPG, inst1.png > > > Establish a stand-alone installer for JBDSIS that will contain JBDS and will enable easier installation of JBDSIS components - specifically Fuse Tooling. This Jira is specifically related to the JBDSIS installer. Other usability issues will be handled in other Jira. > Installation scenario: > {code} > 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) > 2. Download the JBDSIS installer jar. i.e. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.... > 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*.jar` > 4. Select 'JBoss Fuse Development' from the 'Select Additional Features to Install' installer window. > 5. Accept/ respond 'Yes' and restart > 6. Select Window > Perspective > Open Perspective > Fuse Integration > {code} > A prototype installer has already been created - see: > https://github.com/jbosstools/jbosstools-integration-stack/tree/master/de... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22544) Redudant error report in Devstudio's Problems View

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22544?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich edited comment on JBIDE-22544 at 6/6/16 8:53 PM: ----------------------------------------------------------------------- org.eclipse.wst.xml.core.internal.validation.eclipse.Validator is called twice from org.eclipse.wst.validation.internal.ValManager and all results are summed. This happens not only for batch job xml, but for any xml file. It is shown in preferences Validation list as 'XML Validator'. If I disable all other validators, still error markers are duplicated. If I disable 'XML Validator', this kind of errors does not appear. But, the problem is not that the validator duplicates errors itself, but it is that the validator is called twice during the project validation. ValBuilderJob.runInWorkspace() has a loop in which it repeats validation until getRequest() returns null. Then ValManager.validate(IProject,...) calls delete markers, but it works only for the first call, it is designed to accumulate markers created in multiple calls from ValBuilderJob during the same build. Two 'complete' request that make the same file to be validated twice come independently from 1) org.eclipse.wst.validation.internal.operations.ValidationBuilder 2) org.eclipse.wst.jsdt.internal.core.builder.JavaBuilder was (Author: scabanovich): org.eclipse.wst.xml.core.internal.validation.eclipse.Validator is called twice from org.eclipse.wst.validation.internal.ValManager and all results are summed. This happens not only for batch job xml, but for any xml file. It is shown in preferences Validation list as 'XML Validator'. If I disable all other validators, still error markers are duplicated. If I disable 'XML Validator', this kind of errors does not appear. But, the problem is not that the validator duplicates errors itself, but it is that the validator is duplicated in the list of validators in ValManager. I still have not found why it happens. > Redudant error report in Devstudio's Problems View > -------------------------------------------------- > > Key: JBIDE-22544 > URL: https://issues.jboss.org/browse/JBIDE-22544 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: batch, upstream > Reporter: Ondrej Dockal > Assignee: Viacheslav Kabanovich > Fix For: 4.4.x > > Attachments: org.jboss.tools.batch.ui.bot.test.editor.design.DesignChunkStepElementTest.createStep(7).png > > > Some test fails on checking number of errors in Problems View in devstudio. There are duplicated error reports. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3857) Installer executes in console mode (no GUI) when started with OpenJDK 8

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3857?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-3857: ------------------------------------- It feels like when installer is running with OpenJDK it decides there is no GUI available and starts in [console mode|http://izpack.org/documentation/advanced-features.html#console-headl...]. > Installer executes in console mode (no GUI) when started with OpenJDK 8 > ----------------------------------------------------------------------- > > Key: JBDS-3857 > URL: https://issues.jboss.org/browse/JBDS-3857 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.GA > Environment: RHEL Workstation 7.2 > openjdk version "1.8.0_91" > Reporter: Rafael Soares (Tuelho) > Assignee: Denis Golovin > Fix For: 10.1.0.Alpha1 > > > I've noticed the installer wizard does not starts in GUI mode when using OpenJDK 8 JVM/JRE. > The installer only worked fine (with a GUI Wizard) when I used the Oracle JDK 1.8 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3924) Installation looks incomplete but is actually completed

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/JBDS-3924?page=com.atlassian.jira.plugin.... ] Misha Ali commented on JBDS-3924: --------------------------------- To be clear: the install process kind of stops at the screen in the screenshot. AFAIK it never completes, and I only noticed after it took a surprisingly long time to install that it was stuck at this point in the progress bar. > Installation looks incomplete but is actually completed > ------------------------------------------------------- > > Key: JBDS-3924 > URL: https://issues.jboss.org/browse/JBDS-3924 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: installer > Affects Versions: 10.0.0.GA > Environment: Fedora 23 > Using devstudio-10.0.0.GA-v20160603-1025-B5510-installer-standalone.jar > Reporter: Misha Ali > Assignee: Denis Golovin > Labels: install, installation, installer > Fix For: 10.x > > Attachments: devstudio10install.png > > > Running the standalone installer file starts the devstudio install as expected, but twice I have noticed that the Next button is available to click (indicating that the installation has completed) when the status shows that only 2/3 of the installation steps are concluded. (see screenshot for this screen). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22544) Redudant error report in Devstudio's Problems View

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22544?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-22544: ----------------------------------------------- org.eclipse.wst.xml.core.internal.validation.eclipse.Validator is called twice from org.eclipse.wst.validation.internal.ValManager and all results are summed. This happens not only for batch job xml, but for any xml file. It is shown in preferences Validation list as 'XML Validator'. If I disable all other validators, still error markers are duplicated. If I disable 'XML Validator', this kind of errors does not appear. But, the problem is not that the validator duplicates errors itself, but it is that the validator is duplicated in the list of validators in ValManager. I still have not found why it happens. > Redudant error report in Devstudio's Problems View > -------------------------------------------------- > > Key: JBIDE-22544 > URL: https://issues.jboss.org/browse/JBIDE-22544 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: batch, upstream > Reporter: Ondrej Dockal > Assignee: Viacheslav Kabanovich > Fix For: 4.4.x > > Attachments: org.jboss.tools.batch.ui.bot.test.editor.design.DesignChunkStepElementTest.createStep(7).png > > > Some test fails on checking number of errors in Problems View in devstudio. There are duplicated error reports. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22541) server New and Noteworthy for 4.4.0.Final

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22541?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-22541. --------------------------------- Resolution: Rejected nothing new, strangely enough. =/ Makes me kinda sad... but then I rarely have n&n in a final. > server New and Noteworthy for 4.4.0.Final > ----------------------------------------- > > Key: JBIDE-22541 > URL: https://issues.jboss.org/browse/JBIDE-22541 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: archives, jmx, server > Reporter: Alexey Kazakov > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.4.0.Final > > > If no news for 4.4.0.Final since the last CR release for this component 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 create a separate <component>-news-4.4.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pull request. The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. > If you want to replace all previous N&Ns by a new document then create a new <component>-news-4.4.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...], add "page-include-previous: false" attribute to the document and submit a pull request. > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22511) Application wizard: project without git remote is initially decorated with a "required" decorator, not the warning decoration

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22511?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-22511: ----------------------------------------------- [~adietish], please take a look at the pull request. > Application wizard: project without git remote is initially decorated with a "required" decorator, not the warning decoration > ----------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22511 > URL: https://issues.jboss.org/browse/JBIDE-22511 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Viacheslav Kabanovich > Priority: Minor > Fix For: 4.4.x > > Attachments: git-remote-missing.png, select-template-instead-of-git-remote-missing.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3892) Toolbar items/icons disappear when scaled in size

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3892?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3892: -------------------------------- Fix Version/s: 10.1.0.Alpha1 > Toolbar items/icons disappear when scaled in size > ------------------------------------------------- > > Key: JBDS-3892 > URL: https://issues.jboss.org/browse/JBDS-3892 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: upstream > Affects Versions: 10.0.0.Alpha1 > Environment: devstudio-platform-10.0.0-Alpha1-20160517-157-bundle-installer > Reporter: Jan Richter > Assignee: Denis Golovin > Fix For: 10.1.0.Alpha1 > > Attachments: studio.png > > > It installs OK, it starts up and looks like this: > !studio.png|thumbnail! > Lots of widgets not loaded at all, the start icon is default eclipse one, sometimes it refuses to start at all until a clean workspace is selected. > And still, no errors in the log. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3730) Headless standalone installer can be run with xml config that contains eap bundle

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3730?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3730: -------------------------------- Fix Version/s: 10.1.0.Alpha1 > Headless standalone installer can be run with xml config that contains eap bundle > --------------------------------------------------------------------------------- > > Key: JBDS-3730 > URL: https://issues.jboss.org/browse/JBDS-3730 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Jan Richter > Assignee: Denis Golovin > Priority: Minor > Fix For: 10.1.0.Alpha1 > > > One can run the headless standalone installer with a config xml file which contains the instructions to install eap as well. This results in the following: > {noformat}[ Starting automated installation ] > [INFO] Selected JVM Information > [INFO] Location : /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.72-1.b15.fc22.x86_64 > [INFO] Vendor : Oracle Corporation > [INFO] Version : 1.8.0_72 > [INFO] Arch : 64-bit > [ Starting to unpack ] > [ Processing package: P2 Director Application (1/4) ] > [ Processing package: Red Hat JBoss Developer Studio 9.1.0.CR1 (2/4) ] > [ Processing package: Red Hat JBoss Developer Studio 9.1.0.CR1 Metadata Generation (3/4) ] > [ Processing package: JBoss Enterprise Application Platform (4/4) ] > [ WARNING: Error executing > /bin/chmod a+x /home/jrichter/Downloads/temp/runtimes/jboss-eap/bin/init.d/jboss-as-standalone.sh ] > [ ERROR: The installation was not completed ] > [ Unpacking finished ] > com.izforge.izpack.installer.InstallerException: Unpack failed (xml line 19) > com.izforge.izpack.installer.InstallerException: Unpack failed (xml line 19) > at com.izforge.izpack.panels.InstallPanelAutomationHelper.runAutomated(Unknown Source) > at com.izforge.izpack.installer.AutomatedInstaller.installPanel(AutomatedInstaller.java:432) > at com.izforge.izpack.installer.AutomatedInstaller.doInstall(AutomatedInstaller.java:388) > at com.izforge.izpack.installer.Installer.main(Unknown Source) > [ Automated installation FAILED! ]{noformat} > The resulting installation is still perfectly functional, but no icons/shortcuts are created. It might be nicer if the installer was able to identify if it can install all the bundles in the config file and at least warn when starting up. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 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 June 2016