June 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22506) Aeri web requires login to see submitted bug

by Marcel Bruch (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22506?page=com.atlassian.jira.plugi... ] Marcel Bruch closed JBIDE-22506. -------------------------------- Fix Version/s: 4.4.0.Final (was: 4.4.x) Resolution: Done > Aeri web requires login to see submitted bug > -------------------------------------------- > > Key: JBIDE-22506 > URL: https://issues.jboss.org/browse/JBIDE-22506 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aeri > Affects Versions: 4.4.0.Alpha2 > Reporter: Rastislav Wagner > Assignee: Marcel Bruch > Priority: Critical > Fix For: 4.4.0.Final > > > I've submitted a bug via aeri and got this url in notification > https://redhat.ctrlflow.com/reporters/#!/submissions/2UAIQE4IlcQ0ctFOxLBX... which requires login to see the content. > If I remember correctly logging in was not needed in the past. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21958) Provide filters by status on Problems view

by Marcel Bruch (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21958?page=com.atlassian.jira.plugi... ] Marcel Bruch closed JBIDE-21958. -------------------------------- Fix Version/s: 4.4.0.Final (was: 4.4.x) Resolution: Done > Provide filters by status on Problems view > ------------------------------------------- > > Key: JBIDE-21958 > URL: https://issues.jboss.org/browse/JBIDE-21958 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: aeri > Reporter: Aurélien Pupier > Assignee: Marcel Bruch > Priority: Minor > Fix For: 4.4.0.Final > > > Specific use case I have in mind: > - have the list of pending reports > - have the list of pending reports with no issue > If we can filter on every field it would be nice too but perhaps as a second iteration -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21723) debug/warning errors from aeri in logs

by Marcel Bruch (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21723?page=com.atlassian.jira.plugi... ] Marcel Bruch closed JBIDE-21723. -------------------------------- Fix Version/s: 4.4.0.Final Resolution: Done > debug/warning errors from aeri in logs > -------------------------------------- > > Key: JBIDE-21723 > URL: https://issues.jboss.org/browse/JBIDE-21723 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aeri > Reporter: Max Rydahl Andersen > Assignee: Marcel Bruch > Fix For: 4.4.0.Final > > > seeing a info and warning message when errors occurs. > {code} > eclipse.buildId=4.6.0.I20151209-2300 > java.version=1.8.0_20 > java.vendor=Oracle Corporation > BootLoader constants: OS=macosx, ARCH=x86_64, WS=cocoa, NL=en_US > Framework arguments: -product org.eclipse.epp.package.jee.product -product org.eclipse.epp.package.jee.product -keyring /Users/max/.eclipse_keyring > Command-line arguments: -os macosx -ws cocoa -arch x86_64 -product org.eclipse.epp.package.jee.product -data file:/Users/max/workspaces/eclipseerror/ -product org.eclipse.epp.package.jee.product -keyring /Users/max/.eclipse_keyring > org.eclipse.epp.logging.aeri.ide > Info > Fri Feb 19 18:56:42 CET 2016 > Added ‘Unknown category 'org.jboss.to…8.jar_5289305038018513896.jar’ under ‘b2c2e18436026b0d358c3d135c923fc4’ to local history at /Users/max/workspaces/eclipsee…org.jboss.tools/local-history. ; version: 1.100.0.v20160203-1727 > org.eclipse.epp.logging.aeri.core.util.Logs$LogTraceException > at org.eclipse.epp.logging.aeri.core.util.Logs$LogTraceException.newTrace(Logs.java:383) > at org.eclipse.epp.logging.aeri.core.util.Logs.log(Logs.java:134) > at org.eclipse.epp.internal.logging.aeri.ide.server.LocalReportsHistory.doRemember(LocalReportsHistory.java:137) > at org.eclipse.epp.internal.logging.aeri.ide.server.LocalReportsHistory.remember(LocalReportsHistory.java:119) > at org.eclipse.epp.internal.logging.aeri.ide.server.mars.ServerConnection.submit(ServerConnection.java:190) > at org.eclipse.epp.internal.logging.aeri.ide.utils.UploadReportsScheduler.send(UploadReportsScheduler.java:52) > at org.eclipse.epp.internal.logging.aeri.ide.utils.UploadReportsScheduler.send(UploadReportsScheduler.java:69) > at org.eclipse.epp.internal.logging.aeri.ide.IDEStartup$2.send(IDEStartup.java:98) > at org.eclipse.epp.internal.logging.aeri.ide.utils.UploadReportsScheduler$UploadJob.run(UploadReportsScheduler.java:106) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {code} > and > {code} > eclipse.buildId=4.6.0.I20151209-2300 > java.version=1.8.0_20 > java.vendor=Oracle Corporation > BootLoader constants: OS=macosx, ARCH=x86_64, WS=cocoa, NL=en_US > Framework arguments: -product org.eclipse.epp.package.jee.product -product org.eclipse.epp.package.jee.product -keyring /Users/max/.eclipse_keyring > Command-line arguments: -os macosx -ws cocoa -arch x86_64 -product org.eclipse.epp.package.jee.product -data file:/Users/max/workspaces/eclipseerror/ -product org.eclipse.epp.package.jee.product -keyring /Users/max/.eclipse_keyring > org.eclipse.epp.logging.aeri.ide > Warning > Fri Feb 19 18:56:42 CET 2016 > Unexpected response : UNKNOWN ‐ UNKNOWN ; version: 1.100.0.v20160203-1727 > org.eclipse.epp.logging.aeri.core.util.Logs$LogTraceException > at org.eclipse.epp.logging.aeri.core.util.Logs$LogTraceException.newTrace(Logs.java:383) > at org.eclipse.epp.logging.aeri.core.util.Logs.log(Logs.java:134) > at org.eclipse.epp.internal.logging.aeri.ide.server.mars.IO.tryParse(IO.java:237) > at org.eclipse.epp.internal.logging.aeri.ide.server.mars.IO.upload(IO.java:116) > at org.eclipse.epp.internal.logging.aeri.ide.server.mars.ServerConnection.submit(ServerConnection.java:189) > at org.eclipse.epp.internal.logging.aeri.ide.utils.UploadReportsScheduler.send(UploadReportsScheduler.java:52) > at org.eclipse.epp.internal.logging.aeri.ide.utils.UploadReportsScheduler.send(UploadReportsScheduler.java:69) > at org.eclipse.epp.internal.logging.aeri.ide.IDEStartup$2.send(IDEStartup.java:98) > at org.eclipse.epp.internal.logging.aeri.ide.utils.UploadReportsScheduler$UploadJob.run(UploadReportsScheduler.java:106) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22506) Aeri web requires login to see submitted bug

by Marcel Bruch (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22506?page=com.atlassian.jira.plugi... ] Marcel Bruch reassigned JBIDE-22506: ------------------------------------ Resolution: (was: Done) > Aeri web requires login to see submitted bug > -------------------------------------------- > > Key: JBIDE-22506 > URL: https://issues.jboss.org/browse/JBIDE-22506 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aeri > Affects Versions: 4.4.0.Alpha2 > Reporter: Rastislav Wagner > Assignee: Marcel Bruch > Priority: Critical > Fix For: 4.4.x > > > I've submitted a bug via aeri and got this url in notification > https://redhat.ctrlflow.com/reporters/#!/submissions/2UAIQE4IlcQ0ctFOxLBX... which requires login to see the content. > If I remember correctly logging in was not needed in the past. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21958) Provide filters by status on Problems view

by Marcel Bruch (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21958?page=com.atlassian.jira.plugi... ] Marcel Bruch reassigned JBIDE-21958: ------------------------------------ Resolution: (was: Done) Assignee: Marcel Bruch > Provide filters by status on Problems view > ------------------------------------------- > > Key: JBIDE-21958 > URL: https://issues.jboss.org/browse/JBIDE-21958 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: aeri > Reporter: Aurélien Pupier > Assignee: Marcel Bruch > Priority: Minor > Fix For: 4.4.x > > > Specific use case I have in mind: > - have the list of pending reports > - have the list of pending reports with no issue > If we can filter on every field it would be nice too but perhaps as a second iteration -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21723) debug/warning errors from aeri in logs

by Marcel Bruch (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21723?page=com.atlassian.jira.plugi... ] Marcel Bruch reassigned JBIDE-21723: ------------------------------------ Resolution: (was: Done) Assignee: Marcel Bruch > debug/warning errors from aeri in logs > -------------------------------------- > > Key: JBIDE-21723 > URL: https://issues.jboss.org/browse/JBIDE-21723 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aeri > Reporter: Max Rydahl Andersen > Assignee: Marcel Bruch > > seeing a info and warning message when errors occurs. > {code} > eclipse.buildId=4.6.0.I20151209-2300 > java.version=1.8.0_20 > java.vendor=Oracle Corporation > BootLoader constants: OS=macosx, ARCH=x86_64, WS=cocoa, NL=en_US > Framework arguments: -product org.eclipse.epp.package.jee.product -product org.eclipse.epp.package.jee.product -keyring /Users/max/.eclipse_keyring > Command-line arguments: -os macosx -ws cocoa -arch x86_64 -product org.eclipse.epp.package.jee.product -data file:/Users/max/workspaces/eclipseerror/ -product org.eclipse.epp.package.jee.product -keyring /Users/max/.eclipse_keyring > org.eclipse.epp.logging.aeri.ide > Info > Fri Feb 19 18:56:42 CET 2016 > Added ‘Unknown category 'org.jboss.to…8.jar_5289305038018513896.jar’ under ‘b2c2e18436026b0d358c3d135c923fc4’ to local history at /Users/max/workspaces/eclipsee…org.jboss.tools/local-history. ; version: 1.100.0.v20160203-1727 > org.eclipse.epp.logging.aeri.core.util.Logs$LogTraceException > at org.eclipse.epp.logging.aeri.core.util.Logs$LogTraceException.newTrace(Logs.java:383) > at org.eclipse.epp.logging.aeri.core.util.Logs.log(Logs.java:134) > at org.eclipse.epp.internal.logging.aeri.ide.server.LocalReportsHistory.doRemember(LocalReportsHistory.java:137) > at org.eclipse.epp.internal.logging.aeri.ide.server.LocalReportsHistory.remember(LocalReportsHistory.java:119) > at org.eclipse.epp.internal.logging.aeri.ide.server.mars.ServerConnection.submit(ServerConnection.java:190) > at org.eclipse.epp.internal.logging.aeri.ide.utils.UploadReportsScheduler.send(UploadReportsScheduler.java:52) > at org.eclipse.epp.internal.logging.aeri.ide.utils.UploadReportsScheduler.send(UploadReportsScheduler.java:69) > at org.eclipse.epp.internal.logging.aeri.ide.IDEStartup$2.send(IDEStartup.java:98) > at org.eclipse.epp.internal.logging.aeri.ide.utils.UploadReportsScheduler$UploadJob.run(UploadReportsScheduler.java:106) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {code} > and > {code} > eclipse.buildId=4.6.0.I20151209-2300 > java.version=1.8.0_20 > java.vendor=Oracle Corporation > BootLoader constants: OS=macosx, ARCH=x86_64, WS=cocoa, NL=en_US > Framework arguments: -product org.eclipse.epp.package.jee.product -product org.eclipse.epp.package.jee.product -keyring /Users/max/.eclipse_keyring > Command-line arguments: -os macosx -ws cocoa -arch x86_64 -product org.eclipse.epp.package.jee.product -data file:/Users/max/workspaces/eclipseerror/ -product org.eclipse.epp.package.jee.product -keyring /Users/max/.eclipse_keyring > org.eclipse.epp.logging.aeri.ide > Warning > Fri Feb 19 18:56:42 CET 2016 > Unexpected response : UNKNOWN ‐ UNKNOWN ; version: 1.100.0.v20160203-1727 > org.eclipse.epp.logging.aeri.core.util.Logs$LogTraceException > at org.eclipse.epp.logging.aeri.core.util.Logs$LogTraceException.newTrace(Logs.java:383) > at org.eclipse.epp.logging.aeri.core.util.Logs.log(Logs.java:134) > at org.eclipse.epp.internal.logging.aeri.ide.server.mars.IO.tryParse(IO.java:237) > at org.eclipse.epp.internal.logging.aeri.ide.server.mars.IO.upload(IO.java:116) > at org.eclipse.epp.internal.logging.aeri.ide.server.mars.ServerConnection.submit(ServerConnection.java:189) > at org.eclipse.epp.internal.logging.aeri.ide.utils.UploadReportsScheduler.send(UploadReportsScheduler.java:52) > at org.eclipse.epp.internal.logging.aeri.ide.utils.UploadReportsScheduler.send(UploadReportsScheduler.java:69) > at org.eclipse.epp.internal.logging.aeri.ide.IDEStartup$2.send(IDEStartup.java:98) > at org.eclipse.epp.internal.logging.aeri.ide.utils.UploadReportsScheduler$UploadJob.run(UploadReportsScheduler.java:106) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21724) when clicking cancel on "configure automated error reporting" it disables all

by Marcel Bruch (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21724?page=com.atlassian.jira.plugi... ] Marcel Bruch reassigned JBIDE-21724: ------------------------------------ Resolution: (was: Done) Assignee: Marcel Bruch > when clicking cancel on "configure automated error reporting" it disables all > ----------------------------------------------------------------------------- > > Key: JBIDE-21724 > URL: https://issues.jboss.org/browse/JBIDE-21724 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aeri > Reporter: Max Rydahl Andersen > Assignee: Marcel Bruch > Priority: Critical > > When you click configure in aeri preferences the dialog only have Disable and Enable buttons. Clicking "close" in upper left (i.e. Cancel as in = don't do anything) result in all reporting disabled. > I would expect closing the dialog with the close buton or escape would change nothing. - but i globally disables. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3921) DevSuite - Devstudio has outdated icon paths

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3921?page=com.atlassian.jira.plugin.... ] Jan Richter updated JBDS-3921: ------------------------------ Fix Version/s: 10.0.0.GA > DevSuite - Devstudio has outdated icon paths > -------------------------------------------- > > Key: JBDS-3921 > URL: https://issues.jboss.org/browse/JBDS-3921 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.0.0.GA > Reporter: Jan Richter > Assignee: Jan Richter > Fix For: 10.0.0.GA > > > The install config xml still points to jbds.ico and jbds_uninstall.ico so it generates shorctuts with no icons. -- 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 9:21 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 by method newBuild(). The second builder is registered in jsdt as 'JavaScript Validator' So, when I disabled JavaScript Validator in project properties in section Builders, there was no more duplication of markers. It seems like 'JavaScript Validator' and ordinary 'Validation' builders should not be both enabled on a project. 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' 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 > 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: ------------------------------------- pack.id's are for packs defined in https://github.com/dgolovin/jbdevstudio-product/blob/master/installer/src.... > 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

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