April 2013 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-193) Validate plugin @Alias, @Command, and @Option names to ensure no duplicates occur

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-193?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-193: ---------------------------------- Fix Version/s: 2.0.0.Alpha4 (was: 2.0.0.Alpha3) > Validate plugin @Alias, @Command, and @Option names to ensure no duplicates occur > --------------------------------------------------------------------------------- > > Key: FORGE-193 > URL: https://issues.jboss.org/browse/FORGE-193 > Project: Forge > Issue Type: Feature Request > Components: Plugin API, UI - Shell > Affects Versions: 1.0.0.Alpha3 > Reporter: Lincoln Baxter III > Fix For: 2.0.0.Alpha4 > > > Should be invalid for same resource scopes > @Alias("whee") > @Alias("whee") > Should be invalid in same command: > @Option(name="named") > @Option(name="named") > And so on... > Or, it should be possible to reference by Fully Qualified Name if this situation does arise (for @Alias.) -- 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

12 years, 12 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.Alpha4 (was: 2.0.0.Alpha3) > 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.Alpha4 > > > 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

12 years, 12 months

1
0
0 / 0

[JBoss JIRA] (FORGE-186) Allow decoration/interception of Plugin output

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-186?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-186: ---------------------------------- Fix Version/s: 2.0.0.Alpha4 (was: 2.0.0.Alpha3) > Allow decoration/interception of Plugin output > ---------------------------------------------- > > Key: FORGE-186 > URL: https://issues.jboss.org/browse/FORGE-186 > Project: Forge > Issue Type: Feature Request > Components: Plugin API, Usability > Affects Versions: 1.0.6.Final > Reporter: Jonathan Fuerth > Priority: Minor > Fix For: 2.0.0.Alpha4 > > > The Java syntax highlighting in cat & less output is wonderful. As much as we all (don't) love XML, there's still a lot of it to deal with in Java EE projects. Syntax highlighting can help. > Allowing decoration of plugin output would be a major win for extensibility and modularity here. Allowing individual plugins to separate concerns based on runtime conditions. (E.g, what type of resource is in scope.) -- 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

12 years, 12 months

1
0
0 / 0

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

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-269?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-269: ---------------------------------- Fix Version/s: 2.0.0.Alpha4 (was: 2.0.0.Alpha3) > 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.Alpha4 > > > - 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

12 years, 12 months

1
0
0 / 0

[JBoss JIRA] (FORGE-212) Classload dependencies of current project when performing certain operations

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-212?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-212: ---------------------------------- Fix Version/s: 2.0.0.Alpha4 (was: 2.0.0.Alpha3) > Classload dependencies of current project when performing certain operations > ----------------------------------------------------------------------------- > > Key: FORGE-212 > URL: https://issues.jboss.org/browse/FORGE-212 > Project: Forge > Issue Type: Feature Request > Components: Maven Integration, Parsers / File Manipulation, Plugin API > Affects Versions: 1.0.0.Alpha3 > Reporter: wiktorowski maximilien > Priority: Minor > Fix For: 2.0.0.Alpha4 > > > "Generating crud views for entities located into an external jar is a use case i'd like to see implemented in forge. > In my case i have a model.jar containing my entities and an admin.war generated with seam forge. I'd like to use from-entity to generate scaffolding views in admin.war for the entities located in model.jar" > This means that Forge will need to classload dependencies of the target project in order to perform reflection-based generation. This may also require a reflection-based meta-model such as what was done with Errai/GWT. -- 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

12 years, 12 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.Alpha4 (was: 2.0.0.Alpha3) > 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.Alpha4 > > 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

12 years, 12 months

1
0
0 / 0

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

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-378?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-378: ---------------------------------- Fix Version/s: 2.0.0.Alpha4 (was: 2.0.0.Alpha3) > 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: UI - Shell, Usability > Reporter: Pete Muir > Fix For: 2.0.0.Alpha4 > > > 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

12 years, 12 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.Alpha4 (was: 2.0.0.Alpha3) > 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.Alpha4 > > > 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

12 years, 12 months

1
0
0 / 0

[JBoss JIRA] (FORGE-510) Create automated routine for checking plugin version compliance of plugins in Central Plugin Index

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-510?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-510: ---------------------------------- Fix Version/s: 2.0.0.Alpha4 (was: 2.0.0.Alpha3) > Create automated routine for checking plugin version compliance of plugins in Central Plugin Index > -------------------------------------------------------------------------------------------------- > > Key: FORGE-510 > URL: https://issues.jboss.org/browse/FORGE-510 > Project: Forge > Issue Type: Task > Components: Plugin Repository > Affects Versions: 1.0.6.Final > Reporter: Ivan St. Ivanov > Fix For: 2.0.0.Alpha4 > > > Create a routine, executed by the build server, that checks a predefined set of Forge plugins for version consistency with Forge core. In order to satisfy this check, for each major version of the core there should be at least one plugin branch or tag that specifies the same major version. If the check fails, the plugin author should receive an email asking them to fix the inconcistency. -- 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

12 years, 12 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.Alpha4 (was: 2.0.0.Alpha3) > 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.Alpha4 > > > 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

12 years, 12 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues April 2013