July 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3492) JBDS app icon and installer icon are not the same

by Nick Boldt (JIRA)

Nick Boldt created JBDS-3492: -------------------------------- Summary: JBDS app icon and installer icon are not the same Key: JBDS-3492 URL: https://issues.jboss.org/browse/JBDS-3492 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: installer Affects Versions: 9.0.0.Beta2 Reporter: Nick Boldt Assignee: Nick Boldt Attachments: jbds-installer-vs-installer-jbds-icon.png The icon used for the installer is a more-or-less solid red ball, but the icon for the JBDS app is a red ball with while circles through it. Unless this is a quirk of the way that izpack compresses/displays the icon, we may be using a different one for the installer than the app. This may also be an intentional design choice, so that if you're running JBDS and an installer you can tell which is which visually. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3492) JBDS app icon and installer icon are not the same

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3492?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3492: ----------------------------- Attachment: jbds-installer-vs-installer-jbds-icon.png > JBDS app icon and installer icon are not the same > ------------------------------------------------- > > Key: JBDS-3492 > URL: https://issues.jboss.org/browse/JBDS-3492 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.0.0.Beta2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Attachments: jbds-installer-vs-installer-jbds-icon.png > > > The icon used for the installer is a more-or-less solid red ball, but the icon for the JBDS app is a red ball with while circles through it. > Unless this is a quirk of the way that izpack compresses/displays the icon, we may be using a different one for the installer than the app. > This may also be an intentional design choice, so that if you're running JBDS and an installer you can tell which is which visually. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20376) [origin_intservice_59]local port displayed incorrectly when open port forwarding window again after forwarding with random port

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20376?page=com.atlassian.jira.plugi... ] Jeff Cantrill reassigned JBIDE-20376: ------------------------------------- Assignee: Jeff Cantrill > [origin_intservice_59]local port displayed incorrectly when open port forwarding window again after forwarding with random port > ------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20376 > URL: https://issues.jboss.org/browse/JBIDE-20376 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta2, 4.3.0.CR1 > Environment: 3.0.0.Beta2-v20150722-0236-B32 > 3.0.0.CR1-v20150723-1038-B887 > Reporter: Yue Wang > Assignee: Jeff Cantrill > Labels: application_wizard, openshift_v3 > > port forwarding with a random port(not 8080) and close the port forwarding window, then open the window again, you will find the 'Local Port' changes to '8080' -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20377) [origin_intservice_59]Port forwarding info disappeared after refreshing pods

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20377?page=com.atlassian.jira.plugi... ] Jeff Cantrill reassigned JBIDE-20377: ------------------------------------- Assignee: Jeff Cantrill > [origin_intservice_59]Port forwarding info disappeared after refreshing pods > ---------------------------------------------------------------------------- > > Key: JBIDE-20377 > URL: https://issues.jboss.org/browse/JBIDE-20377 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta2, 4.3.0.CR1 > Reporter: Yue Wang > Assignee: Jeff Cantrill > Labels: application_wizard, openshift_v3 > > Start a port forwarding, you can find port forwarding status 'Started' in 'Application port forwarding' window, then you refresh pod and go to 'Application port forwarding' window again, port forwarding status disappeared. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-647) Update JBDS 9.0.0 Install doc with info for offline zip

by Supriya Bharadwaj (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-647?page=com.atlassian.jira.plug... ] Supriya Bharadwaj commented on TOOLSDOC-647: -------------------------------------------- > Nick has confirmed that both the zips are required for the offline install (JBDS-3491). The section "http://docbuilder.usersys.redhat.com/23020/#Install_JBoss_Developer_Studi..." states this already. [~mhusnain], I think we are good to publish the guide now. WDYT? thanks - supriya > Update JBDS 9.0.0 Install doc with info for offline zip > ------------------------------------------------------- > > Key: TOOLSDOC-647 > URL: https://issues.jboss.org/browse/TOOLSDOC-647 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Components: Installation Guide > Affects Versions: 4.3.0.Final > Reporter: Supriya Bharadwaj > Assignee: Supriya Bharadwaj > Fix For: 4.3.0.Final > > > Change info in the Install JBoss Developer Studio BYOE when Offline section of the JBDS 9.0.0 Install guide to say that the user will need only one .zip (update archive) to install. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20388) Renaming an FTL file doesn't update the path of the open editor

by Daniel Dekany (JIRA)

Daniel Dekany created JBIDE-20388: ------------------------------------- Summary: Renaming an FTL file doesn't update the path of the open editor Key: JBIDE-20388 URL: https://issues.jboss.org/browse/JBIDE-20388 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: freemarker Reporter: Daniel Dekany Create a new file with name {{t1.ftl}}. Open it (with the FreeMarker IDE editor). In the Project Explorer's tree rename it to {{t2.ftl}}. Open {{t2.ftl}} too. Now you will have two open editors, both editing the same FTL file. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20388) Renaming an FTL file doesn't update the path of the open editor

by Daniel Dekany (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20388?page=com.atlassian.jira.plugi... ] Daniel Dekany updated JBIDE-20388: ---------------------------------- Issue Type: Bug (was: Enhancement) > Renaming an FTL file doesn't update the path of the open editor > --------------------------------------------------------------- > > Key: JBIDE-20388 > URL: https://issues.jboss.org/browse/JBIDE-20388 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: freemarker > Reporter: Daniel Dekany > > Create a new file with name {{t1.ftl}}. Open it (with the FreeMarker IDE editor). In the Project Explorer's tree rename it to {{t2.ftl}}. Open {{t2.ftl}} too. Now you will have two open editors, both editing the same FTL file. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20387) Use column number when navigating to errors, and more

by Daniel Dekany (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20387?page=com.atlassian.jira.plugi... ] Daniel Dekany updated JBIDE-20387: ---------------------------------- Description: The plugin doesn't utilize some tooling-centric information available in {{freemarker.core.ParseException}}, most importantly, the column number that Eclipse could utilize to jump at the error start inside the line. The information that's not used is (see {{plugins/org.jboss.ide.eclipse.freemarker/src/org/jboss/ide/eclipse/freemarker/editor/Editor.java}}): * {{getColumnNumber()}}, {{getEndColumnNumber()}} * {{getEndLineNumber()}} * {{getEditorMessage()}}: This should be used instead of {{getMessage()}} (though apparently the output of `getMessage()` is identical, it's actually because FM detects that it was called from JBoss Tools and then creates a message customized for that)). was: The plugin doesn't utilize some tooling-centric information available in {{freemarker.core.ParseException}}, most importantly, the column number that Eclipse could utilize to jump at the error start inside the line. The information that's not used is (see {{plugins/org.jboss.ide.eclipse.freemarker/src/org/jboss/ide/eclipse/freemarker/editor/Editor.java}}): * {{getColumnNumber()}}, {{getEndColumnNumber()}} * {{getEndLineNumber()}} * {{getEditorMessage()}}: This should be used instead of `getMessage()` (though apparently the output of `getMessage()` is identical, it's actually because FM detects that it was called from JBoss Tools and then creates a message customized for that)). > Use column number when navigating to errors, and more > ----------------------------------------------------- > > Key: JBIDE-20387 > URL: https://issues.jboss.org/browse/JBIDE-20387 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: freemarker > Reporter: Daniel Dekany > > The plugin doesn't utilize some tooling-centric information available in {{freemarker.core.ParseException}}, most importantly, the column number that Eclipse could utilize to jump at the error start inside the line. The information that's not used is (see {{plugins/org.jboss.ide.eclipse.freemarker/src/org/jboss/ide/eclipse/freemarker/editor/Editor.java}}): > * {{getColumnNumber()}}, {{getEndColumnNumber()}} > * {{getEndLineNumber()}} > * {{getEditorMessage()}}: This should be used instead of {{getMessage()}} (though apparently the output of `getMessage()` is identical, it's actually because FM detects that it was called from JBoss Tools and then creates a message customized for that)). -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20387) Use column number when navigating to errors, and more

by Daniel Dekany (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20387?page=com.atlassian.jira.plugi... ] Daniel Dekany updated JBIDE-20387: ---------------------------------- Description: The plugin doesn't utilize some tooling-centric information available in {{freemarker.core.ParseException}}, most importantly, the column number that Eclipse could utilize to jump at the error start inside the line. The information that's not used is (see {{plugins/org.jboss.ide.eclipse.freemarker/src/org/jboss/ide/eclipse/freemarker/editor/Editor.java}}): * {{getColumnNumber()}}, {{getEndColumnNumber()}} * {{getEndLineNumber()}} * {{getEditorMessage()}}: This should be used instead of {{getMessage()}} (though apparently the output of `getMessage()` is identical, it's actually because FM detects that it was called from JBoss Tools and then creates a message customized for that). was: The plugin doesn't utilize some tooling-centric information available in {{freemarker.core.ParseException}}, most importantly, the column number that Eclipse could utilize to jump at the error start inside the line. The information that's not used is (see {{plugins/org.jboss.ide.eclipse.freemarker/src/org/jboss/ide/eclipse/freemarker/editor/Editor.java}}): * {{getColumnNumber()}}, {{getEndColumnNumber()}} * {{getEndLineNumber()}} * {{getEditorMessage()}}: This should be used instead of {{getMessage()}} (though apparently the output of `getMessage()` is identical, it's actually because FM detects that it was called from JBoss Tools and then creates a message customized for that)). > Use column number when navigating to errors, and more > ----------------------------------------------------- > > Key: JBIDE-20387 > URL: https://issues.jboss.org/browse/JBIDE-20387 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: freemarker > Reporter: Daniel Dekany > > The plugin doesn't utilize some tooling-centric information available in {{freemarker.core.ParseException}}, most importantly, the column number that Eclipse could utilize to jump at the error start inside the line. The information that's not used is (see {{plugins/org.jboss.ide.eclipse.freemarker/src/org/jboss/ide/eclipse/freemarker/editor/Editor.java}}): > * {{getColumnNumber()}}, {{getEndColumnNumber()}} > * {{getEndLineNumber()}} > * {{getEditorMessage()}}: This should be used instead of {{getMessage()}} (though apparently the output of `getMessage()` is identical, it's actually because FM detects that it was called from JBoss Tools and then creates a message customized for that). -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20387) Use column number when navigating to errors, and more

by Daniel Dekany (JIRA)

Daniel Dekany created JBIDE-20387: ------------------------------------- Summary: Use column number when navigating to errors, and more Key: JBIDE-20387 URL: https://issues.jboss.org/browse/JBIDE-20387 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: freemarker Reporter: Daniel Dekany The plugin doesn't utilize some tooling-centric information available in {{freemarker.core.ParseException}}, most importantly, the column number that Eclipse could utilize to jump at the error start inside the line. The information that's not used is (see {{plugins/org.jboss.ide.eclipse.freemarker/src/org/jboss/ide/eclipse/freemarker/editor/Editor.java}}): * {{getColumnNumber()}}, {{getEndColumnNumber()}} * {{getEndLineNumber()}} * {{getEditorMessage()}}: This should be used instead of `getMessage()` (though apparently the output of `getMessage()` is identical, it's actually because FM detects that it was called from JBoss Tools and then creates a message customized for that)). -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 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 2015