September 2014 - jbosstools-issues

[JBoss JIRA] (JBIDE-18134) Port forwarding: Free ports should be used from range 49152–65535

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18134?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-18134: ------------------------------------- Issue Type: Enhancement (was: Feature Request) > Port forwarding: Free ports should be used from range 49152–65535 > ----------------------------------------------------------------- > > Key: JBIDE-18134 > URL: https://issues.jboss.org/browse/JBIDE-18134 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.2.0.CR1 > Reporter: Marián Labuda > Priority: Minor > Labels: port_forwarding_wizard > Fix For: 4.3.x > > > Currently port forwarding use as free ports any port received via java client which is calling some RHC function to get a free port. There are many ports in those so-called free ports which are under range 49152–65535. This range is declared by IANA for dynamic, private... let's call them free ports. > Problem could occur in case of getting a port number lesser than 49152 which is currently not in use, but it is registered and user could start a service using this port number. Then there could be a conflict. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18134) Port forwarding: Free ports should be used from range 49152–65535

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18134?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-18134: ------------------------------------- Labels: port_forwarding_wizard (was: ) > Port forwarding: Free ports should be used from range 49152–65535 > ----------------------------------------------------------------- > > Key: JBIDE-18134 > URL: https://issues.jboss.org/browse/JBIDE-18134 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.2.0.CR1 > Reporter: Marián Labuda > Priority: Minor > Labels: port_forwarding_wizard > Fix For: 4.3.x > > > Currently port forwarding use as free ports any port received via java client which is calling some RHC function to get a free port. There are many ports in those so-called free ports which are under range 49152–65535. This range is declared by IANA for dynamic, private... let's call them free ports. > Problem could occur in case of getting a port number lesser than 49152 which is currently not in use, but it is registered and user could start a service using this port number. Then there could be a conflict. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18134) Port forwarding: Free ports should be used from range 49152–65535

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18134?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-18134: ------------------------------------- Estimated Difficulty: Low > Port forwarding: Free ports should be used from range 49152–65535 > ----------------------------------------------------------------- > > Key: JBIDE-18134 > URL: https://issues.jboss.org/browse/JBIDE-18134 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.2.0.CR1 > Reporter: Marián Labuda > Priority: Minor > Labels: port_forwarding_wizard > Fix For: 4.3.x > > > Currently port forwarding use as free ports any port received via java client which is calling some RHC function to get a free port. There are many ports in those so-called free ports which are under range 49152–65535. This range is declared by IANA for dynamic, private... let's call them free ports. > Problem could occur in case of getting a port number lesser than 49152 which is currently not in use, but it is registered and user could start a service using this port number. Then there could be a conflict. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18124) Server adapter: Creating a new server adapter does not use name that was provided

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18124?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-18124: ------------------------------------- Summary: Server adapter: Creating a new server adapter does not use name that was provided (was: Server adapter: Creating a new server adapter does not use filled name) > Server adapter: Creating a new server adapter does not use name that was provided > --------------------------------------------------------------------------------- > > Key: JBIDE-18124 > URL: https://issues.jboss.org/browse/JBIDE-18124 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.CR1 > Reporter: Marián Labuda > Priority: Minor > Fix For: 4.3.x > > > While creating a new server adapter there is a field in New Server shell for Server's host name and Server name. At least the field Server name should be taken into consideration while creating a server adapter and created server adapter should have be named "filledName at OpenShift [Started]" instead of "applicationName at OpenShift [Started]". -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14818) Server Adapter Editor: there's no "deployments" page for OpenShift that would allow me to rename a module

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14818?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-14818: ------------------------------------- Sorry, no, it was not on my radar as it was targeted to 4.2.x as of 31/Mar/14, so it was not in my priority queue. > Server Adapter Editor: there's no "deployments" page for OpenShift that would allow me to rename a module > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-14818 > URL: https://issues.jboss.org/browse/JBIDE-14818 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift, server > Affects Versions: 4.1.0.Beta2 > Reporter: Andre Dietisheim > Assignee: Rob Stryker > Priority: Critical > Labels: server_adapter_editor > Fix For: 4.2.1.Final > > > In JDF-172 a users tries to deploy an application to OpenShift. He'll use the binary deployment. In order to have the app showing up at */* he'll want to rename the war to *ROOT.war*. If he does this in the *Project Explorer* things are fine as long as the original project is not changed. As soon as there's a change the adapter will "refresh" the war and re-create it with the project name, it will not update the ROOT.war. We therefore need a deployments page where the user can rename a deployment. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18036) Decouple FTL target language syntax coloring

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18036?page=com.atlassian.jira.plugi... ] Denis Golovin commented on JBIDE-18036: --------------------------------------- How do "various syntax highlight issues" look like? > Decouple FTL target language syntax coloring > -------------------------------------------- > > Key: JBIDE-18036 > URL: https://issues.jboss.org/browse/JBIDE-18036 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: freemarker > Reporter: Peter Palaga > Assignee: Peter Palaga > Fix For: 4.2.0.CR2 > > Attachments: coloring-issues.png > > > This issue covers the requirement formulated in point (1) of my earlier comment in [JBIDE-11287|https://issues.jboss.org/browse/JBIDE-11287?focusedCommentId=...]. > The present Freemarker plugin has a hard-coded XML/HTML syntax coloring. Although XML/HTML may well be the most common target language of an FTL template, it is clearly not the only possible target language. One can target virtually any language or even plaintext, where {{<}} and {{<!--}} may have completely different meanings or no meanigs at all. Hardcoding XML highlighting for every file opened by the FTL editor is thus simply incorrect. > Let's define the present task as follows: > (1) Decouple the syntax coloring of the target language of a FTL template by introducing an interface (call it {{TargetLanguageSupport}}) that will provide the general functionality needed for coloring of target languages. > (2) At least two implementations of {{TargetLanguageSupport}} should be added: > (2.1) XML/HTML and > (2.2) plain text. > (3) Some kind of target-language detection should be added, e.g. based on file extensions, making XML/HTML syntax coloring active for files ending with {{\*.xml.ftl}}, {{\*.xhtml.ftl}}, {{\*.html.ftl}} and {{\*.htm.ftl}}. > (3.1) There should be a workspace-wide preference that will say for which file extensions will e.g. XML/HTML syntax coloring be active. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-11367) Application wizard should close and run maven import in background once the application was created

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11367?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-11367: ------------------------------------- Estimated Difficulty: Low (was: High) > Application wizard should close and run maven import in background once the application was created > --------------------------------------------------------------------------------------------------- > > Key: JBIDE-11367 > URL: https://issues.jboss.org/browse/JBIDE-11367 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 3.3.0.Beta1 > Reporter: Xavier Coulon > Labels: application_wizard > Fix For: 4.2.1.Final, 4.3.0.Alpha1 > > > After 3.3.0.Beta1, most of the operations are run at the end of the wizard (ie, in the performFinish() method) in background jobs. The UI is not blocked but the wizard wont close before the jobs are finished. Since creating the app, adding cartridges, cloning the repo and importing the project within it is a lot of work the user is blocked and condemned to see and watch it happen. > We should free the user to do other tasks by allowing him to close the wizard and get notified once the process finished. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-11367) Application wizard should close and run maven import in background once the application was created

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11367?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-11367: ------------------------------------- Summary: Application wizard should close and run maven import in background once the application was created (was: Application wizard should close when importing maven project to avoid blocking too long) > Application wizard should close and run maven import in background once the application was created > --------------------------------------------------------------------------------------------------- > > Key: JBIDE-11367 > URL: https://issues.jboss.org/browse/JBIDE-11367 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 3.3.0.Beta1 > Reporter: Xavier Coulon > Labels: application_wizard > Fix For: 4.2.1.Final, 4.3.0.Alpha1 > > > After 3.3.0.Beta1, most of the operations are run at the end of the wizard (ie, in the performFinish() method) in background jobs. The UI is not blocked but the wizard wont close before the jobs are finished. Since creating the app, adding cartridges, cloning the repo and importing the project within it is a lot of work the user is blocked and condemned to see and watch it happen. > We should free the user to do other tasks by allowing him to close the wizard and get notified once the process finished. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14818) Server Adapter Editor: there's no "deployments" page for OpenShift that would allow me to rename a module

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14818?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-14818: ------------------------------------------ [~rob.stryker] any update on this, did you have the time to look into this? > Server Adapter Editor: there's no "deployments" page for OpenShift that would allow me to rename a module > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-14818 > URL: https://issues.jboss.org/browse/JBIDE-14818 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift, server > Affects Versions: 4.1.0.Beta2 > Reporter: Andre Dietisheim > Assignee: Rob Stryker > Priority: Critical > Labels: server_adapter_editor > Fix For: 4.2.1.Final > > > In JDF-172 a users tries to deploy an application to OpenShift. He'll use the binary deployment. In order to have the app showing up at */* he'll want to rename the war to *ROOT.war*. If he does this in the *Project Explorer* things are fine as long as the original project is not changed. As soon as there's a change the adapter will "refresh" the war and re-create it with the project name, it will not update the ROOT.war. We therefore need a deployments page where the user can rename a deployment. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-8526) Freemarker content assist doesn't work when inside a tag or tag attribute

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-8526?page=com.atlassian.jira.plugin... ] Denis Golovin commented on JBIDE-8526: -------------------------------------- Are there any exceptions in eclipse log? > Freemarker content assist doesn't work when inside a tag or tag attribute > ------------------------------------------------------------------------- > > Key: JBIDE-8526 > URL: https://issues.jboss.org/browse/JBIDE-8526 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: freemarker > Affects Versions: 3.3.x > Environment: Windows XP, > Reporter: Ehrann Mehdan > Assignee: Denis Golovin > Fix For: 4.2.0.CR2 > > > In Freemarker 1.1.0.v20110303-1225-H55-Alpha1 > Eclipse platform version: 3.6.2.r362_v20110210-9gF78Gs1FrIGnHDHWkEcopoN8AmxeZflGDGKQi > Build id: M20110210-1200 > This code will not trigger content assist when pressing ctrl+space with a context named data that has property "someValue" > <tag attribute="${data.someValue}">... > This code will (removed opening tag bracket) > tag attribute="${data.someValue}">... -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 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 September 2014