July 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22659) Error marker information should come from the reconciler thread

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22659?page=com.atlassian.jira.plugi... ] Ondrej Dockal closed JBIDE-22659. --------------------------------- Verified on: Version: 10.0.1.AM2 Build id: AM2-v20160720-1632-B5674 Closing. > Error marker information should come from the reconciler thread > --------------------------------------------------------------- > > Key: JBIDE-22659 > URL: https://issues.jboss.org/browse/JBIDE-22659 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: freemarker > Reporter: Daniel Dekany > Assignee: Alexey Kazakov > Fix For: 4.4.1.AM2 > > > The template is parsed with the actual FreeMarker parser, and the resulting exception (if any) is translated to an Eclipse error marker. The parsing happens asynchronously. This is fine so far. What's strange is that instead of relying on the standard reconciler mechanism, {{org.jboss.ide.eclipse.freemarker.editor.Editor}} tries to figure out when that information needs to be recalculated by examining the keydown events, instead of real change events. Thus it doesn't work if you are inserting text solely with mouse for example. Also the {{Editor}} tries to do this after each key stroke (unlike the reconciler mechanism, which waits until you stop typing for a moment). Also the asynchronous task execution it does has a flaw because of which sometimes ignores the last few changes. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22700) Upgrade to FreeMarker 2.3.25

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22700?page=com.atlassian.jira.plugi... ] Ondrej Dockal closed JBIDE-22700. --------------------------------- Verified on: Version: 10.0.1.AM2 Build id: AM2-v20160720-1632-B5674 closing... > Upgrade to FreeMarker 2.3.25 > ---------------------------- > > Key: JBIDE-22700 > URL: https://issues.jboss.org/browse/JBIDE-22700 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: freemarker > Reporter: Daniel Dekany > Assignee: Alexey Kazakov > 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] (JBIDE-20386) Autocompleation uses very outdated data

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20386?page=com.atlassian.jira.plugi... ] Ondrej Dockal closed JBIDE-20386. --------------------------------- Verified on: Version: 10.0.1.AM2 Build id: AM2-v20160720-1632-B5674 closing... > Autocompleation uses very outdated data > --------------------------------------- > > Key: JBIDE-20386 > URL: https://issues.jboss.org/browse/JBIDE-20386 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: freemarker > Reporter: Daniel Dekany > Assignee: Alexey Kazakov > Fix For: 4.4.1.AM2 > > > When you press Ctrl+Space after {{<#}} or in an expression after {{foo?}}, the list of directive names, and especially the list of built-in names shown is very outdated. Instead of maintaining these lists manually, the list of directive names could be get from {{freemarker.template.Configuration.getSupportedBuiltInDirectiveNames()}}, and the list of built-in names from {{Configuration.getSupportedBuiltInNames()}}. > Some complication since 2.3.23 is that the list of names should be filtered based on {{Template.getActualNamingConvention()}} (which either returns {{Configuration.LEGACY_NAMING_CONVENTION}} or {{Configuration.CAMEL_CASE_NAMING_CONVENTION}}). Though the algorithm for that is simple: If a name contains upper case letter then it's camel case. Otherwise, if it contains {{_}} then it belongs to the legacy naming convention. Otherwise if it's a directive name that equals to a lower-cased camel case directive name, then it's legacy naming convention (consider {{elseIf}} VS {{elseif}}). Otherwise the name belongs to both naming conventions. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3883) "Download & install" button is enabled during detection after going back and forth again

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3883?page=com.atlassian.jira.plugin.... ] Jan Richter closed JBDS-3883. ----------------------------- Verified with B237. > "Download & install" button is enabled during detection after going back and forth again > ---------------------------------------------------------------------------------------- > > Key: JBDS-3883 > URL: https://issues.jboss.org/browse/JBDS-3883 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.0.0.Alpha1 > Reporter: Jan Richter > Assignee: Denis Golovin > Priority: Minor > Fix For: 10.1.0.AM2 > > > Normally, the user cannot proceed with the installation on the confirm page until component detection has finished. If after that they click back and continue again, the detection is launched again, but it allows the user to continue anyway. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3960) Rename platform installer artifacts to start with "devsuite" instead of "development-suite"

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBDS-3960?page=com.atlassian.jira.plugin.... ] Ondrej Dockal closed JBDS-3960. ------------------------------- Verified on devsuite-1.0.0-GA-20160722-237-installer.exe. Closing. > Rename platform installer artifacts to start with "devsuite" instead of "development-suite" > ------------------------------------------------------------------------------------------- > > Key: JBDS-3960 > URL: https://issues.jboss.org/browse/JBDS-3960 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.0.0.GA > Reporter: Nick Boldt > Assignee: Jan Richter > Fix For: 10.1.0.AM2 > > > Max said: "I don't see dev studio in that download dialog - I see "Development-suite" ...which btw. is wrong, it should be devsuite here. Have you opened bug for this already ?" > So, I've opened a bug for this, already. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22803) When OS projects are created and deleted, seems Openshift explorer restores non existing values

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22803?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-22803: ------------------------------- Labels: explorer openshift openshift_v3 (was: ) > When OS projects are created and deleted, seems Openshift explorer restores non existing values > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-22803 > URL: https://issues.jboss.org/browse/JBIDE-22803 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Jeff MAURY > Labels: explorer, openshift, openshift_v3 > Fix For: 4.4.1.AM3 > > Attachments: screenshot-1.png > > > EXEC: create an Openshift project > EXEC: expand it > EXEC: Create an application in this project (nodejs-example) > ASSERT: wait for the pod to be available > EXEC: delete the Openshit project > EXEC: create an Openshift project (using the same name. You may have to repeat this step as you may got error that it still exists) > EXEC: expand it > EXEC: Create an application in this project (nodejs-example) > EXEC: expand the nodejs-example node > ASSERT: you should see 2 pods the old one and the build pod you just created: [^screenshot-1.png] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22803) When OS projects are created and deleted, seems Openshift explorer restores non existing values

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22803?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-22803: ------------------------------- Attachment: screenshot-1.png > When OS projects are created and deleted, seems Openshift explorer restores non existing values > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-22803 > URL: https://issues.jboss.org/browse/JBIDE-22803 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Jeff MAURY > Fix For: 4.4.1.AM3 > > Attachments: screenshot-1.png > > > EXEC: create an Openshift project > EXEC: expand it > EXEC: Create an application in this project (nodejs-example) > ASSERT: wait for the pod to be available > EXEC: delete the Openshit project > EXEC: create an Openshift project (using the same name. You may have to repeat this step as you may got error that it still exists) > EXEC: expand it > EXEC: Create an application in this project (nodejs-example) > EXEC: expand the nodejs-example node > ASSERT: you should see 2 pods the old one and the build pod you just created -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22803) When OS projects are created and deleted, seems Openshift explorer restores non existing values

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22803?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-22803: ------------------------------- Description: EXEC: create an Openshift project EXEC: expand it EXEC: Create an application in this project (nodejs-example) ASSERT: wait for the pod to be available EXEC: delete the Openshit project EXEC: create an Openshift project (using the same name. You may have to repeat this step as you may got error that it still exists) EXEC: expand it EXEC: Create an application in this project (nodejs-example) EXEC: expand the nodejs-example node ASSERT: you should see 2 pods the old one and the build pod you just created: [^screenshot-1.png] was: EXEC: create an Openshift project EXEC: expand it EXEC: Create an application in this project (nodejs-example) ASSERT: wait for the pod to be available EXEC: delete the Openshit project EXEC: create an Openshift project (using the same name. You may have to repeat this step as you may got error that it still exists) EXEC: expand it EXEC: Create an application in this project (nodejs-example) EXEC: expand the nodejs-example node ASSERT: you should see 2 pods the old one and the build pod you just created > When OS projects are created and deleted, seems Openshift explorer restores non existing values > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-22803 > URL: https://issues.jboss.org/browse/JBIDE-22803 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Jeff MAURY > Fix For: 4.4.1.AM3 > > Attachments: screenshot-1.png > > > EXEC: create an Openshift project > EXEC: expand it > EXEC: Create an application in this project (nodejs-example) > ASSERT: wait for the pod to be available > EXEC: delete the Openshit project > EXEC: create an Openshift project (using the same name. You may have to repeat this step as you may got error that it still exists) > EXEC: expand it > EXEC: Create an application in this project (nodejs-example) > EXEC: expand the nodejs-example node > ASSERT: you should see 2 pods the old one and the build pod you just created: [^screenshot-1.png] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22803) When OS projects are created and deleted, seems Openshift explorer restores non existing values

by Jeff MAURY (JIRA)

Jeff MAURY created JBIDE-22803: ---------------------------------- Summary: When OS projects are created and deleted, seems Openshift explorer restores non existing values Key: JBIDE-22803 URL: https://issues.jboss.org/browse/JBIDE-22803 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.4.1.AM2 Reporter: Jeff MAURY Fix For: 4.4.1.AM3 EXEC: create an Openshift project EXEC: expand it EXEC: Create an application in this project (nodejs-example) ASSERT: wait for the pod to be available EXEC: delete the Openshit project EXEC: create an Openshift project (using the same name. You may have to repeat this step as you may got error that it still exists) EXEC: expand it EXEC: Create an application in this project (nodejs-example) EXEC: expand the nodejs-example node ASSERT: you should see 2 pods the old one and the build pod you just created -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3960) Rename platform installer artifacts to start with "devsuite" instead of "development-suite"

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3960?page=com.atlassian.jira.plugin.... ] Jan Richter commented on JBDS-3960: ----------------------------------- Icons should now be fixed as well (sorry for that extra commit, didn't expect the sneaky fix :) ) > Rename platform installer artifacts to start with "devsuite" instead of "development-suite" > ------------------------------------------------------------------------------------------- > > Key: JBDS-3960 > URL: https://issues.jboss.org/browse/JBDS-3960 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.0.0.GA > Reporter: Nick Boldt > Assignee: Jan Richter > Fix For: 10.1.0.AM2 > > > Max said: "I don't see dev studio in that download dialog - I see "Development-suite" ...which btw. is wrong, it should be devsuite here. Have you opened bug for this already ?" > So, I've opened a bug for this, already. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 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