November 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-16072) BrowserSim: Can we support ChildBrowser plugin in cordovasim

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16072?page=com.atlassian.jira.plugi... ] Vlado Pakan resolved JBIDE-16072. --------------------------------- Fix Version/s: (was: 4.1.1.CR1) Resolution: Done > BrowserSim: Can we support ChildBrowser plugin in cordovasim > ------------------------------------------------------------ > > Key: JBIDE-16072 > URL: https://issues.jboss.org/browse/JBIDE-16072 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: browsersim > Reporter: Vlado Pakan > Assignee: Ilya Buziuk > Fix For: 4.2.0.Alpha1 > > > Is it even technically possible with Ripple? > Any alternatives? > https://github.com/phonegap-build/ChildBrowser -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16072) BrowserSim: Can we support ChildBrowser plugin in cordovasim

by Vlado Pakan (JIRA)

Vlado Pakan created JBIDE-16072: ----------------------------------- Summary: BrowserSim: Can we support ChildBrowser plugin in cordovasim Key: JBIDE-16072 URL: https://issues.jboss.org/browse/JBIDE-16072 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: browsersim Reporter: Vlado Pakan Assignee: Ilya Buziuk Fix For: 4.1.1.CR1, 4.2.0.Alpha1 Is it even technically possible with Ripple? Any alternatives? https://github.com/phonegap-build/ChildBrowser -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15304) NullPointerExceptions in JAX-RS doesn't report what project is affected

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15304?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-15304: --------------------------------------- [~dgolovin], Apparently, yes. If you can verify it by yourself, that would be fine. Thanks. > NullPointerExceptions in JAX-RS doesn't report what project is affected > ----------------------------------------------------------------------- > > Key: JBIDE-15304 > URL: https://issues.jboss.org/browse/JBIDE-15304 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.1.0.Final > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 4.1.1.Alpha2, 4.2.0.Alpha1 > > > I've seen this exception happens many times when I have several projects imported out of JBoss Central: > {code}java.lang.NullPointerException > at org.jboss.tools.ws.jaxrs.core.jdt.JavaMethodSignaturesVisitor.visit(JavaMethodSignaturesVisitor.java:105) > at org.eclipse.jdt.core.dom.MethodDeclaration.accept0(MethodDeclaration.java:489) > at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2514) > at org.eclipse.jdt.core.dom.ASTNode.acceptChildren(ASTNode.java:2585) > at org.eclipse.jdt.core.dom.TypeDeclaration.accept0(TypeDeclaration.java:484) > at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2514) > at org.eclipse.jdt.core.dom.ASTNode.acceptChildren(ASTNode.java:2585) > at org.eclipse.jdt.core.dom.CompilationUnit.accept0(CompilationUnit.java:220) > at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2514) > at org.jboss.tools.ws.jaxrs.core.jdt.JdtUtils.resolveMethodSignatures(JdtUtils.java:674) > at org.jboss.tools.ws.jaxrs.core.jdt.CompilationUnitsRepository.mergeAST(CompilationUnitsRepository.java:113) > at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JavaElementDeltaScanner.scanDelta(JavaElementDeltaScanner.java:119) > at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JavaElementDeltaScanner.scanAndFilterEvent(JavaElementDeltaScanner.java:71) > at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JavaElementChangedBuildJob.run(JavaElementChangedBuildJob.java:54) > at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JavaElementChangedBuildJob.execute(JavaElementChangedBuildJob.java:41) > at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JavaElementChangedListener.elementChanged(JavaElementChangedListener.java:69) > at org.eclipse.jdt.internal.core.DeltaProcessor$4.run(DeltaProcessor.java:1682) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.jdt.internal.core.DeltaProcessor.notifyListeners(DeltaProcessor.java:1672) > at org.eclipse.jdt.internal.core.DeltaProcessor.fireReconcileDelta(DeltaProcessor.java:1524) > at org.eclipse.jdt.internal.core.DeltaProcessor.fire(DeltaProcessor.java:1483) > at org.eclipse.jdt.internal.core.JavaModelOperation.run(JavaModelOperation.java:769) > at org.eclipse.jdt.internal.core.JavaModelOperation.runOperation(JavaModelOperation.java:788) > at org.eclipse.jdt.internal.core.CompilationUnit.reconcile(CompilationUnit.java:1247) > at org.eclipse.jdt.internal.ui.text.java.JavaReconcilingStrategy.reconcile(JavaReconcilingStrategy.java:126) > at org.eclipse.jdt.internal.ui.text.java.JavaReconcilingStrategy.access$0(JavaReconcilingStrategy.java:108) > at org.eclipse.jdt.internal.ui.text.java.JavaReconcilingStrategy$1.run(JavaReconcilingStrategy.java:89) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.jdt.internal.ui.text.java.JavaReconcilingStrategy.reconcile(JavaReconcilingStrategy.java:87) > at org.eclipse.jdt.internal.ui.text.java.JavaReconcilingStrategy.initialReconcile(JavaReconcilingStrategy.java:178) > at org.eclipse.jdt.internal.ui.text.CompositeReconcilingStrategy.initialReconcile(CompositeReconcilingStrategy.java:114) > at org.eclipse.jdt.internal.ui.text.JavaCompositeReconcilingStrategy.initialReconcile(JavaCompositeReconcilingStrategy.java:136) > at org.eclipse.jface.text.reconciler.MonoReconciler.initialProcess(MonoReconciler.java:105) > at org.eclipse.jdt.internal.ui.text.JavaReconciler.initialProcess(JavaReconciler.java:406) > at org.eclipse.jface.text.reconciler.AbstractReconciler$BackgroundThread.run(AbstractReconciler.java:173) > {code} > couldn't catch exact steps to replicate, because I have many projects in workspace and log entry doesn't provide additional info about project. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16035) Error when removing plugin via Project Explorer

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16035?page=com.atlassian.jira.plugi... ] Vlado Pakan closed JBIDE-16035. ------------------------------- I'm also not able to replicate this issue anymore either on Linux and on OSX > Error when removing plugin via Project Explorer > ----------------------------------------------- > > Key: JBIDE-16035 > URL: https://issues.jboss.org/browse/JBIDE-16035 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.1.1.CR1 > Environment: Fedora 18 64 bit, JBDS7.1.0.CR1 CR1-v20131116-1929-B543 > Reporter: Vlado Pakan > Priority: Critical > Fix For: 4.1.1.CR1 > > > See https://issues.jboss.org/browse/JBIDE-15864?focusedCommentId=12924803&pag... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15622) Automatically open/send report when log has error

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15622?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-15622: ---------------------------------------- {quote}Do we really need a new project? What about reporting to JBT or JBDS project without any component set, and then the bug reviewer would route the project to the right component, and may assign a Fix Version.{quote} This may be an option for Help->Report Problem Dialog but it can become to noisy if we allow to create issues directly to main JIRA for exceptions from log. {quote}About Action 7 "Return link to created JIRA": What about directly opening JIRA URL in the internal browser?{quote} A good idea. > Automatically open/send report when log has error > ------------------------------------------------- > > Key: JBIDE-15622 > URL: https://issues.jboss.org/browse/JBIDE-15622 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: common/jst/core > Affects Versions: 4.1.1.Alpha1 > Reporter: Mickael Istria > > *Where to:* > 1. Error Dialog – when problem occurs Error Dialog appears and provides opportunity to report a bug > 2. Error Log View (Tool-bar, Menu, Context menu) – report problem for selected stack-trace > 3. Help->Report Problem Dialog – report problem which may be not related with any exceptions > 1. and 2. should create issues in “special” project (see Preconditions). 3. may create issues directly to project Tools (JBoss Tools)? > *Feature list:* > 1. Log in/Anonymous bug reporting (If the user has login to JIRA he can report issues with it. Or he can do it anonymously) > 2. Check Exception Stack-trace for duplicate > 3. Report should contain all needed (useful) information about user's environment (JDK/JRE version, eclipse version, OS version, configuration, etc) > 4. As much as possible fields should be filled up automatically (project, issue type, priority, component/s, affects version/s, environment) may be some of them should be filled up later by Administrator > 5. User should be able to see all the data he is going to send > 6. Show communication errors > 7. Return link to created JIRA > 8. Inform user about the general/common process of bug reporting (see Work-flow) > 9. Option to attach log file > 10. Option to attach screen-shot > *Preconditions:* > 1. We need to create “special” project in JIRA to primary report issue to with anonymous (or dedicated) user. > 2. We need person as Administrator (QE-?) to periodically verifying issue from “special” project. > *Work-flow:* > 1. User decides/agrees to report the problem (see list Where to) > 2. Report Problem dialog appears, user fills up the form > 2. Dialog checks for existing exception stack-traces (when stack-trace available) or by key-words from field summary. > 3. If validation passes dialog creates issue in “special” project of JIRA (see Preconditions) > 4. User gets link to created issue and short description of what will happen next. (features 7. 8.) > 5. Administrator should periodically check “special” project and verify all issues. Administrator may reject issue or correct (versions, components etc, if needed) and move to project Tools (JBoss Tools). > *Primary Description:* > JBT should set up an ILogListener on the Eclipse log and send an error report whenever something is logged as error. > As it's probably not possible to send the error report without asking users, it should show the "Report problem" page. > NetBeans does that and has reported an actual quality benefit. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13743) BrowserSim: Can we support ChildBrowser plugin in cordovasim

by Yahor Radtsevich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13743?page=com.atlassian.jira.plugi... ] Yahor Radtsevich commented on JBIDE-13743: ------------------------------------------ [~vpakan] the issue on Fedora is seems to be the same as JBIDE-16060. Could you please test it on another system and close it if everything is fine there? > BrowserSim: Can we support ChildBrowser plugin in cordovasim > ------------------------------------------------------------ > > Key: JBIDE-13743 > URL: https://issues.jboss.org/browse/JBIDE-13743 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: browsersim > Reporter: Max Rydahl Andersen > Assignee: Ilya Buziuk > Fix For: 4.1.1.CR1, 4.2.0.Alpha1 > > Attachments: childBrowser.jpg > > > Is it even technically possible with Ripple? > Any alternatives? > https://github.com/phonegap-build/ChildBrowser -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16063) Aborting a command has strange behavior

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16063?page=com.atlassian.jira.plugi... ] Pavol Srna commented on JBIDE-16063: ------------------------------------ Hi Lincoln, I agree with you that this is rather a minor issue. Feel free to resolve as won't fix. > Aborting a command has strange behavior > ---------------------------------------- > > Key: JBIDE-16063 > URL: https://issues.jboss.org/browse/JBIDE-16063 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Reporter: Pavol Srna > Assignee: Koen Aers > Labels: respin-a > Fix For: 4.1.1.CR1 > > Attachments: forge-screen-1.png, forge-screen-2.png > > > I see 2 problems how aborting a command currently works. > * If the console is empty and you send Ctrl+C, then the text "[killed]" appears in the console. I guess nothing was actually killed. Then I try to for example create a new project and trigger: 'new-project --named testProject' and this command is swallowed or killed? Please see attached screenshot: > !forge-screen-1.png! > * Second, .. I tried several times to abort "an already in progress new-project" command but sometimes it succeeds and sometimes not. Like on my next screenshot. I figured out that it depends on the speed how fast I press the abort keys on the keyboard. It wasn't very hard for me to simulate the error. > !forge-screen-2.png! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16060) CordovaSim: InAppBrowser plugin doesn't work on Fedora

by Yahor Radtsevich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16060?page=com.atlassian.jira.plugi... ] Yahor Radtsevich updated JBIDE-16060: ------------------------------------- Description: See https://issues.jboss.org/browse/JBIDE-15512?focusedCommentId=12925267&pag... and https://issues.jboss.org/browse/JBIDE-13743?focusedCommentId=12925271&pag... was:See https://issues.jboss.org/browse/JBIDE-15512?focusedCommentId=12925267&pag... > CordovaSim: InAppBrowser plugin doesn't work on Fedora > ------------------------------------------------------ > > Key: JBIDE-16060 > URL: https://issues.jboss.org/browse/JBIDE-16060 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim > Affects Versions: 4.1.1.CR1 > Environment: Fedora 18 KDE 64 bit, JBDS7.1.0.CR1 CR1-v20131116-1929-B543 > Reporter: Vlado Pakan > Assignee: Ilya Buziuk > Labels: respin-a > Fix For: 4.1.1.CR1 > > > See https://issues.jboss.org/browse/JBIDE-15512?focusedCommentId=12925267&pag... > and > https://issues.jboss.org/browse/JBIDE-13743?focusedCommentId=12925271&pag... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16060) CordovaSim: InAppBrowser plugin doesn't work on Fedora

by Yahor Radtsevich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16060?page=com.atlassian.jira.plugi... ] Yahor Radtsevich updated JBIDE-16060: ------------------------------------- Description: See https://issues.jboss.org/browse/JBIDE-15512?focusedCommentId=12925267&pag... (was: See JBIDE-15512) > CordovaSim: InAppBrowser plugin doesn't work on Fedora > ------------------------------------------------------ > > Key: JBIDE-16060 > URL: https://issues.jboss.org/browse/JBIDE-16060 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim > Affects Versions: 4.1.1.CR1 > Environment: Fedora 18 KDE 64 bit, JBDS7.1.0.CR1 CR1-v20131116-1929-B543 > Reporter: Vlado Pakan > Assignee: Ilya Buziuk > Labels: respin-a > Fix For: 4.1.1.CR1 > > > See https://issues.jboss.org/browse/JBIDE-15512?focusedCommentId=12925267&pag... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16060) CordovaSim: InAppBrowser plugin doesn't work on Fedora

by Yahor Radtsevich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16060?page=com.atlassian.jira.plugi... ] Yahor Radtsevich updated JBIDE-16060: ------------------------------------- Labels: respin-a (was: ) > CordovaSim: InAppBrowser plugin doesn't work on Fedora > ------------------------------------------------------ > > Key: JBIDE-16060 > URL: https://issues.jboss.org/browse/JBIDE-16060 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim > Affects Versions: 4.1.1.CR1 > Environment: Fedora 18 KDE 64 bit, JBDS7.1.0.CR1 CR1-v20131116-1929-B543 > Reporter: Vlado Pakan > Assignee: Ilya Buziuk > Labels: respin-a > Fix For: 4.1.1.CR1 > > > See JBIDE-15512 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 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 November 2013