June 2013 - forge-issues - Jboss List Archives

[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 updated FORGE-949: ---------------------------------- Fix Version/s: 1.x Future > 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.x Future > > -- 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

11 years

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 closed FORGE-340. --------------------------------- Assignee: George Gastaldi (was: Rodney Russ) Fix Version/s: 1.3.1.Final (was: 1.x Future) Resolution: Done Fixed. Introduced flag *--keepSources* and checkoutDir now is properly disposed if this flag is not set > 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: UI - Shell > Affects Versions: 1.0.0.Alpha4 > Reporter: Lincoln Baxter III > Assignee: George Gastaldi > Priority: Minor > Labels: Starter > Fix For: 1.3.1.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

11 years

1
0
0 / 0

[JBoss JIRA] (FORGE-811) MavenPlugin: Add maven plugin

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-811?page=com.atlassian.jira.plugin.... ] George Gastaldi closed FORGE-811. --------------------------------- Fix Version/s: 1.3.1.Final (was: 1.x Future) Resolution: Done Implemented > MavenPlugin: Add maven plugin > ----------------------------- > > Key: FORGE-811 > URL: https://issues.jboss.org/browse/FORGE-811 > Project: Forge > Issue Type: Feature Request > Components: Maven Integration > Affects Versions: 1.2.1.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Labels: starter > Fix For: 1.3.1.Final > > > The MavenPlugin could have a command to add Maven plugins to the current project's pom.xml > Syntax could be something like: > {code} > maven add-plugin groupId:artifactId:version > {code} > version is optional and may be prompted if not specified. -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (FORGE-811) MavenPlugin: Add maven plugin

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-811?page=com.atlassian.jira.plugin.... ] George Gastaldi reassigned FORGE-811: ------------------------------------- Assignee: George Gastaldi (was: Ãbner Oliveira) > MavenPlugin: Add maven plugin > ----------------------------- > > Key: FORGE-811 > URL: https://issues.jboss.org/browse/FORGE-811 > Project: Forge > Issue Type: Feature Request > Components: Maven Integration > Affects Versions: 1.2.1.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Labels: starter > Fix For: 1.x Future > > > The MavenPlugin could have a command to add Maven plugins to the current project's pom.xml > Syntax could be something like: > {code} > maven add-plugin groupId:artifactId:version > {code} > version is optional and may be prompted if not specified. -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (FORGE-916) Faces scaffold does not handle deletion of entities with bidirectional relationships

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-916?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-916: ---------------------------------- Fix Version/s: 1.3.1.Final (was: 1.x Future) > Faces scaffold does not handle deletion of entities with bidirectional relationships > ------------------------------------------------------------------------------------ > > Key: FORGE-916 > URL: https://issues.jboss.org/browse/FORGE-916 > Project: Forge > Issue Type: Bug > Components: Scaffold > Affects Versions: 1.0.5.Final, 1.3.0.Final > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > Fix For: 1.3.1.Final > > > The generated Faces scaffold contains code to handle deletion. But this works only for some scenarios. > For bidirectional relationships, the generated code in the View Beans should perform deletion on both sides of the relationship. Currently, this is performed on only one side - the side corresponding to the view from where deletion was triggered. -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (FORGE-918) Faces Scaffolding interprets long x[][] fields as long

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-918?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-918: ---------------------------------- Fix Version/s: 1.3.1.Final (was: 1.x Future) > Faces Scaffolding interprets long x[][] fields as long > ------------------------------------------------------ > > Key: FORGE-918 > URL: https://issues.jboss.org/browse/FORGE-918 > Project: Forge > Issue Type: Bug > Reporter: Vineet Reynolds > Fix For: 1.3.1.Final > > > This is from TicketMonster. The {{SectionAllocation}} class contains a {{long allocated[][]}} field. With the getters and setters (one may need to add the setters; see FORGE-917), the generated view does not contain a widget for the n-dimensional array type, and instead displays a single numerical entry widget. -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (FORGE-913) RichFaces scaffolding does not handle temporal fields in JPA entities correctly

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-913?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-913: ---------------------------------- Fix Version/s: 1.3.1.Final (was: 1.x Future) > RichFaces scaffolding does not handle temporal fields in JPA entities correctly > ------------------------------------------------------------------------------- > > Key: FORGE-913 > URL: https://issues.jboss.org/browse/FORGE-913 > Project: Forge > Issue Type: Bug > Components: Scaffold > Affects Versions: 1.0.5.Final, 1.3.0.Final > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > Fix For: 1.3.1.Final > > > The RichFaces scaffold generator creates {{rich:calendar}} components in the facelets, but without a {{datePattern}} attribute. The behavior of this component in such a case is to not provide the embeddded timepicker. This works for temporal fields of type Date. > But, this is certainly not sufficient for temporal fields of type Timestamp. A {{datePattern}} with a time pattern like {{MMM d, yyyy HH:mm}} or {{MMM d, yyyy hh:mm:a}} needs to be generated for such fields to allow time inputs. > For temporal fields of type Time, consider generating a different widget, since the RichFaces calendar widget is not capable of providing the timepicker alone. -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (FORGE-917) Faces scaffolding omits fields in the create/edit/search views when they do not have setter methods

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-917?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-917: ---------------------------------- Fix Version/s: 1.3.1.Final (was: 1.x Future) > Faces scaffolding omits fields in the create/edit/search views when they do not have setter methods > --------------------------------------------------------------------------------------------------- > > Key: FORGE-917 > URL: https://issues.jboss.org/browse/FORGE-917 > Project: Forge > Issue Type: Bug > Components: Scaffold > Affects Versions: 1.0.5.Final, 1.3.0.Final > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > Fix For: 1.3.1.Final > > > This is from the TicketMonster model. The create,edit and search views for the {{SectionAllocation}} and {{Ticket}} classes only list the current values of the entities. Creating new entities or editing of existing entities of such classes with user-specified values is not possible. Likewise, searching with a criteria is not possible. > Both these JPA entities have one thing in common, in that they do not have setters for their fields. -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (FORGE-958) Forge quick-assist menu does not display commands on first run (should probably give some time for forge to start)

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-958?page=com.atlassian.jira.plugin.... ] George Gastaldi closed FORGE-958. --------------------------------- Assignee: George Gastaldi Fix Version/s: 2.0.0.Alpha6 (was: 2.x Future) Resolution: Done Fixed in the eclipse plugin. Now the quick assist menu waits until the container is started before opening. > Forge quick-assist menu does not display commands on first run (should probably give some time for forge to start) > ------------------------------------------------------------------------------------------------------------------ > > Key: FORGE-958 > URL: https://issues.jboss.org/browse/FORGE-958 > Project: Forge > Issue Type: Feature Request > Components: UI - Eclipse > Affects Versions: 2.0.0.Alpha5 > Reporter: Lincoln Baxter III > Assignee: George Gastaldi > Fix For: 2.0.0.Alpha6 > > > The command quick menu of Forge 2 does not show menu choices the first time because forge is still starting while it is searching for commands to run. First run should probably wait for forge to start before displaying... or should periodically refresh to load new commands (or remove commands that have been uninstalled while the menu is open.) -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (FORGE-958) Forge quick-assist menu does not display commands on first run (should probably give some time for forge to start)

by Lincoln Baxter III (JIRA)

Lincoln Baxter III created FORGE-958: ---------------------------------------- Summary: Forge quick-assist menu does not display commands on first run (should probably give some time for forge to start) Key: FORGE-958 URL: https://issues.jboss.org/browse/FORGE-958 Project: Forge Issue Type: Feature Request Components: UI - Eclipse Affects Versions: 2.0.0.Alpha5 Reporter: Lincoln Baxter III Fix For: 2.x Future The command quick menu of Forge 2 does not show menu choices the first time because forge is still starting while it is searching for commands to run. First run should probably wait for forge to start before displaying... or should periodically refresh to load new commands (or remove commands that have been uninstalled while the menu is open.) -- 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

11 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues June 2013