October 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21033) Add SmokeSuite to org.jboss.tools.mylyn.ui.bot.test

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21033?page=com.atlassian.jira.plugi... ] Len DiMaggio reassigned JBIDE-21033: ------------------------------------ Assignee: Len DiMaggio > Add SmokeSuite to org.jboss.tools.mylyn.ui.bot.test > --------------------------------------------------- > > Key: JBIDE-21033 > URL: https://issues.jboss.org/browse/JBIDE-21033 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: qa > Affects Versions: 4.3.0.Final > Reporter: Len DiMaggio > Assignee: Len DiMaggio > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-20990) Add "CDK Server" for start/stop for the CDK

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20990?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-20990: ------------------------------------- Everything here is PoC for now. None of these strings are permanent until they're in a GA release... and even then I'd imagine they can be changed with some annoyance to docs team. > 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)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3551) JavaEE Developer - be able to start/stop applications on docker with debug on/off

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3551?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-3551: --------------------------------- Fix Version/s: 9.1.0.Beta1 10.0.0.Alpha1 > JavaEE Developer - be able to start/stop applications on docker with debug on/off > --------------------------------------------------------------------------------- > > Key: JBDS-3551 > URL: https://issues.jboss.org/browse/JBDS-3551 > 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 JavaEE Developer I should be able to start/stop applications with debug turned on or off > Acceptance Criteria: > * Developer can start/stop an application from a central place, no CLI operations needed. > * Developer can start with or without debug enabled > * if necessary to restart when going from started to debugging or debugging to started the user should be asked if really want to restart > * When debug is on the Java debugger should be connected and any enabled breakpoints when hit should show up in the debugger -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3552) Developer - be able to incrementally deploy changes to docker containers

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3552?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-3552: --------------------------------- Fix Version/s: 9.1.0.Beta1 10.0.0.Alpha1 > Developer - be able to incrementally deploy changes to docker containers > ------------------------------------------------------------------------- > > Key: JBDS-3552 > URL: https://issues.jboss.org/browse/JBDS-3552 > 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 want to be able to incrementally deploy changes to my running application without building from scratch so I can see changes quickly. > Acceptance Criteria: > * Once the initial application is deployed changes made in the IDE should be deployed over to the containers filesystem/deployment. > * Changes that the runtime support to pickup dynamically (i.e. html/js for JavaEE) should take effect immediatly and be seen in a browser refresh. > * Changes that the the runtime requires a restart for (i.e. class files) should take effect when restarting the application (which should not require a rebuild from source) > * Same workflow should work for docker and openshift applications (but each might implement it differently using oc sync or docker rsync or volume mounts etc.) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[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)

10 years

1
0
0 / 0

[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)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-526) JBDSIS on marketplace contains category for WTP patches

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-526?page=com.atlassian.jira.plugin.... ] Paul Leacu resolved JBTIS-526. ------------------------------ Fix Version/s: 8.0.3.GA Resolution: Done Don't know how that got in there... > JBDSIS on marketplace contains category for WTP patches > ------------------------------------------------------- > > Key: JBTIS-526 > URL: https://issues.jboss.org/browse/JBTIS-526 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 8.0.3.GA > Environment: Eclipse Luna JEE SR2 > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Fix For: 8.0.3.GA > > Attachments: jbdsis803_marketplace_features.png > > > JBDSIS on marketplace contains category for WTP patches. Is this really intended (see the attached screenshot)? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-517) Update web pages for JBDS-IS 9.x

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-517?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-517: ---------------------------------- ok - try it again [~apodhrad] - thkx! > Update web pages for JBDS-IS 9.x > -------------------------------- > > Key: JBTIS-517 > URL: https://issues.jboss.org/browse/JBTIS-517 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: distribution > Affects Versions: 9.0.0.Alpha2 > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Priority: Minor > Fix For: 9.0.0.Alpha2 > > Attachments: jbdsis-900alpha2-webpage.png, jbdsis-900alpha2ea-webpage.png, jbdsis9_ea_webpage_2015_10_29.png, jbdsis9_webpage_2015_10_29.png > > > Update web pages for JBDS-IS 9.x at > * https://devstudio.redhat.com/9.0/development/updates/integration-stack/ > * https://devstudio.redhat.com/9.0/development/updates/integration-stack/ea... > See the attached screenshots of the current web pages. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-508) integration stack update sites mix discovery and earlyaccess causing inconsistent update mechanism

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-508?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-508: ---------------------------------- Release guide updated: https://github.com/jbdevstudio/jbdevstudio-devdoc/blob/master/release_gui... > integration stack update sites mix discovery and earlyaccess causing inconsistent update mechanism > -------------------------------------------------------------------------------------------------- > > Key: JBTIS-508 > URL: https://issues.jboss.org/browse/JBTIS-508 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: releng > Reporter: Max Rydahl Andersen > Assignee: Paul Leacu > Priority: Blocker > > While reviewing JBIDE-20803 I noticed the following: > {code} > jboss.discovery.site.integration-stack.url|jbosstools|4.2.4=http://downlo... > {code} > The stable release for 4.2.4 is stated to point to the stable integration stack url which on surface looks good: > But there are a few problems: > 1) why not just point to http://download.jboss.org/jbosstools/updates/stable/luna/ and have the above internal detail url composited in ? > 2) the actual composite behind it right now is http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4... which links in http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4... (our main sites should never composite earlyaccees since then when users install supported versions they suddenly will now also have access to earlyaccess. > #1 is mainly just to reduce the number of updatesites actually necessary for users to work with > #2 seems to be something inherent broken in the IS build since earlyaccess shold *never* be aggregated into the release site. > Any earlyaccess connectors should explicitly point to a *separate* earlyaccess site. > I would also have expected that the discovery site with the discovery plugins was kept *separate* from the actual update sites to avoid any coupling between these. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[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)

10 years

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues October 2015