February 2013 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-360) FacesPlugin should automatically add the faces mapping if the servlet version < 3

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-360?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-360: ---------------------------------- Fix Version/s: 1.2.2.Final (was: 1.2.1.Final) > FacesPlugin should automatically add the faces mapping if the servlet version < 3 > --------------------------------------------------------------------------------- > > Key: FORGE-360 > URL: https://issues.jboss.org/browse/FORGE-360 > Project: Forge > Issue Type: Enhancement > Components: Builtin Plugins > Affects Versions: 1.0.0.Beta3 > Reporter: Brian Leathem > Labels: HackNight, Starter > Fix For: 1.2.2.Final > > -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-340) Change default plugin checkout location to use the .forge/plugins-sources directory

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-340?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-340: ---------------------------------- Fix Version/s: 1.2.2.Final (was: 1.2.1.Final) > Change default plugin checkout location to use the .forge/plugins-sources directory > ----------------------------------------------------------------------------------- > > Key: FORGE-340 > URL: https://issues.jboss.org/browse/FORGE-340 > Project: Forge > Issue Type: Task > Components: Shell > Affects Versions: 1.0.0.Alpha4 > Reporter: Lincoln Baxter III > Assignee: Rodney Russ > Priority: Minor > Labels: Starter > Fix For: 1.2.2.Final > > > {code}$ forge git-plugin git@github.com:repo/etc{code} > needs to use ~/.forge/plugins-sources/ instead of the /tmp directory - so that developers can hack on installed plugins more easily. > this code lives here: > https://github.com/forge/core/blob/master/shell/src/main/java/org/jboss/f... -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-471) JavaResource handling of files with nested classes is incorrect

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-471?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-471: ---------------------------------- Fix Version/s: 1.2.2.Final (was: 1.2.1.Final) > JavaResource handling of files with nested classes is incorrect > --------------------------------------------------------------- > > Key: FORGE-471 > URL: https://issues.jboss.org/browse/FORGE-471 > Project: Forge > Issue Type: Bug > Components: Parsers / File Manipulation, Resources API > Affects Versions: 1.0.6.Final > Reporter: Rudy De Busscher > Fix For: 1.2.2.Final > > > In the case you have following java source file > public class Test { > > private String mainProperty; > public void mainMethod() { > System.out.println("Hi"); > } > public static final class Nested { > private String innerProperty; > public void innerMethod() { > System.out.println("I'm inner"); > } > } > } > And running following statements > JavaResource javaResource = factory.getResourceFrom(new File"/path/to/file/Test.java")).reify(JavaResource.class); > System.out.println(javaResource.toString()); > List<Resource<?>> resources = javaResource.listResources(); > for (Resource res : resources) { > System.out.println(res.getFullyQualifiedName()); > } > You get following output > be.rubus.forge.deltaspike.test.projectstage.Nested > /path/to/file/Test.java/innerProperty::String > /path/to/file/Test.java/mainMethod()::void > /path/to/file/Test.java/innerMethod()::void > The wrong name is due to the fact that TypeDeclarationFinderVisitor records every class type the parser finds. In our case the 2 class names but only the last one is kept (first name is overwritten) > The MethodFinderVisitor has a similar problem, it gets called twice and adds up the found methods. > So there need to be a general review of the visitors to be able to handle nested or multiple classes in one java source file. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-463) Create Fedora package for Forge

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-463?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-463: ---------------------------------- Fix Version/s: 1.2.2.Final (was: 1.2.1.Final) > Create Fedora package for Forge > ------------------------------- > > Key: FORGE-463 > URL: https://issues.jboss.org/browse/FORGE-463 > Project: Forge > Issue Type: Feature Request > Components: Forge Build > Affects Versions: 1.1.0.Final > Reporter: Dan Allen > Priority: Optional > Fix For: 1.2.2.Final > > > This is an umbrella issue for creating a Fedora package for Forge. Track steps using additional issues. > Creating and publishing Forge packages for Fedora would really help boost adoption of Forge, IMO. Telling someone to download an unzip seems simple enough, but there's just something even more elegant about: > sudo yum install jboss-forge > (no sudo if you're hip enough, one of those GUIs if your glitzy enough) > I discovered that Fedora is trying to make package development easier than ever for Java developers. They've created a plugin for Eclipse [1] that walks you through creating a package, starting from git clone all the way to publish to Bodhi [2] (think of it like Nexus for Fedora, sort of). > This effort relates to, and my help drive, the JBoss AS 7 on Fedora initiative [3]. > [1] http://fedoraproject.org/wiki/Fedora_Packager_For_Eclipse_User_Guide > [2] http://fedoraproject.org/wiki/Bodhi > [3] http://fedoraproject.org/wiki/JBossAS7 -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-385) Current directory is poor default for new-project location when existing project is detected

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-385?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-385: ---------------------------------- Fix Version/s: 1.2.2.Final (was: 1.2.1.Final) > Current directory is poor default for new-project location when existing project is detected > -------------------------------------------------------------------------------------------- > > Key: FORGE-385 > URL: https://issues.jboss.org/browse/FORGE-385 > Project: Forge > Issue Type: Enhancement > Components: Builtin Plugins > Affects Versions: 1.0.0.Beta3 > Reporter: Dan Allen > Priority: Minor > Labels: Starter > Fix For: 1.2.2.Final > > > When creating a new project using the new-project command, forge will offer the current directory as the target location if a project with the same name is found. > {code} > $ new-project --named example --topLevelPackage org.example > ***ERROR*** [/home/dallen/example] already contains a project; please use a different folder. > Where would you like to create the project? [Press ENTER to use the current directory: dallen] > {code} > This default is a recipe for disaster. If there is a project in the way, then using the current directory puts that project *in* the project being created. Additionally, if the current directory is $HOME, then the project will get overlaid in a directory which has many other files and directories. > A better default is to append a number to the end of the project name. For example: > {code} > $ new-project --named example --topLevelPackage org.example > ***ERROR*** [/home/dallen/example] already contains a project; please use a different folder. > Where would you like to create the project? [Press ENTER to use an alternative directory: example2] > {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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-554) Tab AutoCompletion in forge ignores already typed options

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-554?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-554: ---------------------------------- Fix Version/s: 1.2.2.Final (was: 1.2.1.Final) > Tab AutoCompletion in forge ignores already typed options > --------------------------------------------------------- > > Key: FORGE-554 > URL: https://issues.jboss.org/browse/FORGE-554 > Project: Forge > Issue Type: Bug > Environment: Windows 7 64bits > Reporter: George Gastaldi > Fix For: 1.2.2.Final > > > Inside a project, when you "cd" and press <TAB> to navigate between nested folders, the prompt resets to "cd" only, losing the folders previously selected when typing. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-553) Forge Console does not display special characters

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-553?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-553: ---------------------------------- Fix Version/s: 1.2.2.Final (was: 1.2.1.Final) > Forge Console does not display special characters > ------------------------------------------------- > > Key: FORGE-553 > URL: https://issues.jboss.org/browse/FORGE-553 > Project: Forge > Issue Type: Bug > Reporter: George Gastaldi > Assignee: George Gastaldi > Labels: HackNight, annoying > Fix For: 1.2.2.Final > > > When you try typing accented characters, like áéíóú, they are erroneously displayed in Forge console. > There must be a way to set the encoding or leave as default -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-552) Escaping of selected characters doesn't work

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-552?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-552: ---------------------------------- Fix Version/s: 1.2.2.Final (was: 1.2.1.Final) > Escaping of selected characters doesn't work > -------------------------------------------- > > Key: FORGE-552 > URL: https://issues.jboss.org/browse/FORGE-552 > Project: Forge > Issue Type: Bug > Components: Forge Build > Affects Versions: 1.0.2.Final > Environment: Ubuntu 10.04 i686 > Reporter: Jevgeni Zelenkov > Fix For: 1.2.2.Final > > > This is related to the https://issues.jboss.org/browse/FORGE-43 issue. > The following characters in file names should be escaped by the forge completion: > \* ? = ' " { } \ $ ! & ; ( ) < > | > also: TAB-char (yes, I know it is stupid, but possible) > First two (*, ?) are used internally as wildcard chars, so should be allowed to be used escaped as well as unescaped. > = char doesn't need to be escaped neither on linux nor on windows but somehow forge fails to work with files containing = (at least on my ubuntu). > Windows has a slightly different set of chars to be escaped (from wikipedia, not actually tested): > ' " = & | ( ) < > ^ > This issue is added for completeness. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-524) Scaffolding an entity with enum uses a <f:selectItem> for each enum value

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-524?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-524: ---------------------------------- Fix Version/s: 1.2.2.Final (was: 1.2.1.Final) > Scaffolding an entity with enum uses a <f:selectItem> for each enum value > ------------------------------------------------------------------------- > > Key: FORGE-524 > URL: https://issues.jboss.org/browse/FORGE-524 > Project: Forge > Issue Type: Bug > Components: Scaffold > Affects Versions: 1.0.6.Final > Reporter: George Gastaldi > Fix For: 1.2.2.Final > > > When scaffolding an entity with a enumeration as an attribute (displaying it as a selectOneMenu), the enum values are placed directly inside the XHTML. > This is a bad thing, since when you modify the enumeration you MUST change the XHTML also. The scaffolding should use <f:selectItems> instead -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-576) Refactor RunUrlPluginTest

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-576?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-576: ---------------------------------- Fix Version/s: 1.2.2.Final (was: 1.2.1.Final) > Refactor RunUrlPluginTest > ------------------------- > > Key: FORGE-576 > URL: https://issues.jboss.org/browse/FORGE-576 > Project: Forge > Issue Type: Enhancement > Reporter: George Gastaldi > Fix For: 1.2.2.Final > > > org.jboss.forge.shell.test.plugins.builtin.RunUrlPluginTest should be refactored to boot up an embedded server and host a single file from it. The idea is to test it locally, though still using HTTP. -- 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, 3 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues February 2013