June 2016 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-1403) Pressing TAB twice while completing should print a description of the current option being completed

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1403?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-1403: ----------------------------------- Parent: (was: FORGE-944) Issue Type: Enhancement (was: Sub-task) > Pressing TAB twice while completing should print a description of the current option being completed > ---------------------------------------------------------------------------------------------------- > > Key: FORGE-1403 > URL: https://issues.jboss.org/browse/FORGE-1403 > Project: Forge > Issue Type: Enhancement > Components: UI - Shell > Affects Versions: 2.0.0.Beta4 > Reporter: Lincoln Baxter III > Fix For: 3.x Future > > > Forge 1 is very good about helping the user figure out what various command options are for. Forge 2 lacks this helpful information, and it would be useful to display. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2088) Man page documentation is incorrect. Required options being displayed as optional in SYNOPSIS

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2088?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-2088. ---------------------------------- Fix Version/s: 3.0.0.Final (was: 3.x Future) Resolution: Done > Man page documentation is incorrect. Required options being displayed as optional in SYNOPSIS > --------------------------------------------------------------------------------------------- > > Key: FORGE-2088 > URL: https://issues.jboss.org/browse/FORGE-2088 > Project: Forge > Issue Type: Bug > Affects Versions: 2.12.1.Final > Reporter: Ondrej Zizka > Fix For: 3.0.0.Final > > > Not sure if bug or feature, either way - I'd expect that feeding addon-remove an item from addon-list would remove it. Not the case: > $ addon-list > Currently installed addons: > ... > org.jboss.windup.qs:WindupQuickstart,2.0.0.Beta2 > ... > [javaee-WLServlet]$ addon-remove org.jboss.windup.qs:WindupQuickstart,2.0.0.Beta2 > ***ERROR*** Installed addons must be specified -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-944) Establish CLI naming guidelines for Forge 2

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-944?page=com.atlassian.jira.plugin.... ] George Gastaldi closed FORGE-944. --------------------------------- Fix Version/s: 3.0.0.Final (was: 3.x Future) Resolution: Done > Establish CLI naming guidelines for 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: 3.0.0.Final > > > 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 was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2491) Upgrade to Aesh 0.67

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2491?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-2491. ---------------------------------- Resolution: Won't Do > Upgrade to Aesh 0.67 > -------------------- > > Key: FORGE-2491 > URL: https://issues.jboss.org/browse/FORGE-2491 > Project: Forge > Issue Type: Component Upgrade > Components: UI - Shell > Affects Versions: 2.19.2.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 3.x Future > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1909) Refactor Resource API

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1909?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1909. ---------------------------------- Resolution: Out of Date > Refactor Resource API > --------------------- > > Key: FORGE-1909 > URL: https://issues.jboss.org/browse/FORGE-1909 > Project: Forge > Issue Type: Feature Request > Components: Resources > Reporter: Shane Bryzak > Assignee: Shane Bryzak > Fix For: 3.x Future > > > Refactor the resource API for Forge 3.0, removing the existing File and Directory-based resources and replacing with Path resources -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1727) Add PathResource based on the Java 7 NIO Files API

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1727?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1727. ---------------------------------- Resolution: Out of Date > Add PathResource based on the Java 7 NIO Files API > -------------------------------------------------- > > Key: FORGE-1727 > URL: https://issues.jboss.org/browse/FORGE-1727 > Project: Forge > Issue Type: Feature Request > Components: Resources > Affects Versions: 2.3.0.Final > Reporter: Shane Bryzak > Assignee: Shane Bryzak > Fix For: 3.x Future > > > Also update all addons to use this. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[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 closed FORGE-552. --------------------------------- Resolution: Out of Date Seems to be working now > 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: 3.x Future, 2.0.0.Alpha14 > > > 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)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-984) Create base class for Bean classes generated by scaffold from-entity

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-984?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-984: ---------------------------------- Priority: Optional (was: Trivial) > Create base class for Bean classes generated by scaffold from-entity > -------------------------------------------------------------------- > > Key: FORGE-984 > URL: https://issues.jboss.org/browse/FORGE-984 > Project: Forge > Issue Type: Enhancement > Components: Scaffold > Affects Versions: 1.3.2.Final > Reporter: George Gastaldi > Priority: Optional > Fix For: 3.x Future > > > In order to promote code reuse, we should generate an abstract Bean class and make all Beans generated by the scaffold extend this abstract class. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2649) Netbeans cannot find plugin to install forge

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2649?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-2649. ---------------------------------- Assignee: George Gastaldi Resolution: Done Fixed by the Netbeans team. Looks like it was an infrastructure issue. Thanks! > Netbeans cannot find plugin to install forge > -------------------------------------------- > > Key: FORGE-2649 > URL: https://issues.jboss.org/browse/FORGE-2649 > Project: Forge > Issue Type: Bug > Components: UI - NetBeans > Reporter: Tony Diep > Assignee: George Gastaldi > Priority: Minor > Attachments: Screenshot from 2016-05-20 07-54-02.png > > > When installing forge plugin in Netbeans, IDE fails with error that it cannot find the plugin file "Networking problem in http://plugins.netbeans.org/nbpluginportal/files/nbms/z4703_ui-1.1.11.Fin..." -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ROASTER-103) compute serialUID incomplete

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/ROASTER-103?page=com.atlassian.jira.plugi... ] George Gastaldi reassigned ROASTER-103: --------------------------------------- Assignee: Nicolas Challut > compute serialUID incomplete > ---------------------------- > > Key: ROASTER-103 > URL: https://issues.jboss.org/browse/ROASTER-103 > Project: Roaster > Issue Type: Bug > Affects Versions: 2.18.7.Final > Reporter: Nicolas Challut > Assignee: Nicolas Challut > > If I extend a class which implements Serializable, I have to have a serialVersionUID even if I don't implements Serializable myself. But SerialVersionUIDComputer.compute() returrn 0... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues June 2016