March 2014 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-1648) InputComponent with magic name 'arguments' does not work if UISelectOne is used

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/FORGE-1648?page=com.atlassian.jira.plugin... ] Aslak Knutsen updated FORGE-1648: --------------------------------- Fix Version/s: 2.x Future > InputComponent with magic name 'arguments' does not work if UISelectOne is used > ------------------------------------------------------------------------------- > > Key: FORGE-1648 > URL: https://issues.jboss.org/browse/FORGE-1648 > Project: Forge > Issue Type: Bug > Components: UI - API > Affects Versions: 2.1.1.Final > Reporter: Aslak Knutsen > Fix For: 2.x Future > > > {code} > @Inject > @WithAttributes(label = "Arguments", required = true) > private UISelectOne<String> arguments; > {code} > Expected to be able to get 'value choice' via "command <tab>", but 'arguments' is not recognize as a non switch argument. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (FORGE-1648) InputComponent with magic name 'arguments' does not work if UISelectOne is used

by Aslak Knutsen (JIRA)

Aslak Knutsen created FORGE-1648: ------------------------------------ Summary: InputComponent with magic name 'arguments' does not work if UISelectOne is used Key: FORGE-1648 URL: https://issues.jboss.org/browse/FORGE-1648 Project: Forge Issue Type: Bug Components: UI - API Affects Versions: 2.1.1.Final Reporter: Aslak Knutsen {code} @Inject @WithAttributes(label = "Arguments", required = true) private UISelectOne<String> arguments; {code} Expected to be able to get 'value choice' via "command <tab>", but 'arguments' is not recognize as a non switch argument. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (FORGE-1645) JavaResource resolve to wrong path after CD

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1645?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-1645: ----------------------------------- Fix Version/s: 2.x Future > JavaResource resolve to wrong path after CD > ------------------------------------------- > > Key: FORGE-1645 > URL: https://issues.jboss.org/browse/FORGE-1645 > Project: Forge > Issue Type: Bug > Components: Parsers / File Manipulation > Affects Versions: 2.1.1.Final > Environment: Linux Fedora 20, JDK 1.7 > Reporter: Aslak Knutsen > Fix For: 2.x Future > > > With the following code > {code} > @Inject > @WithAttributes(shortName = 's', label = "source", required = true, type = InputType.JAVA_CLASS_PICKER) > private UIInput<JavaResource> source; > {code} > Assume the following directory structure: > x/y/src/main/java/x.java > * Start forge in folder X. > * cd to some sub folder Y > * trigger the 'source' field > ** command --source src/main/java/x.java > The JavaResource fail to resolve the underlying file as it's pointing to: > X/src/main/java/x.java > It seems it's missing the updated 'current dir' and only resolve from 'original working dir' -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (FORGE-1647) Add support API for handling console color

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1647?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-1647: ----------------------------------- Fix Version/s: 2.x Future > Add support API for handling console color > ------------------------------------------ > > Key: FORGE-1647 > URL: https://issues.jboss.org/browse/FORGE-1647 > Project: Forge > Issue Type: Feature Request > Components: UI - Shell > Affects Versions: 2.1.1.Final > Reporter: Aslak Knutsen > Fix For: 2.x Future > > > Forge should provide some helpful coloring API over TerminalColor used by Æsh. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (FORGE-1646) Add convenience API for syntax coloring in shell

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1646?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-1646: ----------------------------------- Fix Version/s: 2.x Future > Add convenience API for syntax coloring in shell > ------------------------------------------------- > > Key: FORGE-1646 > URL: https://issues.jboss.org/browse/FORGE-1646 > Project: Forge > Issue Type: Feature Request > Components: UI - Shell > Affects Versions: 2.1.1.Final > Reporter: Aslak Knutsen > Fix For: 2.x Future > > > It would be use full to be able to color code source code printed to the console via some common api. > {code} > highlight(source, Type.JAVA) > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (FORGE-1647) Add support API for handling console color

by Aslak Knutsen (JIRA)

Aslak Knutsen created FORGE-1647: ------------------------------------ Summary: Add support API for handling console color Key: FORGE-1647 URL: https://issues.jboss.org/browse/FORGE-1647 Project: Forge Issue Type: Feature Request Components: UI - Shell Affects Versions: 2.1.1.Final Reporter: Aslak Knutsen Forge should provide some helpful coloring API over TerminalColor used by Æsh. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (FORGE-1647) Add support API for handling console color

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/FORGE-1647?page=com.atlassian.jira.plugin... ] Aslak Knutsen commented on FORGE-1647: -------------------------------------- Consider porting the API from Forge 1 > Add support API for handling console color > ------------------------------------------ > > Key: FORGE-1647 > URL: https://issues.jboss.org/browse/FORGE-1647 > Project: Forge > Issue Type: Feature Request > Components: UI - Shell > Affects Versions: 2.1.1.Final > Reporter: Aslak Knutsen > > Forge should provide some helpful coloring API over TerminalColor used by Æsh. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (FORGE-1646) Add convenience API for syntax coloring in shell

by Aslak Knutsen (JIRA)

Aslak Knutsen created FORGE-1646: ------------------------------------ Summary: Add convenience API for syntax coloring in shell Key: FORGE-1646 URL: https://issues.jboss.org/browse/FORGE-1646 Project: Forge Issue Type: Feature Request Components: UI - Shell Affects Versions: 2.1.1.Final Reporter: Aslak Knutsen It would be use full to be able to color code source code printed to the console via some common api. {code} highlight(source, Type.JAVA) {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (FORGE-1645) JavaResource resolve to wrong path after CD

by Aslak Knutsen (JIRA)

Aslak Knutsen created FORGE-1645: ------------------------------------ Summary: JavaResource resolve to wrong path after CD Key: FORGE-1645 URL: https://issues.jboss.org/browse/FORGE-1645 Project: Forge Issue Type: Bug Components: Parsers / File Manipulation Affects Versions: 2.1.1.Final Environment: Linux Fedora 20, JDK 1.7 Reporter: Aslak Knutsen With the following code {code} @Inject @WithAttributes(shortName = 's', label = "source", required = true, type = InputType.JAVA_CLASS_PICKER) private UIInput<JavaResource> source; {code} Assume the following directory structure: x/y/src/main/java/x.java * Start forge in folder X. * cd to some sub folder Y * trigger the 'source' field ** command --source src/main/java/x.java The JavaResource fail to resolve the underlying file as it's pointing to: X/src/main/java/x.java It seems it's missing the updated 'current dir' and only resolve from 'original working dir' -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (FORGE-1644) Addons should have a storage area

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1644?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-1644: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/forge/furnace/pull/8 > Addons should have a storage area > --------------------------------- > > Key: FORGE-1644 > URL: https://issues.jboss.org/browse/FORGE-1644 > Project: Forge > Issue Type: Feature Request > Components: Furnace (Container) > Affects Versions: 2.1.1.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 2.x Future > > > If would be nice if each addon had a storage area (not temporary) to store files relevant to the addon execution. This area could live under {{USER_HOME/.forge/store/addon_name}}. > Here is an example code on how to access it: > {code} > @Inject Addon addon; > File storageArea = addon.getStorageDirectory(); > {code} > Examples: > - The current config.xml file could be in the storage directory of the configuration addon > - The shell specific files (export, alias, history) could be in the storage directory of the shell addon -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues March 2014