July 2013 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-974) Faces scaffolding does not correctly update collection members involved in bi-directional relationships when saving an edited entity

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-974?page=com.atlassian.jira.plugin.... ] Vineet Reynolds updated FORGE-974: ---------------------------------- Priority: Critical (was: Major) > Faces scaffolding does not correctly update collection members involved in bi-directional relationships when saving an edited entity > ------------------------------------------------------------------------------------------------------------------------------------ > > Key: FORGE-974 > URL: https://issues.jboss.org/browse/FORGE-974 > Project: Forge > Issue Type: Bug > Components: Scaffold > Affects Versions: 1.3.1.Final > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > Priority: Critical > > The generated scaffold does not contain any logic to update collection properties of a JPA entity. This results in incorrect behavior when the collection is part of a bi-directional relationship in JPA. > This is because no logic exists to remove both sides of the relationship when an entity instance is removed from the collection. The result of this absence in logic is that removal of entities from collection properties do not succeed. Upon save, the collection returns to it's previous state. > Addition of members to the collection property are however performed correctly. Since the Faces scaffold does not allow updates to properties of the the individual members in the collection, no other issue is observed, except for the inability to update the collection state correctly. -- 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-919) Document how to configure your own plugin repository

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-919?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-919: ---------------------------------- Status: Closed (was: Pull Request Sent) Fix Version/s: 1.3.4.Final (was: 1.x Future) Resolution: Done > Document how to configure your own plugin repository > ---------------------------------------------------- > > Key: FORGE-919 > URL: https://issues.jboss.org/browse/FORGE-919 > Project: Forge > Issue Type: Task > Components: Documentation > Affects Versions: 1.3.0.Final > Reporter: George Gastaldi > Assignee: Vineet Reynolds > Fix For: 1.3.4.Final > > > The forge documentation should describe how to create your own personal plugin repository. > Something like: > Add a YAML file like https://github.com/forge/plugin-repository/blob/master/repository.yaml and change the DEFAULT_PLUGIN_REPO property to point to your URL -- 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-919) Document how to configure your own plugin repository

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-919?page=com.atlassian.jira.plugin.... ] Vineet Reynolds updated FORGE-919: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/forge/forge.github.com/pull/16 > Document how to configure your own plugin repository > ---------------------------------------------------- > > Key: FORGE-919 > URL: https://issues.jboss.org/browse/FORGE-919 > Project: Forge > Issue Type: Task > Components: Documentation > Affects Versions: 1.3.0.Final > Reporter: George Gastaldi > Assignee: Vineet Reynolds > Fix For: 1.x Future > > > The forge documentation should describe how to create your own personal plugin repository. > Something like: > Add a YAML file like https://github.com/forge/plugin-repository/blob/master/repository.yaml and change the DEFAULT_PLUGIN_REPO property to point to your URL -- 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-861) Forge 2 does not start upon installation into Eclipse. Must restart eclipse.

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-861?page=com.atlassian.jira.plugin.... ] George Gastaldi commented on FORGE-861: --------------------------------------- Works for me > Forge 2 does not start upon installation into Eclipse. Must restart eclipse. > ---------------------------------------------------------------------------- > > Key: FORGE-861 > URL: https://issues.jboss.org/browse/FORGE-861 > Project: Forge > Issue Type: Bug > Components: UI - Eclipse > Affects Versions: 2.0.0.Alpha2 > Reporter: Lincoln Baxter III > Assignee: George Gastaldi > Fix For: 2.0.0.Alpha6 > > > Technically this issue is in the JBDS side, but since it is related to Forge 2 only, I put the issue here for now. -- 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-861) Forge 2 does not start upon installation into Eclipse. Must restart eclipse.

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-861?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III closed FORGE-861. ------------------------------------ Resolution: Done > Forge 2 does not start upon installation into Eclipse. Must restart eclipse. > ---------------------------------------------------------------------------- > > Key: FORGE-861 > URL: https://issues.jboss.org/browse/FORGE-861 > Project: Forge > Issue Type: Bug > Components: UI - Eclipse > Affects Versions: 2.0.0.Alpha2 > Reporter: Lincoln Baxter III > Assignee: George Gastaldi > Fix For: 2.0.0.Alpha6 > > > Technically this issue is in the JBDS side, but since it is related to Forge 2 only, I put the issue here for now. -- 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-861) Forge 2 does not start upon installation into Eclipse. Must restart eclipse.

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-861?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III updated FORGE-861: ------------------------------------- Fix Version/s: (was: 2.x Future) > Forge 2 does not start upon installation into Eclipse. Must restart eclipse. > ---------------------------------------------------------------------------- > > Key: FORGE-861 > URL: https://issues.jboss.org/browse/FORGE-861 > Project: Forge > Issue Type: Bug > Components: UI - Eclipse > Affects Versions: 2.0.0.Alpha2 > Reporter: Lincoln Baxter III > Assignee: George Gastaldi > Fix For: 2.0.0.Alpha6 > > > Technically this issue is in the JBDS side, but since it is related to Forge 2 only, I put the issue here for now. -- 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-861) Forge 2 does not start upon installation into Eclipse. Must restart eclipse.

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-861?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III closed FORGE-861. ------------------------------------ Assignee: George Gastaldi Fix Version/s: 2.0.0.Alpha6 Resolution: Cannot Reproduce Bug > Forge 2 does not start upon installation into Eclipse. Must restart eclipse. > ---------------------------------------------------------------------------- > > Key: FORGE-861 > URL: https://issues.jboss.org/browse/FORGE-861 > Project: Forge > Issue Type: Bug > Components: UI - Eclipse > Affects Versions: 2.0.0.Alpha2 > Reporter: Lincoln Baxter III > Assignee: George Gastaldi > Fix For: 2.x Future, 2.0.0.Alpha6 > > > Technically this issue is in the JBDS side, but since it is related to Forge 2 only, I put the issue here for now. -- 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-861) Forge 2 does not start upon installation into Eclipse. Must restart eclipse.

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-861?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III reopened FORGE-861: -------------------------------------- > Forge 2 does not start upon installation into Eclipse. Must restart eclipse. > ---------------------------------------------------------------------------- > > Key: FORGE-861 > URL: https://issues.jboss.org/browse/FORGE-861 > Project: Forge > Issue Type: Bug > Components: UI - Eclipse > Affects Versions: 2.0.0.Alpha2 > Reporter: Lincoln Baxter III > Assignee: George Gastaldi > Fix For: 2.0.0.Alpha6, 2.x Future > > > Technically this issue is in the JBDS side, but since it is related to Forge 2 only, I put the issue here for now. -- 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-1017) A valid package name should be computed as default when prompting for a replacement in a JAVA_PACKAGE prompt

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1017?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-1017: ----------------------------------- Status: Closed (was: Pull Request Sent) Fix Version/s: 1.3.4.Final Resolution: Done Merged, thanks > A valid package name should be computed as default when prompting for a replacement in a JAVA_PACKAGE prompt > ------------------------------------------------------------------------------------------------------------ > > Key: FORGE-1017 > URL: https://issues.jboss.org/browse/FORGE-1017 > Project: Forge > Issue Type: Enhancement > Affects Versions: 1.3.3.Final > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > Fix For: 1.3.4.Final > > > When an invalid package name is supplied as a value for an option whose {{PromptType}} is {{PromptType.JAVA_PACKAGE}}, then Forge prompt again for a valid value. No default is computed, and thus this is not friendly to scripts or to environments like the JBDS 7 Forge wizards where the shell is not accessible directly. > An enhancement is thus sought to compute a valid default value for such cases. -- 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-687) PromptType.JAVA_PACKAGE should support default package

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-687?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-687: ---------------------------------- Status: Closed (was: Pull Request Sent) Fix Version/s: 1.3.4.Final (was: 1.x Future) Resolution: Done Merged, thanks ! > PromptType.JAVA_PACKAGE should support default package > ------------------------------------------------------ > > Key: FORGE-687 > URL: https://issues.jboss.org/browse/FORGE-687 > Project: Forge > Issue Type: Bug > Components: UI - Shell > Affects Versions: 1.0.5.Final > Reporter: Andre Dietisheim > Assignee: Vineet Reynolds > Fix For: 1.3.4.Final > > > If you want to prompt the user to provide some valid java package you'd specify PromptType.JAVA_PACKAGE. Unfortunately this prompt type considers the empty string as invalid package even though I'd argue that this is the default package. > If I ask the user for the package, scaffolded resources would get created to, I'd do: > {code} > prompt.promptCommon(target package: ", PromptType.JAVA_PACKAGE, project.getFacet(JavaSourceFacet.class).getBasePackageResource().toString()) > {code} > If I have no valid packageResource (ex. forge would return an invalid base package) I'd want to suggest the user to put his sources into the default package (for a maven project: src/main/java). I'd then feed a "" as default to the prompt: > {code} > prompt.promptCommon(target package: ", PromptType.JAVA_PACKAGE, "") > {code} > Unfortunately the PromptType.JAVA_PACKAGE would not validate the empty string. It would tell me that this is not a valid package. -- 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