July 2013 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-1001) Duplicate local variables are created in the View beans of the generated Faces scaffold

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-1001?page=com.atlassian.jira.plugin... ] Vineet Reynolds closed FORGE-1001. ---------------------------------- Fix Version/s: 1.3.3.Final Resolution: Done Pushed upstream: https://github.com/forge/core/commit/cfc6f49ff8729fdc6ebac5d2827351368cb9... > Duplicate local variables are created in the View beans of the generated Faces scaffold > --------------------------------------------------------------------------------------- > > Key: FORGE-1001 > URL: https://issues.jboss.org/browse/FORGE-1001 > Project: Forge > Issue Type: Bug > Components: Scaffold > Affects Versions: 1.3.2.Final > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > Fix For: 1.3.3.Final > > > Local variables generated in the {{delete()}} method containing the deletion logic are named after the types of the properties. Multiple properties of the same type or parameterized type can exist in the JPA entity. > This was noticed in the JPA entities generated from the [Sakila-H2 model|https://github.com/maxandersen/sakila-h2]. > A better naming convention needs to be used to prevent naming conflicts and eventually syntax errors in the generated scaffold. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-873) Scaffold doesn't shows the correct referenced entities in edit views, while in details views shows something like "org.forgetest.model.Entity@5f9ba38e"

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-873?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-873: ---------------------------------- Fix Version/s: 1.3.4.Final (was: 1.3.3.Final) > Scaffold doesn't shows the correct referenced entities in edit views, while in details views shows something like "org.forgetest.model.Entity@5f9ba38e" > ------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: FORGE-873 > URL: https://issues.jboss.org/browse/FORGE-873 > Project: Forge > Issue Type: Bug > Components: Scaffold > Affects Versions: 1.2.3.Final > Environment: JBoss 7.1.1 final , Hibernate 4.2.0.final, > Reporter: claudio perrotta > Assignee: Vineet Reynolds > Fix For: 1.3.4.Final > > > For a table with a foreign key the UI permits to select the possible values, but this values are listed in a dropdown menu in a form like "org.forgetest.model.Entity@5f9ba38e" (would be preferable that the string present be relative to the PK referenced) > Anyway, after setting this field and submitting the form, the data are inserted in the table correctly but when i want to modify the record, the UI doesn't show the setted value for the foreign key and i must set it again before saving. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-926) It should be : maxlength instead of maxLength

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-926?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-926: ---------------------------------- Fix Version/s: 1.3.4.Final (was: 1.3.3.Final) > It should be : maxlength instead of maxLength > --------------------------------------------- > > Key: FORGE-926 > URL: https://issues.jboss.org/browse/FORGE-926 > Project: Forge > Issue Type: Bug > Components: Scaffold > Affects Versions: 1.2.0.Final, 1.2.1.Final, 1.2.2.Final, 1.3.0.Final > Environment: Any > Reporter: Hanine Hanynowsky > Assignee: Vineet Reynolds > Priority: Minor > Fix For: 1.3.4.Final > > > The JBoss Forge UI scaffold uses maxLength as the attribute name instead of maxlength, when generating <h:inpuText /> components, in .xhtml files. > So this is a typo error (capital L instead of a lowercase l). > People using Eclipse or JBoss developer might notice it since, these IDEs do not complain about it. If you use Netbeans or IntelliJidea, you would be prompted to correct the error. > This has no critical consequences so far, but should be changed to correct name. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-973) Upgrade Metawidget to 3.4

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-973?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-973: ---------------------------------- Fix Version/s: 1.3.4.Final (was: 1.3.3.Final) > Upgrade Metawidget to 3.4 > ------------------------- > > Key: FORGE-973 > URL: https://issues.jboss.org/browse/FORGE-973 > Project: Forge > Issue Type: Component Upgrade > Components: Scaffold > Affects Versions: 1.3.1.Final > Reporter: George Gastaldi > Assignee: Vineet Reynolds > Fix For: 1.3.4.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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-980) Failed retrieving forge modules (ClassNotFoundException: org.jboss.forge.maven.plugins.Configuration)

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-980?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III closed FORGE-980. ------------------------------------ (Issue closed notes: Thank you for the excellent analysis and workaround!) > Failed retrieving forge modules (ClassNotFoundException: org.jboss.forge.maven.plugins.Configuration) > ----------------------------------------------------------------------------------------------------- > > Key: FORGE-980 > URL: https://issues.jboss.org/browse/FORGE-980 > Project: Forge > Issue Type: Bug > Reporter: Lennart Jörelid > Assignee: Lennart Jörelid > Labels: documentation > Attachments: jbossForgeClassLoadingDebugging_1_incorrectRejectionMaybe.png, jbossForgeClassLoadingDebugging_2_okModuleClassLoader.png, jbossForgePlugin.txt > > > https://community.jboss.org/message/825612 > Following a successful build, including unit tests for the Forge plugin, the installation (forge source-install . ) fails with a ClassNotFoundException: org.jboss.forge.maven.plugins.Configuration within the ~/.forge/runtime.log. > This class is located in forge-maven-api, which should be available for all plugins being installed. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-980) Failed retrieving forge modules (ClassNotFoundException: org.jboss.forge.maven.plugins.Configuration)

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-980?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III commented on FORGE-980: ------------------------------------------ Hmmm... You mean transitive as in provided scope? Or transitive as in nested dependencies at compile scope aren't included? The latter would seem like a bug, but... given the work happening on Forge 2, I'm not sure how far down this road we want to go for Forge 1x since it rarely comes up. > Failed retrieving forge modules (ClassNotFoundException: org.jboss.forge.maven.plugins.Configuration) > ----------------------------------------------------------------------------------------------------- > > Key: FORGE-980 > URL: https://issues.jboss.org/browse/FORGE-980 > Project: Forge > Issue Type: Bug > Reporter: Lennart Jörelid > Assignee: Lennart Jörelid > Labels: documentation > Attachments: jbossForgeClassLoadingDebugging_1_incorrectRejectionMaybe.png, jbossForgeClassLoadingDebugging_2_okModuleClassLoader.png, jbossForgePlugin.txt > > > https://community.jboss.org/message/825612 > Following a successful build, including unit tests for the Forge plugin, the installation (forge source-install . ) fails with a ClassNotFoundException: org.jboss.forge.maven.plugins.Configuration within the ~/.forge/runtime.log. > This class is located in forge-maven-api, which should be available for all plugins being installed. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-873) Scaffold doesn't shows the correct referenced entities in edit views, while in details views shows something like "org.forgetest.model.Entity@5f9ba38e"

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-873?page=com.atlassian.jira.plugin.... ] Vineet Reynolds reopened FORGE-873: ----------------------------------- Reopening this issue. There's a possibly a better way to display the labels depending on toString() being declared or not in the Entity class. > Scaffold doesn't shows the correct referenced entities in edit views, while in details views shows something like "org.forgetest.model.Entity@5f9ba38e" > ------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: FORGE-873 > URL: https://issues.jboss.org/browse/FORGE-873 > Project: Forge > Issue Type: Bug > Components: Scaffold > Affects Versions: 1.2.3.Final > Environment: JBoss 7.1.1 final , Hibernate 4.2.0.final, > Reporter: claudio perrotta > Assignee: Vineet Reynolds > Fix For: 1.3.3.Final > > > For a table with a foreign key the UI permits to select the possible values, but this values are listed in a dropdown menu in a form like "org.forgetest.model.Entity@5f9ba38e" (would be preferable that the string present be relative to the PK referenced) > Anyway, after setting this field and submitting the form, the data are inserted in the table correctly but when i want to modify the record, the UI doesn't show the setted value for the foreign key and i must set it again before saving. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1011) Forge Plugin Classloaders should find plugin depedencies (including Transitives)

by Lennart Jörelid (JIRA)

[ https://issues.jboss.org/browse/FORGE-1011?page=com.atlassian.jira.plugin... ] Lennart Jörelid updated FORGE-1011: ----------------------------------- Component/s: Builtin Plugins > Forge Plugin Classloaders should find plugin depedencies (including Transitives) > --------------------------------------------------------------------------------- > > Key: FORGE-1011 > URL: https://issues.jboss.org/browse/FORGE-1011 > Project: Forge > Issue Type: Bug > Components: Builtin Plugins, Plugin API > Affects Versions: 1.3.2.Final > Reporter: Lennart Jörelid > > Can a sufficient solution imply that the NativeLibraryResourceLoader which handles the dependencies of the Forge Plugin have its pathFilter set to ACCEPT instead of REJECT? (Please refer to screenshot in the FORGE-980 issue). -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1011) Forge Plugin Classloaders should find plugin depedencies (including Transitives)

by Lennart Jörelid (JIRA)

[ https://issues.jboss.org/browse/FORGE-1011?page=com.atlassian.jira.plugin... ] Lennart Jörelid updated FORGE-1011: ----------------------------------- Description: Can a sufficient solution imply that the NativeLibraryResourceLoader which handles the dependencies of the Forge Plugin have its pathFilter set to ACCEPT instead of REJECT? (Please refer to screenshot in the FORGE-980 issue). > Forge Plugin Classloaders should find plugin depedencies (including Transitives) > --------------------------------------------------------------------------------- > > Key: FORGE-1011 > URL: https://issues.jboss.org/browse/FORGE-1011 > Project: Forge > Issue Type: Bug > Components: Plugin API > Affects Versions: 1.3.2.Final > Reporter: Lennart Jörelid > > Can a sufficient solution imply that the NativeLibraryResourceLoader which handles the dependencies of the Forge Plugin have its pathFilter set to ACCEPT instead of REJECT? (Please refer to screenshot in the FORGE-980 issue). -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1001) Duplicate local variables are created in the View beans of the generated Faces scaffold

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-1001?page=com.atlassian.jira.plugin... ] Vineet Reynolds reassigned FORGE-1001: -------------------------------------- Assignee: Vineet Reynolds > Duplicate local variables are created in the View beans of the generated Faces scaffold > --------------------------------------------------------------------------------------- > > Key: FORGE-1001 > URL: https://issues.jboss.org/browse/FORGE-1001 > Project: Forge > Issue Type: Bug > Components: Scaffold > Affects Versions: 1.3.2.Final > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > > Local variables generated in the {{delete()}} method containing the deletion logic are named after the types of the properties. Multiple properties of the same type or parameterized type can exist in the JPA entity. > This was noticed in the JPA entities generated from the [Sakila-H2 model|https://github.com/maxandersen/sakila-h2]. > A better naming convention needs to be used to prevent naming conflicts and eventually syntax errors in the generated scaffold. -- 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, 8 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues July 2013