November 2014 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-2056) Commands to add and remove plugins repository into pom.xml

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2056?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-2056: ----------------------------------- Labels: starter (was: ) > Commands to add and remove plugins repository into pom.xml > ---------------------------------------------------------- > > Key: FORGE-2056 > URL: https://issues.jboss.org/browse/FORGE-2056 > Project: Forge > Issue Type: Sub-task > Components: UI - Shell > Affects Versions: 2.12.0.Final > Reporter: Antonio Goncalves > Labels: starter > Fix For: 2.x Future > > > Today we have commands to add/remove dependencies into a `pom.xml` : > {code} > project-add-repository > project-remove-repository > {code} > We need to same functionnalites but for plugin repositories. Commands such as : > {code} > project-add-plugin-repository > project-remove-plugin-repository > {code} > So a command like this : > {code} > project-add-plugin-repository --named jboss-public --url https://repository.jboss.org/nexus/content/groups/public/ ; > {code} > Would add the following to the {{pom.xml}} : > {code} > <pluginRepositories > > <pluginRepository > > <id>jboss-public</id> > <url>https://repository.jboss.org/nexus/content/groups/public/</url> > </pluginRepository > > </pluginRepositories > > {code} -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2047) Commands to add and remove Maven plugins into pom.xml

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2047?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-2047: ----------------------------------- Labels: starter (was: ) > Commands to add and remove Maven plugins into pom.xml > ----------------------------------------------------- > > Key: FORGE-2047 > URL: https://issues.jboss.org/browse/FORGE-2047 > Project: Forge > Issue Type: Sub-task > Components: UI - Shell > Affects Versions: 2.10.1.Final > Reporter: Antonio Goncalves > Labels: starter > Fix For: 2.x Future > > > Today we have commands to add/remove dependencies into a `pom.xml` : > {code} > project-add-dependencies > project-remove-dependencies > project-add-managed-dependencies > project-remove-managed-dependencies > {code} > We need to same functionnalites but for plugins. Commands such as : > {code} > project-add-plugin-dependencies > project-remove-plugin-dependencies > {code} > So a command like this : > {code} > project-add-plugin-dependencies org.codehaus.mojo:exec-maven-plugin:1.3.1 > {code} > Would add the following to the {{pom.xml}} : > {code} > <plugins> > <plugin> > <groupId>org.codehaus.mojo</groupId> > <artifactId>exec-maven-plugin</artifactId> > <version>1.3.1</version> > </plugin> > </plugins> > {code} -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2041) parameterless wizards are not friendly

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2041?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-2041. ---------------------------------- Assignee: George Gastaldi Resolution: Done > parameterless wizards are not friendly > -------------------------------------- > > Key: FORGE-2041 > URL: https://issues.jboss.org/browse/FORGE-2041 > Project: Forge > Issue Type: Feature Request > Components: UI - Shell > Affects Versions: 2.12.2.Final > Reporter: Jess Sightler > Assignee: George Gastaldi > Fix For: 2.12.3.Final > > > Example usage: > [tmp]$ project-new > Project name: Whatwillthisdo > ***SUCCESS*** Project named 'Whatwillthisdo' has been created. > That doesn't seem like I provided enough information for it to do anything useful, but that is the only question that it asked. And the logging is insufficient to know what kind of project it created or any other used defaults. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2041) parameterless wizards are not friendly

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2041?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-2041: ----------------------------------- Fix Version/s: 2.12.3.Final Affects Version/s: 2.12.2.Final Component/s: UI - Shell > parameterless wizards are not friendly > -------------------------------------- > > Key: FORGE-2041 > URL: https://issues.jboss.org/browse/FORGE-2041 > Project: Forge > Issue Type: Feature Request > Components: UI - Shell > Affects Versions: 2.12.2.Final > Reporter: Jess Sightler > Fix For: 2.12.3.Final > > > Example usage: > [tmp]$ project-new > Project name: Whatwillthisdo > ***SUCCESS*** Project named 'Whatwillthisdo' has been created. > That doesn't seem like I provided enough information for it to do anything useful, but that is the only question that it asked. And the logging is insufficient to know what kind of project it created or any other used defaults. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2041) parameterless wizards are not friendly

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2041?page=com.atlassian.jira.plugin... ] George Gastaldi commented on FORGE-2041: ---------------------------------------- {quote} <lincolnthree> gastaldi: we should have more of a wizard flow when working in prompts like that <gastaldi> so we should improve the message? <gastaldi> hm <lincolnthree> gastaldi: it would be nice if it said the description of the command and started walking through prompts, if not all inputs are satisfied <lincolnthree> gastaldi: it should probably also walk through default options even if they have been specified <lincolnthree> gastaldi: so basically, omitting a required option should send you into prompt mode <lincolnthree> gastaldi: where it goes through and confirms all values that you haven't actually specified <lincolnthree> gastaldi: in the initial line <gastaldi> even for the not required inputs? <lincolnthree> yea, i think so <lincolnthree> but it should also say, "Press <ENTER> to use the default value [Value] <lincolnthree> (after giving a description of what the value is <lincolnthree> gastaldi: right now theres no way to use a wizard if any values were omitted on the CLI. it will just default to defaults <lincolnthree> gastaldi: and if we're going to prompt at all, instead of just failing, i think it makes sense to do this <gastaldi> hmmmm <gastaldi> right <gastaldi> that would be a more "wizard-like" experience <gastaldi> should that be triggered only if a required input is not provided? <lincolnthree> gastaldi: yes, I think so <lincolnthree> gastaldi: only if they miss something required <lincolnthree> it should say something like, (Required inputs not satisfied, entering interactive mode.) <lincolnthree> then give a description of the command, and a description of each input as they are prompted <lincolnthree> (obviously they won't be able to go back) <lincolnthree> (but it should be pretty easy to walk through all inputs) {quote} > parameterless wizards are not friendly > -------------------------------------- > > Key: FORGE-2041 > URL: https://issues.jboss.org/browse/FORGE-2041 > Project: Forge > Issue Type: Feature Request > Affects Versions: 2.12.2.Final > Reporter: Jess Sightler > Fix For: 2.12.3.Final > > > Example usage: > [tmp]$ project-new > Project name: Whatwillthisdo > ***SUCCESS*** Project named 'Whatwillthisdo' has been created. > That doesn't seem like I provided enough information for it to do anything useful, but that is the only question that it asked. And the logging is insufficient to know what kind of project it created or any other used defaults. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2142) Prompt for UISelectMany should allow unselecting values

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2142?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-2142. ---------------------------------- Resolution: Done > Prompt for UISelectMany should allow unselecting values > ------------------------------------------------------- > > Key: FORGE-2142 > URL: https://issues.jboss.org/browse/FORGE-2142 > Project: Forge > Issue Type: Enhancement > Components: UI - Shell > Affects Versions: 2.12.2.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 2.12.3.Final > > > When a required UISelectMany input is not provided, the shell prompts from values from the available value choices set in the component. However it should be possible to unselect previously selected values. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2142) Prompt for UISelectMany should allow unselecting values

by George Gastaldi (JIRA)

George Gastaldi created FORGE-2142: -------------------------------------- Summary: Prompt for UISelectMany should allow unselecting values Key: FORGE-2142 URL: https://issues.jboss.org/browse/FORGE-2142 Project: Forge Issue Type: Enhancement Components: UI - Shell Affects Versions: 2.12.2.Final Reporter: George Gastaldi Assignee: George Gastaldi Fix For: 2.12.3.Final When a required UISelectMany input is not provided, the shell prompts from values from the available value choices set in the component. However it should be possible to unselect previously selected values. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2141) rest-generate-endpoints-from-entities selector does not select correct entity

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2141?page=com.atlassian.jira.plugin... ] George Gastaldi commented on FORGE-2141: ---------------------------------------- The correct command is: {{rest-generate-endpoints-from-entities --targets org.cdbookstore.model.*}} Have you tried the following steps? 1) Run {{rest-generate-endpoints-from-entities}} You should see {code} [0] - org.bookstore.model.Author [1] - org.bookstore.model.Book Target: [0-1]: {code} 2) Press "0" and then press <ENTER> 3) When the next prompt appears (with Book entity only), do not select anything and press <ENTER> 4) Check if the AuthorEndpoint is created. > rest-generate-endpoints-from-entities selector does not select correct entity > ----------------------------------------------------------------------------- > > Key: FORGE-2141 > URL: https://issues.jboss.org/browse/FORGE-2141 > Project: Forge > Issue Type: Bug > Affects Versions: 2.12.2.Final > Reporter: Tom Van den Bulck > Priority: Minor > Attachments: jboss forge error.jpg > > > When executing the command rest-generate-endpoints-from-entities --target org.cdbookstore.model.* > It provides a selector > [0] - org.bookstore.model.Author > [1] - org.bookstore.model.Book > Target: [0-1]: 0 > This gives the following result > [0] - org.bookstore.model.Book (which was selection 1) > And vice versa, pressing 1 gives the Author object to select -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2141) rest-generate-endpoints-from-entities selector does not select correct entity

by Tom Van den Bulck (JIRA)

[ https://issues.jboss.org/browse/FORGE-2141?page=com.atlassian.jira.plugin... ] Tom Van den Bulck updated FORGE-2141: ------------------------------------- Attachment: jboss forge error.jpg Attached is a screenshot of the sequence. It did not create the author endpoint after pressing 0 (for the 1st time) It created the book endpoint after pressing 0 for the second time. For the author endpoint I had to select first 1 as an option and then 0 again. > rest-generate-endpoints-from-entities selector does not select correct entity > ----------------------------------------------------------------------------- > > Key: FORGE-2141 > URL: https://issues.jboss.org/browse/FORGE-2141 > Project: Forge > Issue Type: Bug > Affects Versions: 2.12.2.Final > Reporter: Tom Van den Bulck > Priority: Minor > Attachments: jboss forge error.jpg > > > When executing the command rest-generate-endpoints-from-entities --target org.cdbookstore.model.* > It provides a selector > [0] - org.bookstore.model.Author > [1] - org.bookstore.model.Book > Target: [0-1]: 0 > This gives the following result > [0] - org.bookstore.model.Book (which was selection 1) > And vice versa, pressing 1 gives the Author object to select -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2141) rest-generate-endpoints-from-entities selector does not select correct entity

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2141?page=com.atlassian.jira.plugin... ] George Gastaldi commented on FORGE-2141: ---------------------------------------- The correct option name is {{targets}} btw > rest-generate-endpoints-from-entities selector does not select correct entity > ----------------------------------------------------------------------------- > > Key: FORGE-2141 > URL: https://issues.jboss.org/browse/FORGE-2141 > Project: Forge > Issue Type: Bug > Affects Versions: 2.12.2.Final > Reporter: Tom Van den Bulck > Priority: Minor > > When executing the command rest-generate-endpoints-from-entities --target org.cdbookstore.model.* > It provides a selector > [0] - org.bookstore.model.Author > [1] - org.bookstore.model.Book > Target: [0-1]: 0 > This gives the following result > [0] - org.bookstore.model.Book (which was selection 1) > And vice versa, pressing 1 gives the Author object to select -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 2 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues November 2014