[JBoss JIRA] (JBDS-3550) Developer - autodetect the CDK in IDE
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3550?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov updated JBDS-3550:
---------------------------------
Fix Version/s: 9.0.1.Beta1
10.0.0.Alpha1
> Developer - autodetect the CDK in IDE
> -------------------------------------
>
> Key: JBDS-3550
> URL: https://issues.jboss.org/browse/JBDS-3550
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Story
> Components: docker
> Reporter: Max Rydahl Andersen
> Assignee: Xavier Coulon
> Fix For: 9.0.1.Beta1, 10.0.0.Alpha1
>
>
> User Story:
> As a Developer on first startup after the installer have run, the CDK should be configured in the IDE and be ready to use
> Acceptance Criteria:
> * If the CDK is running there should be an openshift connection that is configured with the right url and username and users should have been given a password that allows him to connect
> * if the CDK is running there should be a docker connection that is configured with the right connetion info, certifcates etc. to connect
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months
[JBoss JIRA] (JBDS-3549) Developer - start and stop the CDK easily from within the IDE
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3549?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov updated JBDS-3549:
---------------------------------
Fix Version/s: 10.0.0.Alpha1
> Developer - start and stop the CDK easily from within the IDE
> -------------------------------------------------------------
>
> Key: JBDS-3549
> URL: https://issues.jboss.org/browse/JBDS-3549
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Story
> Components: docker
> Reporter: Max Rydahl Andersen
> Assignee: Xavier Coulon
> Fix For: 9.1.0.Beta1, 10.0.0.Alpha1
>
>
> User Story:
> As a Developer I should be able to start and stop the CDK easily from within the IDE without having to know about internal details like vagrant or command line tools so I can get started quickly.
> Acceptance Criteria:
> * If CDK is not running, clicking start should bring up the CDK and I should be able to use the docker and openshift tooling against the CDK from Eclipse
> * If CDK is running already, clicking start should recognize that and not try to stop/halt it and then I should be able to use the docker and openshift tooling against the CDK from Eclipse
> * If CDK is running, clicking stop should halt the CDK and docker
> * When stopped, the docker and openshift configuraton should still stay in Eclipse, but should not work and give sensible errors when/if failing.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months
[JBoss JIRA] (JBIDE-18178) Forge Console throws exception when UP is kept pressed for some time
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18178?page=com.atlassian.jira.plugi... ]
George Gastaldi resolved JBIDE-18178.
-------------------------------------
Resolution: Out of Date
Cannot reproduce anymore. Looks like it's outdated.
> Forge Console throws exception when UP is kept pressed for some time
> --------------------------------------------------------------------
>
> Key: JBIDE-18178
> URL: https://issues.jboss.org/browse/JBIDE-18178
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Reporter: George Gastaldi
> Assignee: Vineet Reynolds
> Priority: Minor
> Fix For: 4.2.x
>
>
> {code}
> java.lang.Throwable: Unimplemented command: CURSOR_UP
> at org.jboss.tools.aesh.core.internal.ansi.AbstractCommand.handle(AbstractCommand.java:18)
> at org.jboss.tools.aesh.core.internal.ansi.AbstractCommand.handle(AbstractCommand.java:22)
> at org.jboss.tools.aesh.core.internal.io.DocumentInputOutputHandler.handleCommand(DocumentInputOutputHandler.java:42)
> at org.jboss.tools.aesh.core.internal.io.CommandFilter.filterOutput(CommandFilter.java:50)
> at org.jboss.tools.aesh.core.internal.io.AeshOutputStream.write(AeshOutputStream.java:27)
> at java.io.PrintStream.write(PrintStream.java:480)
> at sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:221)
> at sun.nio.cs.StreamEncoder.implFlushBuffer(StreamEncoder.java:291)
> at sun.nio.cs.StreamEncoder.flushBuffer(StreamEncoder.java:104)
> at java.io.OutputStreamWriter.flushBuffer(OutputStreamWriter.java:185)
> at java.io.PrintStream.write(PrintStream.java:527)
> at java.io.PrintStream.print(PrintStream.java:669)
> at org.jboss.aesh.console.AeshConsoleBuffer.redrawMultipleLines(AeshConsoleBuffer.java:207)
> at org.jboss.aesh.console.AeshConsoleBuffer.drawLine(AeshConsoleBuffer.java:128)
> at org.jboss.aesh.console.AeshInputProcessor.getHistoryElement(AeshInputProcessor.java:420)
> at org.jboss.aesh.console.AeshInputProcessor.parseOperation(AeshInputProcessor.java:164)
> at org.jboss.aesh.console.Console.processInternalOperation(Console.java:615)
> at org.jboss.aesh.console.Console.execute(Console.java:605)
> at org.jboss.aesh.console.Console.access$700(Console.java:58)
> at org.jboss.aesh.console.Console$6.run(Console.java:508)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months
[JBoss JIRA] (JBIDE-20990) Add "CDK Server" for start/stop for the CDK
by Burr Sutter (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20990?page=com.atlassian.jira.plugi... ]
Burr Sutter commented on JBIDE-20990:
-------------------------------------
Concerning "Red Hat CDK" - at what point does this string become permanent? It is possible we will have another name in the future.
> Add "CDK Server" for start/stop for the CDK
> -------------------------------------------
>
> Key: JBIDE-20990
> URL: https://issues.jboss.org/browse/JBIDE-20990
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: server
> Reporter: Max Rydahl Andersen
> Assignee: Rob Stryker
>
> We want to be able to start/stop CDK easily.
> Current suggestion is to use a server entry in server view that can start/stop vagrant by simply knowing its file location would be a good start.
> note: the vagrant image might already be running so just need to be able to take care of that.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months
[JBoss JIRA] (JBIDE-20982) JBDS consumes 40-50% CPU without any noticeable job in progress
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20982?page=com.atlassian.jira.plugi... ]
Snjezana Peco commented on JBIDE-20982:
---------------------------------------
I can't reproduce the issue on Linux and Windows.
Importing 200+ javaee7-samples projects takes a long time. Once they are imported, Eclipse/Java consumes 2+ GB RAM, but a minimal percent (<1%) of CPU.
I can't test on Mac. Try to test Eclipse Mars and some newer JDK.
> JBDS consumes 40-50% CPU without any noticeable job in progress
> ---------------------------------------------------------------
>
> Key: JBIDE-20982
> URL: https://issues.jboss.org/browse/JBIDE-20982
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: upstream
> Affects Versions: 4.2.0.Final
> Reporter: Xavier Coulon
> Assignee: Snjezana Peco
> Fix For: 4.4.x
>
> Attachments: jstack-JBDS-3147-1.txt, jstack-JBDS-3147-2.txt, jstack-JBDS-3147-3.txt, jstack-JBDS-3147-4.txt, Screen Shot 2014-09-11 at 16.06.20.png, Screen Shot 2014-09-12 at 09.22.31.png, Screen Shot 2014-09-12 at 12.33.40.png, Screen Shot 2014-09-12 at 17.49.48.png
>
>
> Steps to reproduce (on MacOSX):
> - import all WildFly Quickstarts (https://github.com/wildfly/quickstart)
> - restart the workbench
> - once all projects have been built and no job appears in the progress view, JBDS still consumes ~40% a CPU
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months