November 2013 - jbosstools-issues

[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 updated JBIDE-16063: ------------------------------- Fix Version/s: 4.1.1.CR1 (was: 4.1.1.Final) Labels: respin-a (was: ) > 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 > 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] (JBDS-2727) Cheatsheets for JBoss Central archetypes

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/JBDS-2727?page=com.atlassian.jira.plugin.... ] Vineet Reynolds commented on JBDS-2727: --------------------------------------- [~fbricon], I need to review the work I've done in this branch: https://github.com/VineetReynolds/jboss-wfk-quickstarts/tree/JDF-497 since I noticed that some of the actions are not executable from the cheatsheet. Some command don't exist for them, and hence I've written down the instructions in text. I'll finish it and pass it around for a review. If it is good enough, we can get it merged into the WFK quickstarts repo. I'll aim to get this completed by 22 Nov. I'd like to know if you need this earlier. > Cheatsheets for JBoss Central archetypes > ---------------------------------------- > > Key: JBDS-2727 > URL: https://issues.jboss.org/browse/JBDS-2727 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: central, requirements > Reporter: Burr Sutter > Assignee: Fred Bricon > Fix For: 7.1.0.GA > > Attachments: CHEATSHEET-CONTRIBUTING.html, CHEATSHEET-CONTRIBUTING.md > > > Our archetypes should have cheatsheets when imported/opened into eclipse. > Priority > 1) HTML5 - cheatsheet should focus the end-user's attention on index.html, editable in the VPE, with the jQuery Mobile Palette, it should also describe LiveReload setup and BrowserSim > 2) Java EE Web - cheatsheet should focus the end-user's attention on index.xhtml, editable in the VPE, with the JSF/RichFaces Palette. It should describe the JPA Member.java, the relationship between MemberController.java and index.xhtml, the purpose of MemberResourceRESTService.java and JaxRsActivator.java > Basically walk the user through the flow of events (from the UI to the backend) in the application > 3) RichFaces - cheatsheet should focus the end-user's attention on index.xhtml, editable in the VPE, with the JSF/RichFaces Palette. It should also describe resources/components/memberForm.xhtml and its use of <rich:validator/> and that tag's relationship with the JPA beanvalidations -- 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 updated JBIDE-16063: ------------------------------- Description: 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! was: 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! > 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 > Fix For: 4.1.1.Final > > 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-15875) Typo in description of Hybrid Mobile Tools in JBoss Central Update tab

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15875?page=com.atlassian.jira.plugi... ] Radim Hopp closed JBIDE-15875. ------------------------------ Verified in JBDS 7.1.0.CR1 > Typo in description of Hybrid Mobile Tools in JBoss Central Update tab > ---------------------------------------------------------------------- > > Key: JBIDE-15875 > URL: https://issues.jboss.org/browse/JBIDE-15875 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.1.1.Beta1 > Reporter: Michelle Murray > Assignee: Fred Bricon > Priority: Trivial > Fix For: 4.1.1.CR1 > > > JBoss Central Update tab, JBoss Hybrid Mobile description > Typo: aplications > applications > "Create and test hybrid mobile *applications* with Apache Cordova for Android + iOS" -- 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-15805) Livereload does not work with HTML files without <body>

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15805?page=com.atlassian.jira.plugi... ] Vlado Pakan closed JBIDE-15805. ------------------------------- Verified with JBDS7.1.0.CR1 CR1-v20131116-1929-B543 > Livereload does not work with HTML files without <body> > ------------------------------------------------------- > > Key: JBIDE-15805 > URL: https://issues.jboss.org/browse/JBIDE-15805 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: livereload > Affects Versions: 4.2.0.Alpha1 > Reporter: Alexey Kazakov > Assignee: Xavier Coulon > Fix For: 4.1.1.CR1 > > > Liveroload does not update HTML files if it does not have <body> tag which is not required by HTML5 spec. -- 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-15874) Typo in JBoss Central Updates tab: plugins > plug-ins

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15874?page=com.atlassian.jira.plugi... ] Radim Hopp closed JBIDE-15874. ------------------------------ Verified in JBDS 7.1.0.CR1 > Typo in JBoss Central Updates tab: plugins > plug-ins > ----------------------------------------------------- > > Key: JBIDE-15874 > URL: https://issues.jboss.org/browse/JBIDE-15874 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.1.1.Beta1 > Reporter: Michelle Murray > Assignee: Fred Bricon > Priority: Trivial > Fix For: 4.1.1.CR1 > > Attachments: Central_updates_plugin.png > > > JBoss Central Updates tab uses spelling "plugin" and "plugins". > There are two common spellings of this word: plugin and plug-in. Within Red Hat content services we follow the IBM style guide. It states that the hyphenated version should be used, so "plug-in". > So mispellings in updates tab should be fixed: > * plugin > plug-in > * plugins > plug-ins > Some example instances in image, more in actual tab: > !Central_updates_plugin.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-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 updated JBIDE-16063: ------------------------------- Description: 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! was: 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-screen1.png! > 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 > Fix For: 4.1.1.Final > > 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! -- 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 updated JBIDE-16063: ------------------------------- Description: 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-screen1.png! > 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 > Fix For: 4.1.1.Final > > 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-screen1.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-15170) Quickstart (helloworld-jms) added as part of JBIDE-14940 includes readme file with broken wiki links

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15170?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-15170: ---------------------------------------- Assignee: Jiri Peterka (was: Fred Bricon) > Quickstart (helloworld-jms) added as part of JBIDE-14940 includes readme file with broken wiki links > ---------------------------------------------------------------------------------------------------- > > Key: JBIDE-15170 > URL: https://issues.jboss.org/browse/JBIDE-15170 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.1.0.CR1 > Reporter: Len DiMaggio > Assignee: Jiri Peterka > Fix For: 4.1.1.Final > > > The Readme.md file for the new "backend" helloworld-jms quickstart includes the same content as: http://www.jboss.org/jdf/quickstarts/jboss-as-quickstart/helloworld-jms/ > The wiki links in the readme do not work. -- 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 Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15304?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-15304: ---------------------------------------- Assignee: Nick Boldt (was: Max Rydahl Andersen) > 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: Nick Boldt > 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

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