July 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22574) Custom color of directives in eclipse plugin now working

by Daniel Dekany (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22574?page=com.atlassian.jira.plugi... ] Daniel Dekany commented on JBIDE-22574: --------------------------------------- As JBIDE-20180 is merged now, this can be closed. > Custom color of directives in eclipse plugin now working > -------------------------------------------------------- > > Key: JBIDE-22574 > URL: https://issues.jboss.org/browse/JBIDE-22574 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: freemarker > Environment: Eclipse Mars.2, FreeMarker IDE 1.5.100.Final-v20160603-0259-B419 > Reporter: Marcelo Marcelo > Priority: Minor > Attachments: freemarker-ide.png > > > When using Freemarker IDE on eclipse, I would like to customize editor's colors, since I am using a dark theme and the editor is not readable with the default colors. However, changing the color for directives does not work as expected. It only change colors of closing tags. > Example: <#list> remains dark blue (default color) but </#list> changes to the new color. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22739) Use simpler Surefire include/exclude pattern in root poms

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22739?page=com.atlassian.jira.plugi... ] George Gastaldi commented on JBIDE-22739: ----------------------------------------- There are a couple of tests in Forge that have the Abstract prefix ({{AbstractTextViewerTest}} and {{AbstractConsoleTest}} that tests the {{AbstractTextViewer}} and {{AbstractConsole}} classes respectively (probably fits in item #2 in this issue description). Perhaps I am missing the point in what would be the advantage of adding this exclude pattern? > Use simpler Surefire include/exclude pattern in root poms > --------------------------------------------------------- > > Key: JBIDE-22739 > URL: https://issues.jboss.org/browse/JBIDE-22739 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Priority: Minor > Fix For: 4.4.x > > > 1. In JBDS9, use these new default patterns for Surefire to define which test classes to run/exclude: > {code} > include = *Test*, *Test, *TestCase > exclude = *Abstract* > {code} > 2. If that causes test failures because running incorrectly named > abstract stuff, they can refactor, add their own root pom overrides, use > a TestSuite, or use @Ignore in test classes. > 3. If the count of tests run suddenly DROPS because the pattern isn't > running the correct # of tests, they can add their own root pom > overrides, or use a TestSuite. > Ref: http://lists.jboss.org/pipermail/jbosstools-dev/2015-January/009688.html -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

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

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22737?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-22737: ----------------------------------- Component/s: central-update (was: central) > 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-update > Affects Versions: 4.4.1.AM2 > Reporter: Marián Labuda > Assignee: Nick Boldt > 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22739) Use simpler Surefire include/exclude pattern in root poms

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22739?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-22739: ---------------------------------------- This question is for all component leads. I can say what projects will NOT benefit from that change for sure: javaee and jst. But it's up to component leads to decide if their component would benefit. [~xcoulon], [~ibuziuk], [~gastaldi], [~koen.aers], [~jeffmaury], [~adietish], [~rob.stryker], [~snjeza], [~gercan] > Use simpler Surefire include/exclude pattern in root poms > --------------------------------------------------------- > > Key: JBIDE-22739 > URL: https://issues.jboss.org/browse/JBIDE-22739 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Priority: Minor > Fix For: 4.4.x > > > 1. In JBDS9, use these new default patterns for Surefire to define which test classes to run/exclude: > {code} > include = *Test*, *Test, *TestCase > exclude = *Abstract* > {code} > 2. If that causes test failures because running incorrectly named > abstract stuff, they can refactor, add their own root pom overrides, use > a TestSuite, or use @Ignore in test classes. > 3. If the count of tests run suddenly DROPS because the pattern isn't > running the correct # of tests, they can add their own root pom > overrides, or use a TestSuite. > Ref: http://lists.jboss.org/pipermail/jbosstools-dev/2015-January/009688.html -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

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

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3965?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-3965: --------------------------------- Component/s: platform-installer (was: installer) > 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: platform-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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20180) > (and <) in expressions confuses the editor

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20180?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-20180: -------------------------------------- Fix Version/s: 4.4.1.AM2 (was: 4.3.x) (was: 4.4.x) Assignee: Alexey Kazakov Resolution: Done Pushed to master. Thanks! > > (and <) in expressions confuses the editor > -------------------------------------------- > > Key: JBIDE-20180 > URL: https://issues.jboss.org/browse/JBIDE-20180 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: freemarker > Affects Versions: 4.2.0.Beta2 > Reporter: Daniel Dekany > Assignee: Alexey Kazakov > Fix For: 4.4.1.AM2 > > > In the text editor, {{>}} closes the tag even if it's inside a string literal, or inside parentheses. Try: > * {{<#assign x = 'x>y'>}}: Notice how syntax coloring switches to black > * {{<#if (x > 0)></#if>}}: This one also breaks the outline view; no macros after this will appear in it. > More puzzling cases with {{<}}; these break outline view too: > * {{<#if x == '<'></#if><#macro m></#macro>}} > * {{<#if x < 1></#if><#macro m></#macro>}} > Note: There's an ongoing overhaul of the tokenizers (see in comments), which fixes these, and some more, like the handling of multi-line statements, of {{'}}-quoted stings, of FTL raw strings, of 2.3.22 identifier escapings, gives more detailed syntax highlighting, etc. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-10949) Drag and Drop to the Forge Console

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-10949?page=com.atlassian.jira.plugi... ] George Gastaldi closed JBIDE-10949. ----------------------------------- Fix Version/s: (was: 4.2.x) Assignee: George Gastaldi (was: Koen Aers) Resolution: Won't Do Agree with [~maxandersen]. Closing as Won't Do. > Drag and Drop to the Forge Console > ---------------------------------- > > Key: JBIDE-10949 > URL: https://issues.jboss.org/browse/JBIDE-10949 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: forge > Reporter: Jim Tyrrell > Assignee: George Gastaldi > Priority: Minor > > It would be great to be able to drag and drop artifacts from the project explorer into the Forge Console. ie instead of having to cd a large path, just drag the component in. Easier then maybe a right click and open... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19531) Forge console doesn't start without any error reported in eclipse UI when "VM Arguments" have errors

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19531?page=com.atlassian.jira.plugi... ] George Gastaldi closed JBIDE-19531. ----------------------------------- Fix Version/s: (was: 4.3.x) Assignee: George Gastaldi (was: Koen Aers) Resolution: Out of Date Closing as Out of Date. VM Arguments are not used in Forge 3.x > Forge console doesn't start without any error reported in eclipse UI when "VM Arguments" have errors > ---------------------------------------------------------------------------------------------------- > > Key: JBIDE-19531 > URL: https://issues.jboss.org/browse/JBIDE-19531 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.2.3.CR1 > Reporter: Denis Golovin > Assignee: George Gastaldi > > See Steps to replicate. It doesn't report any errors about forge start. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18717) Generate entities from tables silently fails with no classes generated on PostgreSQL 9.3

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18717?page=com.atlassian.jira.plugi... ] George Gastaldi commented on JBIDE-18717: ----------------------------------------- Can you confirm this is still happening? I haven't been able to reproduce it with the current version > Generate entities from tables silently fails with no classes generated on PostgreSQL 9.3 > ---------------------------------------------------------------------------------------- > > Key: JBIDE-18717 > URL: https://issues.jboss.org/browse/JBIDE-18717 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge, hibernate > Affects Versions: 4.2.0.Final > Reporter: Xavier Coulon > Assignee: Koen Aers > Fix For: 4.2.x, 4.3.x > > > When trying to generate an entity from the single table I have in a PostgreSQL database (a table named "Conference" in the public schema), nothing happens, depiste the fact that I could select the table when using the Forge wizard. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22738) Image registry URL becomes null when going between Connection and Deploy pages on Deploy image to OS wizard

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22738?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich edited comment on JBIDE-22738 at 7/14/16 10:51 AM: ------------------------------------------------------------------------- It is possible in ConnectionWizardPageModel.saveConnection() after calling update() retrieve the shared connection {code} connection = ConnectionsRegistrySingleton.getInstance().getByUrl(ConnectionURL.forConnection(connection)); {code} or, to make it more simple, method ConnectionsRegistry.update(currentConnection, updatedConnection) may return the resolved connection. However, all wizards listening for connection change now notice only instance change when they are notified after connect() with wizard.setConnection(connection); That should be addressed in some way or maybe ignored depending on wizard. was (Author: scabanovich): It is possible in ConnectionWizardPageModel.saveConnection() after calling update() retrieve the shared connection {code} connection = ConnectionsRegistrySingleton.getInstance().getByUrl(ConnectionURL.forConnection(connection)); {code} However, all wizards listening for connection change now notice only instance change when they are notified after connect() with wizard.setConnection(connection); That should be addressed in some way or maybe ignored depending on wizard. > Image registry URL becomes null when going between Connection and Deploy pages on Deploy image to OS wizard > ----------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22738 > URL: https://issues.jboss.org/browse/JBIDE-22738 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: docker, openshift > Affects Versions: 4.4.1.AM1 > Reporter: Dmitry Bocharov > Attachments: WAY1.webm, WAY2.webm > > -- 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