April 2013 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-192) Make Forge console i18n and L10n compatible

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-192?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-192: ---------------------------------- Fix Version/s: 2.0.0.Alpha3 (was: 2.0.0.Alpha2) > Make Forge console i18n and L10n compatible > ------------------------------------------- > > Key: FORGE-192 > URL: https://issues.jboss.org/browse/FORGE-192 > Project: Forge > Issue Type: Feature Request > Components: Brainstorming, UI - Shell > Affects Versions: 1.0.6.Final > Reporter: George Gastaldi > Fix For: 2.0.0.Alpha3 > > > Forge should allow different languages to be used, so that the help messages and commands could be typed on the native speaker developer language. > Example: When a Brazilian Portuguese developer is creating a new project, he would type: "novo-projeto" instead of "new-project". -- 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

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-184) Add 'plugins register-plugin', 'update-registration' style commands for updating the central plugin repository index

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-184?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-184: ---------------------------------- Fix Version/s: 2.0.0.Alpha3 (was: 2.0.0.Alpha2) > Add 'plugins register-plugin', 'update-registration' style commands for updating the central plugin repository index > -------------------------------------------------------------------------------------------------------------------- > > Key: FORGE-184 > URL: https://issues.jboss.org/browse/FORGE-184 > Project: Forge > Issue Type: Feature Request > Components: Brainstorming, Builtin Plugins, Plugin Repository > Affects Versions: 1.0.0.Alpha4 > Reporter: Lincoln Baxter III > Fix For: 2.0.0.Alpha3 > > > Forge should provide commands to simplify the process of registering a plugin with the central repository. > The command should verify all metadata by attempting to build/install the plugin before allowing an update request to be sent. -- 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

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-85) Shell cannot parse command values containing '!' exclaimation points

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-85?page=com.atlassian.jira.plugin.s... ] George Gastaldi updated FORGE-85: --------------------------------- Fix Version/s: 2.0.0.Alpha3 (was: 2.0.0.Alpha2) > Shell cannot parse command values containing '!' exclaimation points > -------------------------------------------------------------------- > > Key: FORGE-85 > URL: https://issues.jboss.org/browse/FORGE-85 > Project: Forge > Issue Type: Bug > Components: UI - Shell > Affects Versions: 1.0.0.Beta2 > Reporter: Lincoln Baxter III > Labels: HackNight > Fix For: 2.0.0.Alpha3 > > Attachments: Forge-85.patch > > > {code} > [pfdemo] pfdemo $ echo sdfdf! > sdfdf ! > [pfdemo] pfdemo $ echo sdfdf!sdf > ***ERROR*** Exception encountered: !sdf: event not found (type "set VERBOSE true" to enable stack traces) > [pfdemo] pfdemo $ > [pfdemo] pfdemo $ echo 'asdf!asdf` > ***ERROR*** Exception encountered: !asdf`: event not found (type "set VERBOSE true" to enable stack traces) > [pfdemo] pfdemo $ > {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

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-238) Log forge commands run against a project

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-238?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-238: ---------------------------------- Fix Version/s: 2.0.0.Alpha3 (was: 2.0.0.Alpha2) > Log forge commands run against a project > ---------------------------------------- > > Key: FORGE-238 > URL: https://issues.jboss.org/browse/FORGE-238 > Project: Forge > Issue Type: Feature Request > Components: Usability > Reporter: Brian Leathem > Fix For: 2.0.0.Alpha3 > > > ou should have forge create a log file in a project, of all the forge commands you ran in that project. > maybe even script style, so you can play it back. -- 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

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-273) Create project from Maven archetype

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-273?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-273: ---------------------------------- Fix Version/s: 2.0.0.Alpha3 (was: 2.0.0.Alpha2) > Create project from Maven archetype > ----------------------------------- > > Key: FORGE-273 > URL: https://issues.jboss.org/browse/FORGE-273 > Project: Forge > Issue Type: Feature Request > Components: Blessed Plugins > Reporter: Dan Allen > Assignee: Rodney Russ > Priority: Minor > Fix For: 2.0.0.Alpha3 > > > Since the catalog of Maven archetypes is substantial, and the archetype plugin interface is so abysmal, Forge could benefit from being a stand-in replacement to archetype:generate. A command in Forge to create a new project from a Maven archetype would certainly offer a nice complement to the more basic "new-project" command. It could just be an additional flag to the new-project command, such as: > new-project --named MyProject --fromArchetype org.jboss.weld.archetypes:jboss-javaee6-webapp > Using the interactive prompts, you may be able to provide a list of archetypes, perhaps w/ a filtering mechanism. You could also just do a best guess based on what's found in the catalog. > new-project --named MyProject --fromArchetype jboss-javaee6-webapp > You could just delegate to Maven by building up the "mvn archetype:generate" command from Forge. Long term we could consider emulating the archetype:generate plugin so as just to consume the projects that are out there already w/o any linkage to Maven. -- 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

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-331) Get online help from plugin's javadoc

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-331?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-331: ---------------------------------- Fix Version/s: 2.0.0.Alpha3 (was: 2.0.0.Alpha2) > Get online help from plugin's javadoc > ------------------------------------- > > Key: FORGE-331 > URL: https://issues.jboss.org/browse/FORGE-331 > Project: Forge > Issue Type: Feature Request > Components: Plugin API > Reporter: Jonathan Fuerth > Priority: Minor > Fix For: 2.0.0.Alpha3 > > > IDEs already have lots of great tooling to help write good javadoc and keep it neatly formatted and up to date. It would be excellent if forge's source of help text for plugins came straight from the javadoc. This could be done either via a doclet that operates on the Java source code, or by scraping the output of the default doclet (like Eclipse will do if you attach generated JavaDoc rather than library source code). > Lowering the barrier to providing high-quality documentation should help encourage plugin authors to provide good help, and in turn that should help everyone pick up and learn Forge faster. -- 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

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-309) Support multi-line paste (accepting defaults as you go)

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-309?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-309: ---------------------------------- Fix Version/s: 2.0.0.Alpha3 (was: 2.0.0.Alpha2) > Support multi-line paste (accepting defaults as you go) > ------------------------------------------------------- > > Key: FORGE-309 > URL: https://issues.jboss.org/browse/FORGE-309 > Project: Forge > Issue Type: Feature Request > Components: UI - Shell > Reporter: Richard Kennard > Priority: Minor > Fix For: 2.0.0.Alpha3 > > > Given that one of Forge's strengths is to create entire projects with just a few commands, it may be a useful learning tool to be able to cut/paste those commands from somebody's blog directly into Forge. For example I could highlight a couple dozen lines from... > http://kennardconsulting.blogspot.com/2011/04/grokking-seam-forge-part-3.... > ...and paste them, and Forge would execute them all. It would need to recognize carriage returns as command separators, and to somehow accept defaults, but it'd be neat for bloggers to be able to say 'here, paste this into Seam Forge'. > Just an idea. > Richard. -- 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

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-255) Add getSupportedPackagingTypes() to PackagingFacet to allow build tools to specity supported packaging types

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-255?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-255: ---------------------------------- Fix Version/s: 2.0.0.Alpha3 (was: 2.0.0.Alpha2) > Add getSupportedPackagingTypes() to PackagingFacet to allow build tools to specity supported packaging types > ------------------------------------------------------------------------------------------------------------ > > Key: FORGE-255 > URL: https://issues.jboss.org/browse/FORGE-255 > Project: Forge > Issue Type: Feature Request > Components: Plugin API > Affects Versions: 1.0.0.Beta2 > Reporter: Lincoln Baxter III > Priority: Minor > Labels: starter > Fix For: 2.0.0.Alpha3 > > -- 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

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-297) Should provide ability to specify mutually exclusive command options

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-297?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-297: ---------------------------------- Fix Version/s: 2.0.0.Alpha3 (was: 2.0.0.Alpha2) > Should provide ability to specify mutually exclusive command options > -------------------------------------------------------------------- > > Key: FORGE-297 > URL: https://issues.jboss.org/browse/FORGE-297 > Project: Forge > Issue Type: Feature Request > Components: Plugin API > Affects Versions: 1.0.0.Alpha1 > Reporter: Lincoln Baxter III > Priority: Minor > Fix For: 2.0.0.Alpha3 > > > When developing Plugin @Commands, it is sometimes convenient to specify options from which only one must be selected > For example: > * providing a maven GAV "org.jboss.seam.forge:forge-parent:1.0.0" > * specifying the path to said project "~/projects/forge/" > Both inputs are valid, but only one is required. If one is selected, the other should be hidden from completion. (Or some such interaction.) > If both are missing, Forge should prompt for one to be completed. -- 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

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-253) Forge should provide development profiles API for datasources and other configs

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-253?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-253: ---------------------------------- Fix Version/s: 2.0.0.Alpha3 (was: 2.0.0.Alpha2) > Forge should provide development profiles API for datasources and other configs > ------------------------------------------------------------------------------- > > Key: FORGE-253 > URL: https://issues.jboss.org/browse/FORGE-253 > Project: Forge > Issue Type: Feature Request > Components: Plugin API > Affects Versions: 1.0.0.Alpha3 > Reporter: Lincoln Baxter III > Fix For: 2.0.0.Alpha3 > > > lincolnthree > It gives you what is in persistence.xml > 11:22 > maxandersen > it wasn't there a jbossworld > 11:22 > lincolnthree > that's been there from the beginning > 11:22 > maxandersen > yes - persistence.xml says datasources > nothing about the actual connection info > 11:23 > lincolnthree > oh right > well > connection info is stored on the server > forge doesn't know that > unless it's in the persistence.xml > 11:23 > maxandersen > lincolnthree: exaactly - but it has to know that eventually. > 11:23 > lincolnthree > as properties > 11:23 > maxandersen > lincolnthree: it wont be > lincolnthree: this is why tools like rails, hibernate tools and others have notion of "profiles" or simply just property overrides for use at design time and for use at runtime -- 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

11 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues April 2013