December 2012 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-721) When using scheduling can't change default directory from com.example

by Robb Greathouse (JIRA)

Robb Greathouse created FORGE-721: ------------------------------------- Summary: When using scheduling can't change default directory from com.example Key: FORGE-721 URL: https://issues.jboss.org/browse/FORGE-721 Project: Forge Issue Type: Bug Components: Scaffold Affects Versions: 1.1.2.Final Environment: Forge 1.1.2 on MAC with JDK 1.7 Reporter: Robb Greathouse When I use forge to create a project this is under a directory structure other than com.example.[project name] for example com.jboss is still creates the view and rest components under com.example -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-720) Ability to install / uninstall addons from command line

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-720?page=com.atlassian.jira.plugin.... ] George Gastaldi resolved FORGE-720. ----------------------------------- Resolution: Done Installation is ok > Ability to install / uninstall addons from command line > ------------------------------------------------------- > > Key: FORGE-720 > URL: https://issues.jboss.org/browse/FORGE-720 > Project: Forge > Issue Type: Feature Request > Components: Usability > Reporter: Lincoln Baxter III > Assignee: George Gastaldi > Fix For: 2.0.0.Alpha1 > > > {code}forge --install org.jboss.forge:example,2.0.0-SNAPSHOT{code} > the forge shell script itself should be able to kick off an installation of an addon > 1:18 > gastaldi > hum > 1:18 > lincolnthree > forge --install org.example:plugin,2.0.0-SNAPSHOT —repository=~/.forge/custom_addons_dir > 1:18 > kenfinnigan > so would that start forge, install an addon, and forge be ready with that addon? > 1:18 > lincolnthree > it would then shut down > but the addon would be installed > 1:18 > kenfinnigan > ah ok > 1:18 > lincolnthree > so basically like forge -e > but just for installing addons > removal should also be possible > and listing what's there > should be easy to do! > 1:19 > relatively -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-720) Ability to install / uninstall addons from command line

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-720?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-720: ---------------------------------- Description: {code}forge --install org.jboss.forge:example,2.0.0-SNAPSHOT{code} the forge shell script itself should be able to kick off an installation of an addon 1:18 gastaldi hum 1:18 lincolnthree forge --install org.example:plugin,2.0.0-SNAPSHOT —repository=~/.forge/custom_addons_dir 1:18 kenfinnigan so would that start forge, install an addon, and forge be ready with that addon? 1:18 lincolnthree it would then shut down but the addon would be installed 1:18 kenfinnigan ah ok 1:18 lincolnthree so basically like forge -e but just for installing addons removal should also be possible and listing what's there should be easy to do! 1:19 relatively was: {code}forge --install org.example:plugin,2.0.0-SNAPSHOT{code} the forge shell script itself should be able to kick off an installation of an addon 1:18 gastaldi hum 1:18 lincolnthree forge --install org.example:plugin,2.0.0-SNAPSHOT —repository=~/.forge/custom_addons_dir 1:18 kenfinnigan so would that start forge, install an addon, and forge be ready with that addon? 1:18 lincolnthree it would then shut down but the addon would be installed 1:18 kenfinnigan ah ok 1:18 lincolnthree so basically like forge -e but just for installing addons removal should also be possible and listing what's there should be easy to do! 1:19 relatively > Ability to install / uninstall addons from command line > ------------------------------------------------------- > > Key: FORGE-720 > URL: https://issues.jboss.org/browse/FORGE-720 > Project: Forge > Issue Type: Feature Request > Components: Usability > Reporter: Lincoln Baxter III > Assignee: George Gastaldi > Fix For: 2.0.0.Alpha1 > > > {code}forge --install org.jboss.forge:example,2.0.0-SNAPSHOT{code} > the forge shell script itself should be able to kick off an installation of an addon > 1:18 > gastaldi > hum > 1:18 > lincolnthree > forge --install org.example:plugin,2.0.0-SNAPSHOT —repository=~/.forge/custom_addons_dir > 1:18 > kenfinnigan > so would that start forge, install an addon, and forge be ready with that addon? > 1:18 > lincolnthree > it would then shut down > but the addon would be installed > 1:18 > kenfinnigan > ah ok > 1:18 > lincolnthree > so basically like forge -e > but just for installing addons > removal should also be possible > and listing what's there > should be easy to do! > 1:19 > relatively -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-720) Ability to install / uninstall addons from command line

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-720?page=com.atlassian.jira.plugin.... ] Work on FORGE-720 started by George Gastaldi. > Ability to install / uninstall addons from command line > ------------------------------------------------------- > > Key: FORGE-720 > URL: https://issues.jboss.org/browse/FORGE-720 > Project: Forge > Issue Type: Feature Request > Components: Usability > Reporter: Lincoln Baxter III > Assignee: George Gastaldi > Fix For: 2.0.0.Alpha1 > > > {code}forge --install org.example:plugin,2.0.0-SNAPSHOT{code} > the forge shell script itself should be able to kick off an installation of an addon > 1:18 > gastaldi > hum > 1:18 > lincolnthree > forge --install org.example:plugin,2.0.0-SNAPSHOT —repository=~/.forge/custom_addons_dir > 1:18 > kenfinnigan > so would that start forge, install an addon, and forge be ready with that addon? > 1:18 > lincolnthree > it would then shut down > but the addon would be installed > 1:18 > kenfinnigan > ah ok > 1:18 > lincolnthree > so basically like forge -e > but just for installing addons > removal should also be possible > and listing what's there > should be easy to do! > 1:19 > relatively -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-720) Ability to install / uninstall addons from command line

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-720?page=com.atlassian.jira.plugin.... ] George Gastaldi reassigned FORGE-720: ------------------------------------- Assignee: George Gastaldi > Ability to install / uninstall addons from command line > ------------------------------------------------------- > > Key: FORGE-720 > URL: https://issues.jboss.org/browse/FORGE-720 > Project: Forge > Issue Type: Feature Request > Components: Usability > Reporter: Lincoln Baxter III > Assignee: George Gastaldi > Fix For: 2.0.0.Alpha1 > > > {code}forge --install org.example:plugin,2.0.0-SNAPSHOT{code} > the forge shell script itself should be able to kick off an installation of an addon > 1:18 > gastaldi > hum > 1:18 > lincolnthree > forge --install org.example:plugin,2.0.0-SNAPSHOT —repository=~/.forge/custom_addons_dir > 1:18 > kenfinnigan > so would that start forge, install an addon, and forge be ready with that addon? > 1:18 > lincolnthree > it would then shut down > but the addon would be installed > 1:18 > kenfinnigan > ah ok > 1:18 > lincolnthree > so basically like forge -e > but just for installing addons > removal should also be possible > and listing what's there > should be easy to do! > 1:19 > relatively -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-719) Design an user interface API for addons

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-719?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III commented on FORGE-719: ------------------------------------------ Of course we can provide some convenience APIs on top of this as well, but we need something core and low-level to provide the kind of abstraction necessary. I'm not saying my suggestion is the answer, but it's got to be something that really provides a strong type-safe view of how to interact with the user data. > Design an user interface API for addons > --------------------------------------- > > Key: FORGE-719 > URL: https://issues.jboss.org/browse/FORGE-719 > Project: Forge > Issue Type: Story > Components: Brainstorming > Reporter: George Gastaldi > Fix For: 2.0.0.Alpha1 > > > Requirements: > - It must be usable in a Shell UI > - It should be usable in a Visual UI (SWT, Swing) > - It must be typesafe, therefore allowing the use of complex types. > Let's use this JIRA to brainstorm about it. -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-719) Design an user interface API for addons

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-719?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III commented on FORGE-719: ------------------------------------------ We're trying to design the next Plugin API - as we call it in Forge 1. So we need a programming model that lets people declare interactions in a manner that is agnostic of the UI it will eventually be presented in. {code}public interface Interaction { public String getName(); public Set<Rule> getRules(); public Set<Input> getInputs(); public PreparedInteraction prepare(PopulatedInput... inputs); }{code} {code}public interface PopulatedInput<T> { public T getValue(); }{code} {code}public interface PreparedInteraction { public void perform(); }{code} This is just an example initial interface. My idea here is that each interaction has a name (possibly something we can move to an Annotation instead, but just thinking out loud.) Each interaction also has a set of inputs. This would be every possible input that could ever be required to run the plugin. The rules would then be used to specify which inputs to show or not show, and in what order. The inputs become populated as their values are filled in by the UI/Rules, and then those populated inputs are passed to the prepare() method, which returns an object ready to perform() the given interaction. I know this is a bit rough around the edges, but it's an idea. We should probably look at some other frameworks out there and see what other people have done, and try to take some of what works and adapt it for Forge. > Design an user interface API for addons > --------------------------------------- > > Key: FORGE-719 > URL: https://issues.jboss.org/browse/FORGE-719 > Project: Forge > Issue Type: Story > Components: Brainstorming > Reporter: George Gastaldi > Fix For: 2.0.0.Alpha1 > > > Requirements: > - It must be usable in a Shell UI > - It should be usable in a Visual UI (SWT, Swing) > - It must be typesafe, therefore allowing the use of complex types. > Let's use this JIRA to brainstorm about it. -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-720) Ability to install / uninstall addons from command line

by Lincoln Baxter III (JIRA)

Lincoln Baxter III created FORGE-720: ---------------------------------------- Summary: Ability to install / uninstall addons from command line Key: FORGE-720 URL: https://issues.jboss.org/browse/FORGE-720 Project: Forge Issue Type: Feature Request Components: Usability Reporter: Lincoln Baxter III Fix For: 2.0.0.Alpha1 {code}forge --install org.example:plugin,2.0.0-SNAPSHOT{code} the forge shell script itself should be able to kick off an installation of an addon 1:18 gastaldi hum 1:18 lincolnthree forge --install org.example:plugin,2.0.0-SNAPSHOT —repository=~/.forge/custom_addons_dir 1:18 kenfinnigan so would that start forge, install an addon, and forge be ready with that addon? 1:18 lincolnthree it would then shut down but the addon would be installed 1:18 kenfinnigan ah ok 1:18 lincolnthree so basically like forge -e but just for installing addons removal should also be possible and listing what's there should be easy to do! 1:19 relatively -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-719) Design an user interface API for addons

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-719?page=com.atlassian.jira.plugin.... ] George Gastaldi commented on FORGE-719: --------------------------------------- It would be nice to have a common API with could be used to provide some tips to the UI Engine (SWT in case of Eclipse, Swing in IntelliJ and Shell) on how to ask for parameters for a specific command. In Shell, we can do that by prompting the user for each necessary parameter (unless it is explicitly set). In an UI, they would be probably be rendered as text fields. What we need is a domain model that fit in this proposal and also allowing some extra features, like input validation, mutually exclusive command options (as described in FORGE-297). As typesafe, I meant to allow the use of a Javabean to store the input for a specific parameter or group of parameters. > Design an user interface API for addons > --------------------------------------- > > Key: FORGE-719 > URL: https://issues.jboss.org/browse/FORGE-719 > Project: Forge > Issue Type: Story > Components: Brainstorming > Reporter: George Gastaldi > Fix For: 2.0.0.Alpha1 > > > Requirements: > - It must be usable in a Shell UI > - It should be usable in a Visual UI (SWT, Swing) > - It must be typesafe, therefore allowing the use of complex types. > Let's use this JIRA to brainstorm about it. -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-719) Design an user interface API for addons

by Luca Masini (JIRA)

[ https://issues.jboss.org/browse/FORGE-719?page=com.atlassian.jira.plugin.... ] Luca Masini commented on FORGE-719: ----------------------------------- Can you please elaborate it more ??? I would like to understand your thinking. > Design an user interface API for addons > --------------------------------------- > > Key: FORGE-719 > URL: https://issues.jboss.org/browse/FORGE-719 > Project: Forge > Issue Type: Story > Components: Brainstorming > Reporter: George Gastaldi > Fix For: 2.0.0.Alpha1 > > > Requirements: > - It must be usable in a Shell UI > - It should be usable in a Visual UI (SWT, Swing) > - It must be typesafe, therefore allowing the use of complex types. > Let's use this JIRA to brainstorm about it. -- 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

13 years, 4 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues December 2012