February 2013 - forge-issues - Jboss List Archives

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

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-297?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III updated FORGE-297: ------------------------------------- Fix Version/s: 2.0.0.Alpha2 (was: 2.0.0.Alpha1) > 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.Alpha2 > > > 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, 3 months

1
0
0 / 0

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

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-255?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III updated FORGE-255: ------------------------------------- Fix Version/s: 2.0.0.Alpha2 (was: 2.0.0.Alpha1) > 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.Alpha2 > > -- 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, 3 months

1
0
0 / 0

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

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-331?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III updated FORGE-331: ------------------------------------- Fix Version/s: 2.0.0.Alpha2 (was: 2.0.0.Alpha1) > 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.Alpha2 > > > 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, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-368) Return list of properties based on higher-level understanding

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-368?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III updated FORGE-368: ------------------------------------- Fix Version/s: 2.0.0.Alpha2 (was: 2.0.0.Alpha1) > Return list of properties based on higher-level understanding > ------------------------------------------------------------- > > Key: FORGE-368 > URL: https://issues.jboss.org/browse/FORGE-368 > Project: Forge > Issue Type: Feature Request > Components: Parsers / File Manipulation > Reporter: Richard Kennard > Fix For: 2.0.0.Alpha2 > > > Hi guys, > As I understand it, Forge has an understanding of your project that transcends Java's own understanding. So for example if I say... > field string --named foo > ...Forge knows I'm creating a property, and it creates getters and setters for that property. But later if I do... > org.jboss.forge.parser.java.JavaClass.getMethods() > ...then I get back just normal methods. I'll have to check their signature for 'get' or 'set' to see if they're properties. Equally if I do... > org.jboss.forge.parser.java.JavaClass.getFields() > ...I get back just normal fields. I don't know if these are property fields (and if so, what their corresponding getter/setter methods are) or whether they're just internal fields (and should be ignored). > Is there a recommended way to 'get back out' the list of properties for a class? Something that tells me a) the field; b) the getter; c) the setter? > If it helps, for now I am using a rough implementation at: https://github.com/kennardconsulting/forge/blob/master/scaffold-metawidge... -- 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, 3 months

1
0
0 / 0

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

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-253?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III updated FORGE-253: ------------------------------------- Fix Version/s: 2.0.0.Alpha2 (was: 2.0.0.Alpha1) > 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.Alpha2 > > > 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, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-240) Provide ability to reference project settings through EL in Default @Option params:

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-240?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III updated FORGE-240: ------------------------------------- Fix Version/s: 2.0.0.Alpha2 (was: 2.0.0.Alpha1) > Provide ability to reference project settings through EL in Default @Option params: > ------------------------------------------------------------------------------------ > > Key: FORGE-240 > URL: https://issues.jboss.org/browse/FORGE-240 > Project: Forge > Issue Type: Feature Request > Components: Plugin API > Affects Versions: 1.0.0.Alpha2 > Reporter: Lincoln Baxter III > Fix For: 2.0.0.Alpha2 > > > @Option(default="org.${project.name}") String defaultPackage -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-378) Add "environments" as a first class construct

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-378?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III updated FORGE-378: ------------------------------------- Fix Version/s: 2.0.0.Alpha2 (was: 2.0.0.Alpha1) > Add "environments" as a first class construct > --------------------------------------------- > > Key: FORGE-378 > URL: https://issues.jboss.org/browse/FORGE-378 > Project: Forge > Issue Type: Feature Request > Components: Shell, Usability > Reporter: Pete Muir > Fix For: 2.0.0.Alpha2 > > > For example: > {code} > set environment JBOSS_AS7 --version 7.1.0.Final > {code} > Where JBOSS_AS7 is a built in profile that contains necessary info on various versions of JBoss AS 7. > For example, the persistence plugin could read from this, changing > {code} > persistence setup --provider HIBERNATE --container JBOSS_AS7 > {code} > to > {code} > persistence setup > {code} > Or, when setting up CDI, this would remove the need to ask ask which API to use (always use the Java EE BOM with JBoss AS), and as the metadata builds, remove the need to ask the version of the spec BOM to use. > Lot's of other places where this could provide better defaulting, or remove the need to ask questions. > This also seems fairly consistent with the Forge approach - good understanding of the project in question. -- 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, 3 months

1
0
0 / 0

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

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-273?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III updated FORGE-273: ------------------------------------- Fix Version/s: 2.0.0.Alpha2 (was: 2.0.0.Alpha1) > 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.Alpha2 > > > 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, 3 months

1
0
0 / 0

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

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-309?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III updated FORGE-309: ------------------------------------- Fix Version/s: 2.0.0.Alpha2 (was: 2.0.0.Alpha1) > 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: Shell > Reporter: Richard Kennard > Priority: Minor > Fix For: 2.0.0.Alpha2 > > > 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, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-269) Respecting file locking in IDE

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-269?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III updated FORGE-269: ------------------------------------- Fix Version/s: 2.0.0.Alpha2 (was: 2.0.0.Alpha1) > Respecting file locking in IDE > ------------------------------ > > Key: FORGE-269 > URL: https://issues.jboss.org/browse/FORGE-269 > Project: Forge > Issue Type: Feature Request > Components: Resources API > Reporter: Koen Aers > Fix For: 2.0.0.Alpha2 > > > - Forge needs to fire events requesting the files/folders to lock > - Forge can lock files as it reads/writes them (on demand) > - If deadlock potential arises, forge could prompt the user to continue anyway, at which point the plugin continues > - in the future, forge could provide a diff to eclipse after performing the operations on the side > see: http://transcripts.jboss.org/meeting/irc.freenode.org/forge/2011/forge.20... -- 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, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues February 2013