October 2013 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-1302) Provide Eclipse CheatSheets as a quickstart for some Forge plugins

by George Gastaldi (JIRA)

George Gastaldi created FORGE-1302: -------------------------------------- Summary: Provide Eclipse CheatSheets as a quickstart for some Forge plugins Key: FORGE-1302 URL: https://issues.jboss.org/browse/FORGE-1302 Project: Forge Issue Type: Feature Request Components: Brainstorming, UI - Eclipse Affects Versions: 2.0.0.Alpha14 Reporter: George Gastaldi Fix For: 2.x Future -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1301) Shell no longer displays full list of commands when core is installed

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1301?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-1301: ----------------------------------- Steps to Reproduce: # Delete ~/.forge # Run {{./forge -i core}} # Start forge # Press <TAB> If reproduced correctly, you'll see only *alias* and *unalias* commands available. was: # Delete ~/.forge # Run {{./forge -i core}} # Start forge # Press <TAB> If you could reproduce it correctly, you'll see only *alias* and *unalias* commands available. > Shell no longer displays full list of commands when core is installed > --------------------------------------------------------------------- > > Key: FORGE-1301 > URL: https://issues.jboss.org/browse/FORGE-1301 > Project: Forge > Issue Type: Bug > Components: Furnace (Container) > Affects Versions: 2.0.0.Alpha14 > Reporter: George Gastaldi > Priority: Blocker > Fix For: 2.0.0.Beta1 > > > It was observed that this is caused when the simple-container is enabled -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1301) Shell no longer displays full list of commands when core is installed

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1301?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-1301: ----------------------------------- Description: It was observed that this is caused when the simple-container is enabled (was: This is caused because the simple-container is installed with core) > Shell no longer displays full list of commands when core is installed > --------------------------------------------------------------------- > > Key: FORGE-1301 > URL: https://issues.jboss.org/browse/FORGE-1301 > Project: Forge > Issue Type: Bug > Components: Furnace (Container) > Affects Versions: 2.0.0.Alpha14 > Reporter: George Gastaldi > Priority: Blocker > Fix For: 2.0.0.Beta1 > > > It was observed that this is caused when the simple-container is enabled -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1301) Shell no longer displays full list of commands when core is installed

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1301?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-1301: ----------------------------------- Fix Version/s: 2.0.0.Beta1 > Shell no longer displays full list of commands when core is installed > --------------------------------------------------------------------- > > Key: FORGE-1301 > URL: https://issues.jboss.org/browse/FORGE-1301 > Project: Forge > Issue Type: Bug > Components: Furnace (Container) > Affects Versions: 2.0.0.Alpha14 > Reporter: George Gastaldi > Priority: Blocker > Fix For: 2.0.0.Beta1 > > > This is caused because the simple-container is installed with core -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1301) Shell no longer displays full list of commands when core is installed

by George Gastaldi (JIRA)

George Gastaldi created FORGE-1301: -------------------------------------- Summary: Shell no longer displays full list of commands when core is installed Key: FORGE-1301 URL: https://issues.jboss.org/browse/FORGE-1301 Project: Forge Issue Type: Bug Components: Furnace (Container) Affects Versions: 2.0.0.Alpha14 Reporter: George Gastaldi Priority: Blocker This is caused because the simple-container is installed with core -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1296) Allow constraints to be specified on the versions of the Facets during setup

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1296?page=com.atlassian.jira.plugin... ] George Gastaldi reassigned FORGE-1296: -------------------------------------- Assignee: George Gastaldi > Allow constraints to be specified on the versions of the Facets during setup > ---------------------------------------------------------------------------- > > Key: FORGE-1296 > URL: https://issues.jboss.org/browse/FORGE-1296 > Project: Forge > Issue Type: Feature Request > Components: UI - API > Affects Versions: 2.0.0.Alpha14 > Reporter: Vineet Reynolds > Assignee: George Gastaldi > > The current implementation of the Scaffold and possibly other addons, verifies if facets are setup and then proceeds to add the wizards for these facets to the NavigationResult. > It is possible that some of the versions displayed in the individual wizards will not be applicable when used in a composite wizard like the scaffold. We need to find a way for the composite to hint or specify the allowed versions of the individual facets. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1296) Allow constraints to be specified on the versions of the Facets during setup

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1296?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-1296: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/forge/core/pull/358 > Allow constraints to be specified on the versions of the Facets during setup > ---------------------------------------------------------------------------- > > Key: FORGE-1296 > URL: https://issues.jboss.org/browse/FORGE-1296 > Project: Forge > Issue Type: Feature Request > Components: UI - API > Affects Versions: 2.0.0.Alpha14 > Reporter: Vineet Reynolds > > The current implementation of the Scaffold and possibly other addons, verifies if facets are setup and then proceeds to add the wizards for these facets to the NavigationResult. > It is possible that some of the versions displayed in the individual wizards will not be applicable when used in a composite wizard like the scaffold. We need to find a way for the composite to hint or specify the allowed versions of the individual facets. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1298) Forge should display Maven activity while installing addons

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1298?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1298. ---------------------------------- Assignee: George Gastaldi Fix Version/s: 2.0.0.Beta1 (was: 2.x Future) Resolution: Done > Forge should display Maven activity while installing addons > ----------------------------------------------------------- > > Key: FORGE-1298 > URL: https://issues.jboss.org/browse/FORGE-1298 > Project: Forge > Issue Type: Enhancement > Components: Addon Manager > Affects Versions: 2.0.0.Alpha14 > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 2.0.0.Beta1 > > > Otherwise it seems that the command hangs and you think that there's something wrong. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1300) sun.misc.Signal is restricted in Furnace

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1300?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1300. ---------------------------------- Assignee: George Gastaldi Resolution: Done > sun.misc.Signal is restricted in Furnace > ---------------------------------------- > > Key: FORGE-1300 > URL: https://issues.jboss.org/browse/FORGE-1300 > Project: Forge > Issue Type: Bug > Components: Furnace (Container) > Affects Versions: 2.0.0.Alpha14 > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 2.0.0.Beta1 > > > Aesh needs this class to register interrupt hooks -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-944) Thoughts on CLI renaming on Forge 2

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-944?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III commented on FORGE-944: ------------------------------------------ Okay, the remove-an-addon etc, commands have been renamed to addon-install addon-remove addon-install-build (not sure about this last one.) > Thoughts on CLI renaming on Forge 2 > ----------------------------------- > > Key: FORGE-944 > URL: https://issues.jboss.org/browse/FORGE-944 > Project: Forge > Issue Type: Enhancement > Components: Brainstorming > Affects Versions: 2.x Future > Reporter: Antonio Goncalves > Priority: Optional > Labels: cli, renaming > Fix For: 2.x Future > > > I was talking about having CLI naming conventions on the forum and George and Lincoln suggested to add these ideas on a JIRA. So here is my humble contribution to record all the ideas about renaming commands. > Disclaimer : I haven't used Forge for a long time, I've just started using it again, so some of the following ideas might not be accurate > As a new comer in Forge I felt the commands were not that intuitive. I loved the following : > {code} > java new-enum-type > java new-itnerface > java new-class > {code} > > So I was expecting to have something similar in all the other techologies, such as JPA : > {code} > jpa new-entity (instead of entity --named) > jpa new-embedable > jpa new-mapped-superclass --named Person > jpa new-entity --named Vet --extends Person > {code} > Lincoln suggested having single-level command keywords only such as : > {code} > jpa-new-entity (instead of entity --named) > jpa-new-embedable > jpa-new-mapped-superclass --named Person > jpa-new-entity --named Vet --extends Person > {code} > h3. Verbs and keywords > When you look at the commansd, there are several common verbs and keywords than come often : > {code} > add : ejb-add-transaction-attribute > new : beans-new-bean, faces-new-view, new-project (prefer project-new) > list : list-web-resources, beans list-interceptors, beans list-alternatives, list-scaffold-providers > setup : ejb setup, entity setup > put : i18n put > remove : i18n remove, project remove-property > execute : execute-java > set : maven set-groupid > find : forge find-plugin > install : > update : forge update-abort, gitignore update-repo > run : run-url > info : analytics info > {code} > That brings several thoughts : > * {{ls}} is used as well as {{list}}, should this be homogenize (e.g. beans-ls-interceptors) > * {{rm}} is used as well as {{remove}}, should this be homogenize (e.g. i18n-rm, project-rm-property) > * The difference between {{execute}} and {{run}} is not clear, should this be homogenize and only use one ? > * Also there is {{execute}} and {{exec}}, this should be homogenize (e.g. {{execute-java}} and {{exec}}) > * Confusion between {{new}} and {{add}}. You create a new class with {{java-new-class}} and shouldn't you add a field and a method to existing class ({{java-add-field}} instead of {{java-new-field}}) > * Some confusion between {{maven}} and {{project}} > * Is there any difference between {{set}} and {{update}} ? {{maven set-artifactid}} updates the already existing artifactId and {{gitignore update-repo}} updates an existing repo > * we use {{field}} (e.g. {{java-add-field}}) and then property ({{constraint Future --onProperty date}}), it should be fiels ({{constraint Future --onField date}}) > In many commands you find a type argument such as ({{type}}, {{scaffoldType}}, {{fieldType}} : > {code} > scaffold setup --scaffoldType faces > field manyToMany --named specialties --fieldType ~.model.Specialty.java > field temporal --type DATE --named date > {code} > Why not having only {{type}} in all the cases : > {code} > scaffold-setup --type faces > jpa-add-field manyToMany --named specialties --type ~.model.Specialty.java > jpa-add-field temporal --named date --type DATE > {code} > h3. Grammar > The CLI grammar could look like this : > {code} > command = shell | forge command ; > forge command = technology,-action,[-artifact] [{--argument value}] ; > shell = cat | cd | cp | edit | find | grep | ls ... > technology = project | scaffold | beans | constraint | java | jpa | i18n | ejb ... > action = add | new | ls | rm | setup ... > artifact = providers | interceptors | class | filter... > argument = named | onField | type | extends > {code} > h3. Examples > So if we take that grammar and apply single-level command keywords, we could have things like that : > {code} > mkdir > ls > ls-commands -all > project-new --named MyPro > scaffold-ls-providers > scaffold-templates --scaffoldType faces > beans-ls-interceptors > constraint-new-constraint --named MyConstraint > constraint-add-constraint MyConstraint --onField MyProp > java-new-class --named MyClass > java-add-field 'private List<Vet> vets' > java-add-method 'public List<Vet> getVetList() {return null;}' > java-add-annotation --type XmlRootElement --onClass MyClass > java-add-annotation --type XmlAttribute --onField MyProp > jpa-new-mapped-superclass --named Person > jpa-new-entity --named Vet --extends Person > jpa-add-field manyToOne --named owner --type ~.model.Owner.java > i18n-add-locale --locale PT > ejb-new-stateless --named MyStateless > ejb-new-singleton --named MySingleton --implements MyInterface AndAnotherInterface > ejb-add-transaction-attribute --type NEVER > ejb-add-transaction-attribute --type NEVER --onMethod MyNeverMethod > faces-new-view --named MyView > faces-set-project-stage --stage PRODUCTION > servlet-new-filter --named MyFilter > rest-new-endpoint --named MyEndpoint --extends MyRestExtension > mvn-build --notest > {code} > Scaffolding is a bit tricky because it's extendable and you could end up with > {code} > scaffold-ui-from-entity ~.model.* > scaffold-rest-endpoint-from-entity ~.model.* > scaffold-dao-from-entity ~.model.* > scaffold-ejb-service-from-dao ~.dao.* > scaffold-rest-endpoint-from-dao ~.dao.* > {code} > Or something like that > {code} > scaffold --ui --from-entity ~.model.* > scaffold --rest-endpoint --from-entity ~.model.* > scaffold --dao --from-entity ~.model.* > scaffold --ejb-service --from-dao ~.dao.* > scaffold --rest-endpoint --from-dao ~.dao.* > {code} > Here are my 2 cents thoughts on a topic that I'm discovering. As you all know, naming is really important and should be looked at carefully. Let's use this JIRA to exchange ideas. -- 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, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues October 2013