July 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22546) Project is not refreshed automatically after Scaffold Generate

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22546?page=com.atlassian.jira.plugi... ] Josef Kopriva closed JBIDE-22546. --------------------------------- Closing. Refresh is working: tested on FC24 and OS X El Capitan. Tested in: Red Hat JBoss Developer Studio Version: 10.0.1.AM2 Build id: AM2-v20160713-1835-B5660 Build date: 20160713-1835 > Project is not refreshed automatically after Scaffold Generate > -------------------------------------------------------------- > > Key: JBIDE-22546 > URL: https://issues.jboss.org/browse/JBIDE-22546 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.4.0.Alpha2 > Reporter: Pavol Srna > Assignee: George Gastaldi > Fix For: 4.4.1.AM2 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-805) Fuse: Fix all automated tests for 8.0.0.Beta3

by Tomáš Sedmík (JIRA)

Tomáš Sedmík created JBTIS-805: ---------------------------------- Summary: Fuse: Fix all automated tests for 8.0.0.Beta3 Key: JBTIS-805 URL: https://issues.jboss.org/browse/JBTIS-805 Project: JBoss Tools Integration Stack Issue Type: Task Components: Fuse IDE, QE Affects Versions: 4.3.1.Final Reporter: Tomáš Sedmík Assignee: Tomáš Sedmík Priority: Blocker automated tests have to be adapted to changes in Fuse Tooling 8.0.0.Beta3 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22734) Please clarify CDK usage

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22734?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-22734: --------------------------------------- I created an installer issue to include the note: JBDS-3965 > Please clarify CDK usage > ------------------------ > > Key: JBIDE-22734 > URL: https://issues.jboss.org/browse/JBIDE-22734 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: cdk, docker > Environment: CDK, as used in DevStudio and installed via Development Suite. > Reporter: Rick Wagner > > * * This use case may be attributable to user error. Please weigh implementation cost accordingly. * * > After using the Development Suite installer, the user arrives in a newly installed DevStudio instance but without clear instructions on how to use the CDK. In my first attempt, I relied upon previous CDK experience and went to a command-line to start the CDK with 'vagrant up'. This resulted in a failure of later DevStudio components. > The proper trail is to go to the 'Servers' tab in DevStudio to bring up the environment. (Then DevStudio components like the Docker explorer will properly self-configure. This does *not* happen when the CDK is brought up manually as I had done.) > Please consider, look for ways to prevent other users from taking a similar path. Thanks! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3965) Add a note on how to launch cdk in last page of devsuite installer

by Martin Malina (JIRA)

Martin Malina created JBDS-3965: ----------------------------------- Summary: Add a note on how to launch cdk in last page of devsuite installer Key: JBDS-3965 URL: https://issues.jboss.org/browse/JBDS-3965 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Feature Request Components: installer Affects Versions: 10.1.0.AM2 Reporter: Martin Malina Recently, [~rick_wagner] gave us some feedback on how he tried to use the devsuite installer and then connect to the docker daemon running in cdk. This is described here: JBIDE-22734 What happened was that Rick didn't know he was supposed to start CDK from the Servers view. Having some prior knowledge of CDK, he started it from CLI. Then he went to the Docker Explorer view and wanted to connect to cdk's docker daemon. Normally, the docker connection will be created for you automatically, but that assumes you start the cdk adapter in Servers View. So here's a proposal: Perhaps at the end of the devsuite installer, just before devstudio is launched, we could briefly note that to start using CDK, you can start it from the Server view, once devstudio is launched? Please note that the actual name of the server adapter is probably Container Runtime Environment, but I'm not 100 % sure, this needs to be verified. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22737) No connectors found for Central

by Marián Labuda (JIRA)

Marián Labuda created JBIDE-22737: ------------------------------------- Summary: No connectors found for Central Key: JBIDE-22737 URL: https://issues.jboss.org/browse/JBIDE-22737 Project: Tools (JBoss Tools) Issue Type: Bug Components: central Affects Versions: 4.4.1.AM2 Reporter: Marián Labuda Priority: Critical Upon devstudio start there are following errors in error log and software update tab in central is not working (no connectors found): {code} No URL set for discovery catalog. Property jboss.discovery.directory.url is missing! An exception stack trace is not available. {code} {code} All attempts to discover connectors have failed An exception stack trace is not available. Failed to get connectors from RemoteProxyWizardDiscoveryStrategy java.lang.NullPointerException at java.net.URI$Parser.parse(URI.java:3042) at java.net.URI.<init>(URI.java:588) at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy.loadRegistry(RemoteExternalBundleDiscoveryStrategy.java:90) at org.jboss.tools.discovery.core.internal.connectors.xpl.ExternalBundleDiscoveryStrategy.performDiscovery(ExternalBundleDiscoveryStrategy.java:117) at org.jboss.tools.discovery.core.internal.connectors.ChainedDiscoveryStrategy.performDiscovery(ChainedDiscoveryStrategy.java:68) at org.eclipse.mylyn.internal.discovery.core.model.ConnectorDiscovery.performDiscovery(ConnectorDiscovery.java:114) at org.jboss.tools.central.internal.discovery.wizards.ProxyWizardManager.loadWizards(ProxyWizardManager.java:107) at org.jboss.tools.central.internal.discovery.wizards.ProxyWizardUpdateJob.run(ProxyWizardUpdateJob.java:47) 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22735) CDK Server adapter is not available in Quick Access bar when typing "cdk"

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22735?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-22735: ------------------------------------- Suggested command name: Launch Container Development Environment (CDK) > CDK Server adapter is not available in Quick Access bar when typing "cdk" > ------------------------------------------------------------------------- > > Key: JBIDE-22735 > URL: https://issues.jboss.org/browse/JBIDE-22735 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.4.0.Final > Reporter: Alexey Kazakov > Assignee: Rob Stryker > Priority: Critical > > I guess this is a side effect of renaming "CDK Server Adapter" to "Container Development Environment". > We need to investigate if the only way to make the adapter available for "cdk" is to have "cdk" mentioned in the server type name. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22735) CDK Server adapter is not available in Quick Access bar when typing "cdk"

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22735?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-22735: ------------------------------------- I can add a second command with "Launch CDK Server Adapter" to do the same thing, but, there's no way to get "Launch Container Development Environment" to show up when the user types "CDK". It's very clearly string-based, and also wouldn't make much sense if a user typed CDK and the resultant action didn't have the letters CDK anywhere in it. I also thought this goes against what our branding requirements are now. As I understood it, having CDK in this location wouldn't be appropriate. The user *can* type "cde" and the action "Launch Container Development Environment" will show up in the filtered list. If this is acceptable, I'd guess we need to update documentation. Again, I can add a second action that has the other language, so that whether user types "CDK" or "CDE" will behave the same way. But the question is whether we **want** to show this action when a user types CDK, or if that's an outdated usecase. > CDK Server adapter is not available in Quick Access bar when typing "cdk" > ------------------------------------------------------------------------- > > Key: JBIDE-22735 > URL: https://issues.jboss.org/browse/JBIDE-22735 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.4.0.Final > Reporter: Alexey Kazakov > Assignee: Rob Stryker > Priority: Critical > > I guess this is a side effect of renaming "CDK Server Adapter" to "Container Development Environment". > We need to investigate if the only way to make the adapter available for "cdk" is to have "cdk" mentioned in the server type name. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22736) Freemarker test job is not triggered when a PR submitted

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22736?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-22736: ---------------------------------------- cc: [~mickael_istria] > Freemarker test job is not triggered when a PR submitted > --------------------------------------------------------- > > Key: JBIDE-22736 > URL: https://issues.jboss.org/browse/JBIDE-22736 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.1.AM1 > Reporter: Alexey Kazakov > Assignee: Nick Boldt > > "testPR" doesn't help. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22736) Freemarker test job is not triggered when a PR submitted

by Alexey Kazakov (JIRA)

Alexey Kazakov created JBIDE-22736: -------------------------------------- Summary: Freemarker test job is not triggered when a PR submitted Key: JBIDE-22736 URL: https://issues.jboss.org/browse/JBIDE-22736 Project: Tools (JBoss Tools) Issue Type: Bug Components: build Affects Versions: 4.4.1.AM1 Reporter: Alexey Kazakov Assignee: Nick Boldt "testPR" doesn't help. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21819) Freemarker syntax highlighting issues with square brackets syntax

by Daniel Dekany (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21819?page=com.atlassian.jira.plugi... ] Daniel Dekany edited comment on JBIDE-21819 at 7/13/16 6:29 PM: ---------------------------------------------------------------- The overhauled scanners of JBIDE-20180 (PR sent) happen to solve these. It's not to say that it makes square bracket syntax handling perfect (for example, if the syntax changes after you have opened the file, it won't re-scan the document automatically), but it solves the specific problems describe here. was (Author: ddekany): The overhauled scanners of JBIDE-20180 (PR sent) happens to solve these. It's not to say that it makes square bracket syntax handling perfect (for example, if the syntax changes after you have opened the file, it won't re-scan the document automatically), but it solves the specific problems describe here. > Freemarker syntax highlighting issues with square brackets syntax > ----------------------------------------------------------------- > > Key: JBIDE-21819 > URL: https://issues.jboss.org/browse/JBIDE-21819 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: freemarker > Affects Versions: 4.3.0.Final > Reporter: Kari Aliranta > Fix For: LATER > > > Ftl file (square syntax) highlighting seems to have two issues in the latest final, i.e.: > 1. It needs user input to engage (except for interpolation tags, i.e. ${somevariable}) > 2. It is stopped by ${somevariable} tags that are NOT within brackets > h2. Example > This is best exemplified by following beginning of an actual ftl file: > (*1*, *2* etc. with stars are my markings for referencing, and are NOT in actual FTL file) > {code} > *1*[#ftl attributes={"layout":"defaultLayout"} /] > [#if cmpsContainer??] > [#if cmpsContainer.getComponent('protocols')??] > [#assign protocols = cmpsContainer.getComponent('protocols') /] > [/#if] > [/#if] > *2* > <script>head.load("${root}/lib/redbox.js");</script> > *3*[(a)alerts.success placeholder="${defaultPlaceholder}" class="fade alert-fixed"]${uitags.assignmentRemoved}*4*[/(a)alerts.success] > {code} > The following happens: > - When opening the file, the only things highlighted are the ${root} and ${uitags.assignmentRemoved} (considered "interpolation" in Freemarker syntax highlighting configuration) > - You need to write anything at *1* to engage highlighting other syntax, in which case the highlighting runs up until *2* > - You then need to write anything at *3* to continue highlighting, in which case the hightlighting stops at *4*, and you then need to write anything at *4* to make it continue > - Note that the highlighting does NOT stop at ${defaultPlaceholder} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 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 July 2016