July 2013 - forge-issues - Jboss List Archives

[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 edited comment on FORGE-524 at 7/4/13 11:12 AM: ---------------------------------------------------------------- IMHO this is the best strategy: http://stackoverflow.com/a/8229982 was (Author: gastaldi): IMHO this is the best strategy: http://stackoverflow.com/a/2869011 > 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.x Future > > > 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-856) JSF scaffold from entity error with private get method

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-856?page=com.atlassian.jira.plugin.... ] Vineet Reynolds closed FORGE-856. --------------------------------- Fix Version/s: 1.3.3.Final (was: 1.x Future) Resolution: Done Pushed uptream: https://github.com/forge/core/commit/02a04ff4e8e8aa8788eef2c19a7f618606bd... Only public methods are considered for identifying getters and setters to build up metadata about metawidget properties. This makes sense since non-public members would impose constraints on the kind of code that would be generated to access properties if such properties exist (for e.g. EL expressions in this case). Moreover, if metawidget properties were to be treated as the equivalent of JavaBean properties, then public getters/setters are required, going by Section 8.3.1 of the JavaBeans specification. > JSF scaffold from entity error with private get method > ------------------------------------------------------ > > Key: FORGE-856 > URL: https://issues.jboss.org/browse/FORGE-856 > Project: Forge > Issue Type: Bug > Components: Scaffold > Affects Versions: 1.2.3.Final > Reporter: Jason Porter > Assignee: Vineet Reynolds > Fix For: 1.3.3.Final > > > Not sure if this is a bug in Forge or MetaWidget, but if you have a private method named get<whatever else> when the page is generated it thinks that's a getter and adds it to the page and the EL, which of course blows up. > You can see that in TicketMonster (up until commit 2b80ca6) in the SectionAllocation entity. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-856) JSF scaffold from entity error with private get method

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-856?page=com.atlassian.jira.plugin.... ] Vineet Reynolds reassigned FORGE-856: ------------------------------------- Assignee: Vineet Reynolds > JSF scaffold from entity error with private get method > ------------------------------------------------------ > > Key: FORGE-856 > URL: https://issues.jboss.org/browse/FORGE-856 > Project: Forge > Issue Type: Bug > Components: Scaffold > Affects Versions: 1.2.3.Final > Reporter: Jason Porter > Assignee: Vineet Reynolds > Fix For: 1.x Future > > > Not sure if this is a bug in Forge or MetaWidget, but if you have a private method named get<whatever else> when the page is generated it thinks that's a getter and adds it to the page and the EL, which of course blows up. > You can see that in TicketMonster (up until commit 2b80ca6) in the SectionAllocation entity. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-993) Support for multi project: So forge can understand the parent and child modules resource/source

by Rajmahendra Hegde (JIRA)

Rajmahendra Hegde created FORGE-993: --------------------------------------- Summary: Support for multi project: So forge can understand the parent and child modules resource/source Key: FORGE-993 URL: https://issues.jboss.org/browse/FORGE-993 Project: Forge Issue Type: Feature Request Components: Plugin API Affects Versions: 1.3.2.Final Reporter: Rajmahendra Hegde Assuming we have a maven project MyProj - (parent) MyProj-JPA MyProj-Web JPA contains JPA entities Web contains JSF Now user want to create a rest-services in Web or in a separate module say, MyProj-Rest. The current forge is working completely isolated without knowing the sub-modules of the current maven project. (or its not accessing the resource/source of the sub-project its currently running. Some time user want to create modular based development like above project structure. We need to provide a feature to access sub project resources/source also. So user can work in multi-project support environment to modularize his component. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-992) Create a Github hook for the Plugin/Addon repository

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-992?page=com.atlassian.jira.plugin.... ] George Gastaldi commented on FORGE-992: --------------------------------------- More info: https://help.github.com/articles/post-receive-hooks > Create a Github hook for the Plugin/Addon repository > ---------------------------------------------------- > > Key: FORGE-992 > URL: https://issues.jboss.org/browse/FORGE-992 > Project: Forge > Issue Type: Sub-task > Components: Plugin Repository > Reporter: George Gastaldi > Fix For: 2.x Future > > > This service should notify the Forge Addon repository application of any new releases to an addon/plugin -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-992) Create a Github hook for the Plugin/Addon repository

by George Gastaldi (JIRA)

George Gastaldi created FORGE-992: ------------------------------------- Summary: Create a Github hook for the Plugin/Addon repository Key: FORGE-992 URL: https://issues.jboss.org/browse/FORGE-992 Project: Forge Issue Type: Sub-task Components: Plugin Repository Reporter: George Gastaldi Fix For: 2.x Future This service should notify the Forge Addon repository application of any new releases to an addon/plugin -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-991) Create a plugin/addon repository application for Forge

by George Gastaldi (JIRA)

George Gastaldi created FORGE-991: ------------------------------------- Summary: Create a plugin/addon repository application for Forge Key: FORGE-991 URL: https://issues.jboss.org/browse/FORGE-991 Project: Forge Issue Type: Feature Request Components: Plugin Repository Reporter: George Gastaldi Fix For: 2.x Future >From [~dan.j.allen]: {quote} I know that Forge has a plugin repository, but there's always room for new ideas. The jQuery foundation recently rebooted their plugin registry to drive all contributions to it out of git. I thought you might be interested in reviewing how they set it up and see if any ideas might apply to Forge plugin registry, both in terms of how a plugin is registered and plugin discovery. Announcement: http://blog.jquery.com/2013/01/16/announcing-the-jquery-plugin-registry/ Plugin Registry: http://plugins.jquery.com/ GitHub repo: https://github.com/jquery/plugins.jquery.com As they put it: "The goal is to make sharing and browsing quality jQuery plugins a pleasant experience for everyone!" Replace jQuery w/ Forge and we have the same goal. {quote} {quote} Oh, and one more thing. I think this is the killer feature: "To register and publish your plugin, you’ll need to push your code to a public repository on GitHub, and add our post-recieve webhook URL (http://plugins.jquery.com/postreceive-hook) to your repository. The next time you push a semver tag, we’ll take care of registering the plugin name and updating its page on the site. When you’re ready to release the next version of your plugin, just tag and push again!" {quote} -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-949) Validation plugin generates incorrect validation.xml entries for EAP 6.1

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-949?page=com.atlassian.jira.plugin.... ] George Gastaldi closed FORGE-949. --------------------------------- Good job ! > Validation plugin generates incorrect validation.xml entries for EAP 6.1 > ------------------------------------------------------------------------ > > Key: FORGE-949 > URL: https://issues.jboss.org/browse/FORGE-949 > Project: Forge > Issue Type: Bug > Components: Builtin Plugins > Affects Versions: 1.3.0.Final > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > Fix For: 1.3.3.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, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-949) Validation plugin generates incorrect validation.xml entries for EAP 6.1

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-949?page=com.atlassian.jira.plugin.... ] Vineet Reynolds resolved FORGE-949. ----------------------------------- Fix Version/s: 1.3.3.Final (was: 1.x Future) Resolution: Done Pushed upstream: https://github.com/forge/core/commit/7d5c09f90ea704d1b98bc6661a410d6ed715... > Validation plugin generates incorrect validation.xml entries for EAP 6.1 > ------------------------------------------------------------------------ > > Key: FORGE-949 > URL: https://issues.jboss.org/browse/FORGE-949 > Project: Forge > Issue Type: Bug > Components: Builtin Plugins > Affects Versions: 1.3.0.Final > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > Fix For: 1.3.3.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, 9 months

1
0
0 / 0

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

by Lennart Jörelid (JIRA)

[ https://issues.jboss.org/browse/FORGE-980?page=com.atlassian.jira.plugin.... ] Lennart Jörelid updated FORGE-980: ---------------------------------- Attachment: jbossForgePlugin.txt Classloading debug log, identifying the available paths for the two standard classloaders. > 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 > 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, 9 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