February 2014 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-1557) Version must be explicitly set when the test is inside the addon project

by George Gastaldi (JIRA)

George Gastaldi created FORGE-1557: -------------------------------------- Summary: Version must be explicitly set when the test is inside the addon project Key: FORGE-1557 URL: https://issues.jboss.org/browse/FORGE-1557 Project: Forge Issue Type: Bug Components: Furnace (Container) Affects Versions: 2.0.0.Final Reporter: George Gastaldi Assignee: George Gastaldi Fix For: 2.0.1.Final The @AddonDependency version must be set when the project is a single addon, otherwise an error is thrown saying that the version cannot be resolved. -- 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

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1557) Version must be explicitly set when the test is inside the addon project

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1557?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1557. ---------------------------------- Resolution: Done > Version must be explicitly set when the test is inside the addon project > ------------------------------------------------------------------------ > > Key: FORGE-1557 > URL: https://issues.jboss.org/browse/FORGE-1557 > Project: Forge > Issue Type: Bug > Components: Furnace (Container) > Affects Versions: 2.0.0.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 2.0.1.Final > > > The @AddonDependency version must be set when the project is a single addon, otherwise an error is thrown saying that the version cannot be resolved. -- 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

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1556) Shell history, aliases and exported files should be placed in ~/.forge

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-1556?page=com.atlassian.jira.plugin... ] Vineet Reynolds commented on FORGE-1556: ---------------------------------------- This probably depends on AESH-206 since the SettingsBuilder API does not seem to allow for setting the export file path unless the export file already exists. > Shell history, aliases and exported files should be placed in ~/.forge > ---------------------------------------------------------------------- > > Key: FORGE-1556 > URL: https://issues.jboss.org/browse/FORGE-1556 > Project: Forge > Issue Type: Enhancement > Components: UI - Shell > Affects Versions: 2.0.0.Final > Reporter: George Gastaldi > Assignee: Vineet Reynolds > Fix For: 2.x Future > > > The following files are created in ~/ when the shell is executed: > - .aesh_aliases > - .aesh_export > - .aesh_history > They should be placed in ~/.forge/ and renamed respectively to > - aliases > - export > - history -- 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

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1327) Upgrade to Roaster (formerly known as java-parser 2.0)

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1327?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-1327: ----------------------------------- Summary: Upgrade to Roaster (formerly known as java-parser 2.0) (was: Upgrade to Java-parser 2.0.0.Alpha1) > Upgrade to Roaster (formerly known as java-parser 2.0) > ------------------------------------------------------ > > Key: FORGE-1327 > URL: https://issues.jboss.org/browse/FORGE-1327 > Project: Forge > Issue Type: Component Upgrade > Components: Parsers / File Manipulation > Affects Versions: 2.0.0.Beta3 > Reporter: George Gastaldi > Fix For: 2.1.0.Final > > -- 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

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1556) Shell history, aliases and exported files should be placed in ~/.forge

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-1556?page=com.atlassian.jira.plugin... ] Vineet Reynolds commented on FORGE-1556: ---------------------------------------- We won't use the Forge 1 filenames since we'd like to avoid conflicts when a Forge 1 process is executing at the same time (either in JBDS or otherwise). > Shell history, aliases and exported files should be placed in ~/.forge > ---------------------------------------------------------------------- > > Key: FORGE-1556 > URL: https://issues.jboss.org/browse/FORGE-1556 > Project: Forge > Issue Type: Enhancement > Components: UI - Shell > Affects Versions: 2.0.0.Final > Reporter: George Gastaldi > Assignee: Vineet Reynolds > Fix For: 2.x Future > > > The following files are created in ~/ when the shell is executed: > - .aesh_aliases > - .aesh_export > - .aesh_history > They should be placed in ~/.forge/ and renamed respectively to > - forge_aliases > - forge_export > - forge_history -- 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

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1556) Shell history, aliases and exported files should be placed in ~/.forge

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-1556?page=com.atlassian.jira.plugin... ] Vineet Reynolds updated FORGE-1556: ----------------------------------- Description: The following files are created in ~/ when the shell is executed: - .aesh_aliases - .aesh_export - .aesh_history They should be placed in ~/.forge/ and renamed respectively to - aliases - export - history was: The following files are created in ~/ when the shell is executed: - .aesh_aliases - .aesh_export - .aesh_history They should be placed in ~/.forge/ and renamed respectively to - forge_aliases - forge_export - forge_history > Shell history, aliases and exported files should be placed in ~/.forge > ---------------------------------------------------------------------- > > Key: FORGE-1556 > URL: https://issues.jboss.org/browse/FORGE-1556 > Project: Forge > Issue Type: Enhancement > Components: UI - Shell > Affects Versions: 2.0.0.Final > Reporter: George Gastaldi > Assignee: Vineet Reynolds > Fix For: 2.x Future > > > The following files are created in ~/ when the shell is executed: > - .aesh_aliases > - .aesh_export > - .aesh_history > They should be placed in ~/.forge/ and renamed respectively to > - aliases > - export > - history -- 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

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1556) Shell history, aliases and exported files should be placed in ~/.forge

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-1556?page=com.atlassian.jira.plugin... ] Vineet Reynolds updated FORGE-1556: ----------------------------------- Description: The following files are created in ~/ when the shell is executed: - .aesh_aliases - .aesh_export - .aesh_history They should be placed in ~/.forge/ and renamed respectively to - forge_aliases - forge_export - forge_history was: The following files are created in ~/ when the shell is executed: - .aesh_aliases - .aesh_export - .aesh_history They should be placed in ~/.forge/ and renamed respectively to - .forge_aliases - .forge_export - .forge_history > Shell history, aliases and exported files should be placed in ~/.forge > ---------------------------------------------------------------------- > > Key: FORGE-1556 > URL: https://issues.jboss.org/browse/FORGE-1556 > Project: Forge > Issue Type: Enhancement > Components: UI - Shell > Affects Versions: 2.0.0.Final > Reporter: George Gastaldi > Assignee: Vineet Reynolds > Fix For: 2.x Future > > > The following files are created in ~/ when the shell is executed: > - .aesh_aliases > - .aesh_export > - .aesh_history > They should be placed in ~/.forge/ and renamed respectively to > - forge_aliases > - forge_export > - forge_history -- 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

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1556) Shell history, aliases and exported files should be placed in ~/.forge

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-1556?page=com.atlassian.jira.plugin... ] Vineet Reynolds reassigned FORGE-1556: -------------------------------------- Assignee: Vineet Reynolds > Shell history, aliases and exported files should be placed in ~/.forge > ---------------------------------------------------------------------- > > Key: FORGE-1556 > URL: https://issues.jboss.org/browse/FORGE-1556 > Project: Forge > Issue Type: Enhancement > Components: UI - Shell > Affects Versions: 2.0.0.Final > Reporter: George Gastaldi > Assignee: Vineet Reynolds > Fix For: 2.x Future > > > The following files are created in ~/ when the shell is executed: > - .aesh_aliases > - .aesh_export > - .aesh_history > They should be placed in ~/.forge/ and renamed respectively to > - .forge_aliases > - .forge_export > - .forge_history -- 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

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1556) Shell history, aliases and exported files should be placed in ~/.forge

by George Gastaldi (JIRA)

George Gastaldi created FORGE-1556: -------------------------------------- Summary: Shell history, aliases and exported files should be placed in ~/.forge Key: FORGE-1556 URL: https://issues.jboss.org/browse/FORGE-1556 Project: Forge Issue Type: Enhancement Components: UI - Shell Affects Versions: 2.0.0.Final Reporter: George Gastaldi Fix For: 2.x Future The following files are created in ~/ when the shell is executed: - .aesh_aliases - .aesh_export - .aesh_history They should be placed in ~/.forge/ and renamed respectively to - .forge_aliases - .forge_export - .forge_history -- 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

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1555) Autocomplete should display options without requiring a user to type in a double hyphen --

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-1555?page=com.atlassian.jira.plugin... ] Vineet Reynolds updated FORGE-1555: ----------------------------------- Description: When I key in {noformat} [Order.java]$ jpa-new-field --named description <TAB> {noformat}, I do not get to see the options available for the command, until I key in a double-hyphen, like so: {noformat} [Order.java]$ jpa-new-field --named description -- --targetEntity --type --length --lob {noformat} I think a tying a TAB after a space should display the options for a command. Note that this issue is limited in scope (and is different from FORGE-1554) to ensuring that parameter names are displayed as autocomplete options without requiring a {{--}} to be keyed in by the user. was: When I key in {noformat} [Order.java]$ jpa-new-field --named description <TAB> {noformat}, I do not get to see the options available for the command, until I key in a double-hyphen, like so: {noformat} [Order.java]$ jpa-new-field --named description -- --targetEntity --type --length --lob {noformat} I think a tying a TAB after a space should display the options for a command. > Autocomplete should display options without requiring a user to type in a double hyphen -- > ------------------------------------------------------------------------------------------ > > Key: FORGE-1555 > URL: https://issues.jboss.org/browse/FORGE-1555 > Project: Forge > Issue Type: Feature Request > Components: UI - Shell > Affects Versions: 2.0.0.Final > Reporter: Vineet Reynolds > Fix For: 2.x Future > > > When I key in > {noformat} > [Order.java]$ jpa-new-field --named description <TAB> > {noformat}, I do not get to see the options available for the command, until I key in a double-hyphen, like so: > {noformat} > [Order.java]$ jpa-new-field --named description -- > --targetEntity --type --length --lob > {noformat} > I think a tying a TAB after a space should display the options for a command. > Note that this issue is limited in scope (and is different from FORGE-1554) to ensuring that parameter names are displayed as autocomplete options without requiring a {{--}} to be keyed in by the user. -- 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

10 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues February 2014