[JBoss JIRA] (FORGE-552) Escaping of selected characters doesn't work
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-552?page=com.atlassian.jira.plugin.... ]
George Gastaldi commented on FORGE-552:
---------------------------------------
This is an Aesh bug, see AESH-333
> Escaping of selected characters doesn't work
> --------------------------------------------
>
> Key: FORGE-552
> URL: https://issues.jboss.org/browse/FORGE-552
> Project: Forge
> Issue Type: Bug
> Components: UI - Shell
> Affects Versions: 1.0.2.Final, 2.19.2.Final
> Environment: Ubuntu 10.04 i686
> Reporter: Jevgeni Zelenkov
> Assignee: George Gastaldi
> Priority: Critical
> Fix For: 2.0.0.Alpha14, 2.20.0.Final
>
>
> This is related to the FORGE-43 issue.
> The following characters in file names should be escaped by the forge completion:
> \* ? = ' " { } \ $ ! & ; ( ) < > |
> also: TAB-char (yes, I know it is stupid, but possible)
> First two (*, ?) are used internally as wildcard chars, so should be allowed to be used escaped as well as unescaped.
> = char doesn't need to be escaped neither on linux nor on windows but somehow forge fails to work with files containing = (at least on my ubuntu).
> Windows has a slightly different set of chars to be escaped (from wikipedia, not actually tested):
> ' " = & | ( ) < > ^
> This issue is added for completeness.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 3 months
[JBoss JIRA] (FORGE-552) Escaping of selected characters doesn't work
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-552?page=com.atlassian.jira.plugin.... ]
George Gastaldi updated FORGE-552:
----------------------------------
Description:
This is related to the FORGE-43 issue.
The following characters in file names should be escaped by the forge completion:
\* ? = ' " { } \ $ ! & ; ( ) < > |
also: TAB-char (yes, I know it is stupid, but possible)
First two (*, ?) are used internally as wildcard chars, so should be allowed to be used escaped as well as unescaped.
= char doesn't need to be escaped neither on linux nor on windows but somehow forge fails to work with files containing = (at least on my ubuntu).
Windows has a slightly different set of chars to be escaped (from wikipedia, not actually tested):
' " = & | ( ) < > ^
This issue is added for completeness.
was:
This is related to the https://issues.jboss.org/browse/FORGE-43 issue.
The following characters in file names should be escaped by the forge completion:
\* ? = ' " { } \ $ ! & ; ( ) < > |
also: TAB-char (yes, I know it is stupid, but possible)
First two (*, ?) are used internally as wildcard chars, so should be allowed to be used escaped as well as unescaped.
= char doesn't need to be escaped neither on linux nor on windows but somehow forge fails to work with files containing = (at least on my ubuntu).
Windows has a slightly different set of chars to be escaped (from wikipedia, not actually tested):
' " = & | ( ) < > ^
This issue is added for completeness.
> Escaping of selected characters doesn't work
> --------------------------------------------
>
> Key: FORGE-552
> URL: https://issues.jboss.org/browse/FORGE-552
> Project: Forge
> Issue Type: Bug
> Components: UI - Shell
> Affects Versions: 1.0.2.Final, 2.19.2.Final
> Environment: Ubuntu 10.04 i686
> Reporter: Jevgeni Zelenkov
> Assignee: George Gastaldi
> Priority: Critical
> Fix For: 2.0.0.Alpha14, 2.20.0.Final
>
>
> This is related to the FORGE-43 issue.
> The following characters in file names should be escaped by the forge completion:
> \* ? = ' " { } \ $ ! & ; ( ) < > |
> also: TAB-char (yes, I know it is stupid, but possible)
> First two (*, ?) are used internally as wildcard chars, so should be allowed to be used escaped as well as unescaped.
> = char doesn't need to be escaped neither on linux nor on windows but somehow forge fails to work with files containing = (at least on my ubuntu).
> Windows has a slightly different set of chars to be escaped (from wikipedia, not actually tested):
> ' " = & | ( ) < > ^
> This issue is added for completeness.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 3 months
[JBoss JIRA] (FORGE-2493) UISelectOne<String> accepts any input as a value
by George Gastaldi (JIRA)
George Gastaldi created FORGE-2493:
--------------------------------------
Summary: UISelectOne<String> accepts any input as a value
Key: FORGE-2493
URL: https://issues.jboss.org/browse/FORGE-2493
Project: Forge
Issue Type: Bug
Components: UI - API
Affects Versions: 2.19.2.Final
Reporter: George Gastaldi
Assignee: George Gastaldi
Fix For: 2.20.0.Final
{{UISelectOne<String>}} inputs accepts any input as a value. It should accept only those defined in their value choices.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 3 months
[JBoss JIRA] (FORGE-2492) forge hangs on AbstractProjectCommand.getSelectedProject() when used inside fabric8-forge (the REST service)
by James Strachan (JIRA)
James Strachan created FORGE-2492:
-------------------------------------
Summary: forge hangs on AbstractProjectCommand.getSelectedProject() when used inside fabric8-forge (the REST service)
Key: FORGE-2492
URL: https://issues.jboss.org/browse/FORGE-2492
Project: Forge
Issue Type: Feature Request
Affects Versions: 2.19.2.Final, 2.17.0.Final
Environment: using the fabric8-forge docker image inside OpenShift
Reporter: James Strachan
Here's a stack trace:
https://gist.github.com/jstrachan/741d65b7dd87ca0e701e
when using Forge from the hawtio console, the JVM seems to hang for 1-2 minutes now inside the call to AbstractProjectCommand.getSelectedProject(). Whats odd is I can create an archetype and invoke this code path on startup just fine - but then thats in a different thread to the one using Forge from inside the JAXRS service; so am wondering if its related to which thread is being used?
Seems to ultimately be a wagon / aether issue; taking too long to download things.
Wonder is there any way to configure the maven addon in forge to register a Wagon listener maybe? No idea whats causing the pause
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 3 months
[JBoss JIRA] (FORGE-552) Escaping of selected characters doesn't work
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-552?page=com.atlassian.jira.plugin.... ]
Work on FORGE-552 started by George Gastaldi.
---------------------------------------------
> Escaping of selected characters doesn't work
> --------------------------------------------
>
> Key: FORGE-552
> URL: https://issues.jboss.org/browse/FORGE-552
> Project: Forge
> Issue Type: Bug
> Components: UI - Shell
> Affects Versions: 1.0.2.Final, 2.19.2.Final
> Environment: Ubuntu 10.04 i686
> Reporter: Jevgeni Zelenkov
> Assignee: George Gastaldi
> Priority: Critical
> Fix For: 2.0.0.Alpha14, 2.20.0.Final
>
>
> This is related to the https://issues.jboss.org/browse/FORGE-43 issue.
> The following characters in file names should be escaped by the forge completion:
> \* ? = ' " { } \ $ ! & ; ( ) < > |
> also: TAB-char (yes, I know it is stupid, but possible)
> First two (*, ?) are used internally as wildcard chars, so should be allowed to be used escaped as well as unescaped.
> = char doesn't need to be escaped neither on linux nor on windows but somehow forge fails to work with files containing = (at least on my ubuntu).
> Windows has a slightly different set of chars to be escaped (from wikipedia, not actually tested):
> ' " = & | ( ) < > ^
> This issue is added for completeness.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 3 months
[JBoss JIRA] (FORGE-552) Escaping of selected characters doesn't work
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-552?page=com.atlassian.jira.plugin.... ]
George Gastaldi updated FORGE-552:
----------------------------------
Component/s: UI - Shell
(was: Forge Build)
Fix Version/s: 2.20.0.Final
(was: 2.x Future)
Priority: Critical (was: Major)
Affects Version/s: 2.19.2.Final
Hi Claus,
I raised the priority in this issue and will try to fix it in the next release.
Thanks
> Escaping of selected characters doesn't work
> --------------------------------------------
>
> Key: FORGE-552
> URL: https://issues.jboss.org/browse/FORGE-552
> Project: Forge
> Issue Type: Bug
> Components: UI - Shell
> Affects Versions: 1.0.2.Final, 2.19.2.Final
> Environment: Ubuntu 10.04 i686
> Reporter: Jevgeni Zelenkov
> Priority: Critical
> Fix For: 2.0.0.Alpha14, 2.20.0.Final
>
>
> This is related to the https://issues.jboss.org/browse/FORGE-43 issue.
> The following characters in file names should be escaped by the forge completion:
> \* ? = ' " { } \ $ ! & ; ( ) < > |
> also: TAB-char (yes, I know it is stupid, but possible)
> First two (*, ?) are used internally as wildcard chars, so should be allowed to be used escaped as well as unescaped.
> = char doesn't need to be escaped neither on linux nor on windows but somehow forge fails to work with files containing = (at least on my ubuntu).
> Windows has a slightly different set of chars to be escaped (from wikipedia, not actually tested):
> ' " = & | ( ) < > ^
> This issue is added for completeness.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 3 months
[JBoss JIRA] (FORGE-552) Escaping of selected characters doesn't work
by Claus Ibsen (JIRA)
[ https://issues.jboss.org/browse/FORGE-552?page=com.atlassian.jira.plugin.... ]
Claus Ibsen commented on FORGE-552:
-----------------------------------
[~gastaldi] this is needed for the fabric8 project for the Camel add-on we work on.
Its this ticket
https://github.com/fabric8io/fabric8/issues/4548#issuecomment-144291583
> Escaping of selected characters doesn't work
> --------------------------------------------
>
> Key: FORGE-552
> URL: https://issues.jboss.org/browse/FORGE-552
> Project: Forge
> Issue Type: Bug
> Components: Forge Build
> Affects Versions: 1.0.2.Final
> Environment: Ubuntu 10.04 i686
> Reporter: Jevgeni Zelenkov
> Fix For: 2.0.0.Alpha14, 2.x Future
>
>
> This is related to the https://issues.jboss.org/browse/FORGE-43 issue.
> The following characters in file names should be escaped by the forge completion:
> \* ? = ' " { } \ $ ! & ; ( ) < > |
> also: TAB-char (yes, I know it is stupid, but possible)
> First two (*, ?) are used internally as wildcard chars, so should be allowed to be used escaped as well as unescaped.
> = char doesn't need to be escaped neither on linux nor on windows but somehow forge fails to work with files containing = (at least on my ubuntu).
> Windows has a slightly different set of chars to be escaped (from wikipedia, not actually tested):
> ' " = & | ( ) < > ^
> This issue is added for completeness.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 3 months