January 2014 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-1418) Once a man page has been displayed, no other man pages may be displayed

by Lincoln Baxter III (JIRA)

Lincoln Baxter III created FORGE-1418: ----------------------------------------- Summary: Once a man page has been displayed, no other man pages may be displayed Key: FORGE-1418 URL: https://issues.jboss.org/browse/FORGE-1418 Project: Forge Issue Type: Feature Request Components: UI - Shell Reporter: Lincoln Baxter III Fix For: 2.x Future Once a man page has been displayed, even if a separate command manual page is requested, the original man page from the first command will be displayed. Steps to reproduce: {code} man ls man faces-setup {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, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1418) Once a man page has been displayed, no other man pages may be displayed

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1418?page=com.atlassian.jira.plugin... ] Lincoln Baxter III updated FORGE-1418: -------------------------------------- Affects Version/s: 2.0.0.Beta4 > Once a man page has been displayed, no other man pages may be displayed > ----------------------------------------------------------------------- > > Key: FORGE-1418 > URL: https://issues.jboss.org/browse/FORGE-1418 > Project: Forge > Issue Type: Feature Request > Components: UI - Shell > Affects Versions: 2.0.0.Beta4 > Reporter: Lincoln Baxter III > Fix For: 2.x Future > > > Once a man page has been displayed, even if a separate command manual page is requested, the original man page from the first command will be displayed. > Steps to reproduce: > {code} > man ls > man faces-setup > {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, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1417) Piping a forge command to another command succeeds then fails

by Lincoln Baxter III (JIRA)

Lincoln Baxter III created FORGE-1417: ----------------------------------------- Summary: Piping a forge command to another command succeeds then fails Key: FORGE-1417 URL: https://issues.jboss.org/browse/FORGE-1417 Project: Forge Issue Type: Feature Request Components: UI - Shell Affects Versions: 2.0.0.Beta4 Reporter: Lincoln Baxter III {code} [core]$ addon-list | grep furnace org.jboss.forge.furnace.container:cdi,2.0.0-SNAPSHOT org.jboss.forge.furnace.container:simple,2.0.0-SNAPSHOT ***ERROR*** Failure while executing aesh command [core]$ {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, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1417) Piping a forge command to another command succeeds then fails

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1417?page=com.atlassian.jira.plugin... ] Lincoln Baxter III updated FORGE-1417: -------------------------------------- Fix Version/s: 2.x Future > Piping a forge command to another command succeeds then fails > ------------------------------------------------------------- > > Key: FORGE-1417 > URL: https://issues.jboss.org/browse/FORGE-1417 > Project: Forge > Issue Type: Feature Request > Components: UI - Shell > Affects Versions: 2.0.0.Beta4 > Reporter: Lincoln Baxter III > Fix For: 2.x Future > > > {code} > [core]$ addon-list | grep furnace > org.jboss.forge.furnace.container:cdi,2.0.0-SNAPSHOT > org.jboss.forge.furnace.container:simple,2.0.0-SNAPSHOT > ***ERROR*** Failure while executing aesh command > [core]$ {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, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1416) How to know which addons are installed and available ?

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1416?page=com.atlassian.jira.plugin... ] Lincoln Baxter III closed FORGE-1416. ------------------------------------- Fix Version/s: 2.0.0.Final (was: 2.x Future) Resolution: Done Implemented the "addon-list" command. {code} [core]$ addon-list ***SUCCESS*** Currently installed addons: org.jboss.forge.addon:addon-manager,2.0.0-SNAPSHOT org.jboss.forge.addon:addon-manager-spi,2.0.0-SNAPSHOT org.jboss.forge.addon:addons,2.0.0-SNAPSHOT org.jboss.forge.addon:configuration,2.0.0-SNAPSHOT org.jboss.forge.addon:convert,2.0.0-SNAPSHOT org.jboss.forge.addon:core,2.0.0-SNAPSHOT org.jboss.forge.addon:dependencies,2.0.0-SNAPSHOT org.jboss.forge.addon:dev-tools-java,2.0.0-SNAPSHOT org.jboss.forge.addon:environment,2.0.0-SNAPSHOT org.jboss.forge.addon:facets,2.0.0-SNAPSHOT org.jboss.forge.addon:javaee,2.0.0-SNAPSHOT org.jboss.forge.addon:maven,2.0.0-SNAPSHOT org.jboss.forge.addon:parser-java,2.0.0-SNAPSHOT org.jboss.forge.addon:parser-xml,2.0.0-SNAPSHOT org.jboss.forge.addon:projects,2.0.0-SNAPSHOT org.jboss.forge.addon:resources,2.0.0-SNAPSHOT org.jboss.forge.addon:shell,2.0.0-SNAPSHOT org.jboss.forge.addon:shell-spi,2.0.0-SNAPSHOT org.jboss.forge.addon:templates,2.0.0-SNAPSHOT org.jboss.forge.addon:templates-spi,2.0.0-SNAPSHOT org.jboss.forge.addon:text,2.0.0-SNAPSHOT org.jboss.forge.addon:ui,2.0.0-SNAPSHOT org.jboss.forge.addon:ui-spi,2.0.0-SNAPSHOT org.jboss.forge.furnace.container:cdi,2.0.0-SNAPSHOT org.jboss.forge.furnace.container:simple,2.0.0-SNAPSHOT {code} > How to know which addons are installed and available ? > ------------------------------------------------------ > > Key: FORGE-1416 > URL: https://issues.jboss.org/browse/FORGE-1416 > Project: Forge > Issue Type: Sub-task > Components: UI - Shell > Affects Versions: 2.0.0.Beta4 > Reporter: Antonio Goncalves > Assignee: Lincoln Baxter III > Fix For: 2.0.0.Final > > > It would be good to have a few commands to know which addons are available (e.g. {{addon-list --available}}) and which ones are installed (e.g. {{addon-list --installed}}). > Or a more generic {{addon-list}} command that will list all the addons with a flag (installed, available...) -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1416) How to know which addons are installed and available ?

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1416?page=com.atlassian.jira.plugin... ] Lincoln Baxter III reassigned FORGE-1416: ----------------------------------------- Assignee: Lincoln Baxter III > How to know which addons are installed and available ? > ------------------------------------------------------ > > Key: FORGE-1416 > URL: https://issues.jboss.org/browse/FORGE-1416 > Project: Forge > Issue Type: Sub-task > Components: UI - Shell > Affects Versions: 2.0.0.Beta4 > Reporter: Antonio Goncalves > Assignee: Lincoln Baxter III > Fix For: 2.x Future > > > It would be good to have a few commands to know which addons are available (e.g. {{addon-list --available}}) and which ones are installed (e.g. {{addon-list --installed}}). > Or a more generic {{addon-list}} command that will list all the addons with a flag (installed, available...) -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1333) Forge "man" pages are missing for most UI Commands

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1333?page=com.atlassian.jira.plugin... ] Lincoln Baxter III reassigned FORGE-1333: ----------------------------------------- Assignee: Lincoln Baxter III > Forge "man" pages are missing for most UI Commands > -------------------------------------------------- > > Key: FORGE-1333 > URL: https://issues.jboss.org/browse/FORGE-1333 > Project: Forge > Issue Type: Sub-task > Components: UI - Shell > Affects Versions: 2.0.0.Beta4 > Reporter: Antonio Goncalves > Assignee: Lincoln Baxter III > Fix For: 2.x Future > > > This is more a question because I don't know what {{man}} is suppose to do. This is what I get : > {code} > [Test.java]$ man grep > No manual entry for grep > [Test.java]$ man echo > No manual entry for echo > {code} > I would expect to have a manual for each Forge command and also to get completion (e.g. {{man jpa}} TAB and it will give all the JPA commands available in the manual -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1333) Forge "man" pages are missing for most UI Commands

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1333?page=com.atlassian.jira.plugin... ] Lincoln Baxter III closed FORGE-1333. ------------------------------------- Fix Version/s: 2.0.0.Final (was: 2.x Future) Resolution: Done Implemented by auto-generating man pages when full "hand-written" user documentation is unavailable. > Forge "man" pages are missing for most UI Commands > -------------------------------------------------- > > Key: FORGE-1333 > URL: https://issues.jboss.org/browse/FORGE-1333 > Project: Forge > Issue Type: Sub-task > Components: UI - Shell > Affects Versions: 2.0.0.Beta4 > Reporter: Antonio Goncalves > Assignee: Lincoln Baxter III > Fix For: 2.0.0.Final > > > This is more a question because I don't know what {{man}} is suppose to do. This is what I get : > {code} > [Test.java]$ man grep > No manual entry for grep > [Test.java]$ man echo > No manual entry for echo > {code} > I would expect to have a manual for each Forge command and also to get completion (e.g. {{man jpa}} TAB and it will give all the JPA commands available in the manual -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1416) How to know which addons are installed and available ?

by Antonio Goncalves (JIRA)

Antonio Goncalves created FORGE-1416: ---------------------------------------- Summary: How to know which addons are installed and available ? Key: FORGE-1416 URL: https://issues.jboss.org/browse/FORGE-1416 Project: Forge Issue Type: Sub-task Components: UI - Shell Affects Versions: 2.0.0.Beta4 Reporter: Antonio Goncalves Fix For: 2.x Future It would be good to have a few commands to know which addons are available (e.g. {{addon-list --available}}) and which ones are installed (e.g. {{addon-list --installed}}). Or a more generic {{addon-list}} command that will list all the addons with a flag (installed, available...) -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1393) constraint commands are missing

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1393?page=com.atlassian.jira.plugin... ] George Gastaldi commented on FORGE-1393: ---------------------------------------- The syntax is a bit different: {code} constraint-add --javaClass org.demo.model.Customer --constraint Null {code} > constraint commands are missing > ------------------------------- > > Key: FORGE-1393 > URL: https://issues.jboss.org/browse/FORGE-1393 > Project: Forge > Issue Type: Sub-task > Components: UI - Shell > Affects Versions: 2.0.0.Beta4 > Reporter: Antonio Goncalves > Assignee: George Gastaldi > Fix For: 2.0.0.Final > > > On Forge 1.x you could add constraints to a specific field with > {code} > constraint NotNull --onProperty login ; > {code} > The {{constraint}} commands are missing. If we follow the new naming convention, we should have, at least, one command to create new custom constraints (that could go into a default {{constraint}} package for example : > {code} > constraint-new MyOwnConstraint ; > {code} > And a command to add a constraint to a property : > {code} > constraint-add NotNull --onProperty login ; > constraint-add MyOwnConstraint --onProperty lastname ; > {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, 3 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues January 2014