February 2014 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-1582) Support the creation of nested Java source types

by Matt Benson (JIRA)

Matt Benson created FORGE-1582: ---------------------------------- Summary: Support the creation of nested Java source types Key: FORGE-1582 URL: https://issues.jboss.org/browse/FORGE-1582 Project: Forge Issue Type: Feature Request Components: Parsers / File Manipulation Affects Versions: 2.x Future Reporter: Matt Benson -- 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

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1342) Move parser-java addon's org.jboss.forge.addon.parser.java.beans to java-parser

by Matt Benson (JIRA)

[ https://issues.jboss.org/browse/FORGE-1342?page=com.atlassian.jira.plugin... ] Matt Benson resolved FORGE-1342. -------------------------------- Fix Version/s: 2.0.0.CR1 (was: 2.x Future) Resolution: Done https://github.com/forge/roaster/commit/404f95220572cd70f39a7521f6f648f51... > Move parser-java addon's org.jboss.forge.addon.parser.java.beans to java-parser > ------------------------------------------------------------------------------- > > Key: FORGE-1342 > URL: https://issues.jboss.org/browse/FORGE-1342 > Project: Forge > Issue Type: Task > Components: Parsers / File Manipulation > Affects Versions: 2.0.0.Beta3 > Reporter: George Gastaldi > Assignee: Matt Benson > Fix For: 2.0.0.CR1 > > > The functionality in the org.jboss.forge.addon.parser.java.beans package in the parser-java addon API should be moved to the java-parser 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

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1548) Updated the Forge 2.0 plugin and now JBDS won't start

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/FORGE-1548?page=com.atlassian.jira.plugin... ] Koen Aers commented on FORGE-1548: ---------------------------------- Hey Robb, Can you describe the exact scenario? Forge 2 is by default not installed in JBDS, so I assume you first have installed it from a particular update site? Cheers, Koen > Updated the Forge 2.0 plugin and now JBDS won't start > ----------------------------------------------------- > > Key: FORGE-1548 > URL: https://issues.jboss.org/browse/FORGE-1548 > Project: Forge > Issue Type: Bug > Components: UI - Eclipse > Affects Versions: 2.0.0.CR2, 2.0.0.Final > Environment: JBDS 7.1 Macbook Pro Maverick OS. > Reporter: Robb Greathouse > Assignee: Koen Aers > > After checking for updates on JBDS I approved the update of the Forge 2 plugin. > JBDS asked to to be restarted. Upon restarting it gave a progress window announcing Forge 2 starting. After 10 minutes it had not started. -- 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

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1436) Implement 'help' command as a source of general guidance and flow control

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1436?page=com.atlassian.jira.plugin... ] Lincoln Baxter III updated FORGE-1436: -------------------------------------- Summary: Implement 'help' command as a source of general guidance and flow control (was: help command is missing) > Implement 'help' command as a source of general guidance and flow control > ------------------------------------------------------------------------- > > Key: FORGE-1436 > URL: https://issues.jboss.org/browse/FORGE-1436 > Project: Forge > Issue Type: Sub-task > Components: UI - Shell > Affects Versions: 2.0.0.Beta4 > Reporter: Antonio Goncalves > Fix For: 2.x Future > > > I find this one usefull and it could even add more content (such as mentioning the {{man}} command... > {code} > [no project] Forge $ help > Welcome to JBoss Forge, a next-generation interactive Shell and project-generation tool. If you find yourself lost, or uncertain how to complete an operation, you may press the <TAB> key for command-completion, or <TAB><TAB> for hints while typing a command. > Type 'list-commands' for a list of available commands in the current Resource context. > You are not working on a project. Type 'help new-project' to get started. > {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

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1479) Explicitly setup in Bean Validation, not in JPA

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1479?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-1479: ----------------------------------- Status: Closed (was: Pull Request Sent) Fix Version/s: 2.0.1.Final (was: 2.x Future) Resolution: Done > Explicitly setup in Bean Validation, not in JPA > ----------------------------------------------- > > Key: FORGE-1479 > URL: https://issues.jboss.org/browse/FORGE-1479 > Project: Forge > Issue Type: Sub-task > Components: UI - Shell > Affects Versions: 2.0.0.CR2 > Reporter: Antonio Goncalves > Assignee: George Gastaldi > Fix For: 2.0.1.Final > > > Just after a creating a project, a create a new entity without setting up the persistence ({{jpa-setup}}) : > {code} > ***SUCCESS*** Project named 'test' has been created. > [test]$ jpa-new-entity --named Author > [Author.java]$ jpa-new-field --named firstname --length 50 > ***SUCCESS*** Field firstname created > {code} > This hasn't created a {{persistence.xml}} file. But on the other hand, if I want to add a constraint on the entity, I need to explicitelly setup Bean Validation : > {code} > [Author.java]$ con > connection-profile-create connection-profile-remove constraint-setup > [Author.java]$ constraint-setup > ***SUCCESS*** Bean Validation is installed. > [Author.java]$ con > connection-profile-create connection-profile-remove constraint-add constraint-setup > [Author.java]$ constraint-add --constraint NotNull --onProperty firstname > ***SUCCESS*** Constraint NotNull successfully configured > {code} > if most of the information is giving at project creation, do we still need to explicitly setup Java EE components ? At the moment we have the following : > {code} > servlet-setup > ejb-setup > soap-setup > cdi-setup > jms-setup > rest-setup > jpa-setup > faces-setup > jstl-setup > jta-setup > constraint-setup > {code} > Most of these commands do not have parameters (except for persistence, rest, validation). So why not activate them by default (or only if {{export ACCEPT_DEFAULTS=true}} ) ? Something like : "if the command {{constraint-add}} is entered, Forge would go {{if constraint is not setup, then I invoke constraint-setup}}", "if the command {{ejb-new}} is entered, Forge would go {{if ejb is not setup, then I invoke ejb-setup}}" > That would save some bugs (developers forgetting to setup things), less typing and shorter scripts. -- 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

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1436) help command is missing

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1436?page=com.atlassian.jira.plugin... ] Lincoln Baxter III updated FORGE-1436: -------------------------------------- Fix Version/s: 2.x Future > help command is missing > ----------------------- > > Key: FORGE-1436 > URL: https://issues.jboss.org/browse/FORGE-1436 > Project: Forge > Issue Type: Sub-task > Components: UI - Shell > Affects Versions: 2.0.0.Beta4 > Reporter: Antonio Goncalves > Fix For: 2.x Future > > > I find this one usefull and it could even add more content (such as mentioning the {{man}} command... > {code} > [no project] Forge $ help > Welcome to JBoss Forge, a next-generation interactive Shell and project-generation tool. If you find yourself lost, or uncertain how to complete an operation, you may press the <TAB> key for command-completion, or <TAB><TAB> for hints while typing a command. > Type 'list-commands' for a list of available commands in the current Resource context. > You are not working on a project. Type 'help new-project' to get started. > {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

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1436) help command is missing

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1436?page=com.atlassian.jira.plugin... ] Lincoln Baxter III reopened FORGE-1436: --------------------------------------- I think we should reconsider this issue. Help is a pretty useful command and is easier to understand for those who are not already familiar with command line tools. Help should probably print context-sensitive tips just like it did in George's Forge 1 help plugin. > help command is missing > ----------------------- > > Key: FORGE-1436 > URL: https://issues.jboss.org/browse/FORGE-1436 > Project: Forge > Issue Type: Sub-task > Components: UI - Shell > Affects Versions: 2.0.0.Beta4 > Reporter: Antonio Goncalves > > I find this one usefull and it could even add more content (such as mentioning the {{man}} command... > {code} > [no project] Forge $ help > Welcome to JBoss Forge, a next-generation interactive Shell and project-generation tool. If you find yourself lost, or uncertain how to complete an operation, you may press the <TAB> key for command-completion, or <TAB><TAB> for hints while typing a command. > Type 'list-commands' for a list of available commands in the current Resource context. > You are not working on a project. Type 'help new-project' to get started. > {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

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1581) User configuration file should be configurable

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1581?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1581. ---------------------------------- Resolution: Done > User configuration file should be configurable > ---------------------------------------------- > > Key: FORGE-1581 > URL: https://issues.jboss.org/browse/FORGE-1581 > Project: Forge > Issue Type: Feature Request > Components: Builtin Plugins > Affects Versions: 2.0.0.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 2.0.1.Final > > > The user configuration file is fixed at ~/.forge/config.xml. Forge should use a system property to customize that. > Eg: > {{-Dorg.jboss.forge.addon.configuration.USER_CONFIG_PATH=/foo/config.xml}} -- 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

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1581) User configuration file should be configurable

by George Gastaldi (JIRA)

George Gastaldi created FORGE-1581: -------------------------------------- Summary: User configuration file should be configurable Key: FORGE-1581 URL: https://issues.jboss.org/browse/FORGE-1581 Project: Forge Issue Type: Feature Request Components: Builtin Plugins Affects Versions: 2.0.0.Final Reporter: George Gastaldi Assignee: George Gastaldi Fix For: 2.0.1.Final The user configuration file is fixed at ~/.forge/config.xml. Forge should use a system property to customize that. Eg: {{-Dorg.jboss.forge.addon.configuration.USER_CONFIG_PATH=/foo/config.xml}} -- 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

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1547) Adding debug information on JSF pages

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1547?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1547. ---------------------------------- Fix Version/s: 2.0.1.Final (was: 2.x Future) Resolution: Done > Adding debug information on JSF pages > ------------------------------------- > > Key: FORGE-1547 > URL: https://issues.jboss.org/browse/FORGE-1547 > Project: Forge > Issue Type: Enhancement > Components: Scaffold > Affects Versions: 2.0.0.Final > Reporter: Antonio Goncalves > Assignee: Antonio Goncalves > Labels: starter > Fix For: 2.0.1.Final > > > JSF pages are hard to debug, so adding a {{ui:debug}} in the main template. The idea (as explained on http://stackoverflow.com/questions/4049531/uidebug-tag-not-working-in-fac...) is to add a {{ui:debug}} and some config in web.xml so only the debugging shows up in development. > So in the {{pageTemplate.xhtml}} we would add : > {code} > <h:body> > <ui:debug rendered="#{initParam['javax.faces.FACELETS_DEVELOPMENT']}"/> > <div class="navbar navbar-fixed-top"> > {code} > And in the {{web.xml}} : > {code} > <context-param> > <param-name>javax.faces.FACELETS_DEVELOPMENT</param-name> > <param-value>true</param-value> > </context-param> > {code} > Then, once in any page, you just need to press CTRL+ SHIFT + D -- 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

10 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues February 2014