August 2013 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-1118) Allow skipping of DOT generation using property

by George Gastaldi (JIRA)

George Gastaldi created FORGE-1118: -------------------------------------- Summary: Allow skipping of DOT generation using property Key: FORGE-1118 URL: https://issues.jboss.org/browse/FORGE-1118 Project: Forge Issue Type: Enhancement Components: Maven Plugin Affects Versions: 2.0.0.Alpha10 Reporter: George Gastaldi Assignee: George Gastaldi Priority: Trivial Fix For: 2.0.0.Alpha11 If a property eg: {{furnace.dot.skip}} is specified, the generation of the DOT file should be skipped. This is useful when building of the artifact is not necessary in constant deploy/debug scenarios. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1117) Display a warning message when Forge boots up without any addons

by George Gastaldi (JIRA)

George Gastaldi created FORGE-1117: -------------------------------------- Summary: Display a warning message when Forge boots up without any addons Key: FORGE-1117 URL: https://issues.jboss.org/browse/FORGE-1117 Project: Forge Issue Type: Enhancement Components: Furnace (Container) Affects Versions: 2.0.0.Alpha10 Reporter: George Gastaldi Fix For: 2.x Future When Forge boots up without any addon, a warning message should be displayed. This helps users to understand that Forge is running and not frozen. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1116) Move forge.compatibility.IDE to the Environment Addon

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1116?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-1116: ----------------------------------- Summary: Move forge.compatibility.IDE to the Environment Addon (was: Move forge.compatability.IDE to the Environment Addon) > Move forge.compatibility.IDE to the Environment Addon > ----------------------------------------------------- > > Key: FORGE-1116 > URL: https://issues.jboss.org/browse/FORGE-1116 > Project: Forge > Issue Type: Feature Request > Components: Builtin Plugins > Affects Versions: 2.0.0.Alpha10 > Reporter: Lincoln Baxter III > Fix For: 2.x Future > > > From the shell addon: > {code} > public void startupDefaultShell(@Observes PostStartup startup) throws Exception > { > if (!Boolean.getBoolean("forge.compatibility.IDE")) > { > Settings settings = new SettingsBuilder().create(); > this.shell = shellFactory.createShell(settings); > } > } > {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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1116) Move forge.compatability.IDE to the Environment Addon

by Lincoln Baxter III (JIRA)

Lincoln Baxter III created FORGE-1116: ----------------------------------------- Summary: Move forge.compatability.IDE to the Environment Addon Key: FORGE-1116 URL: https://issues.jboss.org/browse/FORGE-1116 Project: Forge Issue Type: Feature Request Components: Builtin Plugins Affects Versions: 2.0.0.Alpha10 Reporter: Lincoln Baxter III >From the shell addon: {code} public void startupDefaultShell(@Observes PostStartup startup) throws Exception { if (!Boolean.getBoolean("forge.compatibility.IDE")) { Settings settings = new SettingsBuilder().create(); this.shell = shellFactory.createShell(settings); } } {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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1116) Move forge.compatability.IDE to the Environment Addon

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1116?page=com.atlassian.jira.plugin... ] Lincoln Baxter III updated FORGE-1116: -------------------------------------- Fix Version/s: 2.x Future > Move forge.compatability.IDE to the Environment Addon > ----------------------------------------------------- > > Key: FORGE-1116 > URL: https://issues.jboss.org/browse/FORGE-1116 > Project: Forge > Issue Type: Feature Request > Components: Builtin Plugins > Affects Versions: 2.0.0.Alpha10 > Reporter: Lincoln Baxter III > Fix For: 2.x Future > > > From the shell addon: > {code} > public void startupDefaultShell(@Observes PostStartup startup) throws Exception > { > if (!Boolean.getBoolean("forge.compatibility.IDE")) > { > Settings settings = new SettingsBuilder().create(); > this.shell = shellFactory.createShell(settings); > } > } > {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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1115) Generate code in JPA entities to implement the mutual registration pattern

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-1115?page=com.atlassian.jira.plugin... ] Vineet Reynolds edited comment on FORGE-1115 at 8/16/13 2:23 PM: ----------------------------------------------------------------- Since code generation of business services may rely on this, it would be necessary to determine whether the pattern is implemented. This would have to wait until method bodies can be parsed to determine if the inverse fields are referenced in the desired manner. A non-deterministic way would involve parsing some of the code like method signatures, javadoc comments etc., to heuristically determine if the pattern is implemented. was (Author: vineet.reynolds): Since code generation of business services may rely on this, it would be necessary to determine whether the pattern is implemented. This would have to wait until method bodies can be parsed to determine if the inverse fields are referenced in the desired manner. A non-deterministic way would involve parsing some of the code like method signatures, to heuristically determine if the pattern is implemented. > Generate code in JPA entities to implement the mutual registration pattern > -------------------------------------------------------------------------- > > Key: FORGE-1115 > URL: https://issues.jboss.org/browse/FORGE-1115 > Project: Forge > Issue Type: Feature Request > Components: Builtin Plugins > Affects Versions: 1.3.3.Final > Reporter: Vineet Reynolds > Fix For: 1.x Future, 2.x Future > > > It would be preferable to generate code to implement [the mutual registration pattern|http://www.two-sdg.demon.co.uk/curbralan/papers/MutualRegistration.pdf]. This would ensure that changes to bidirectional relationships are propagated through methods invoked on the JPA entity, instead of delegating this logic to the business services. Not implementing this, would result in [object corruption issues|http://en.wikibooks.org/wiki/Java_Persistence/Relationships#Object...]. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1115) Generate code in JPA entities to implement the mutual registration pattern

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-1115?page=com.atlassian.jira.plugin... ] Vineet Reynolds commented on FORGE-1115: ---------------------------------------- Since code generation of business services may rely on this, it would be necessary to determine whether the pattern is implemented. This would have to wait until method bodies can be parsed to determine if the inverse fields are referenced in the desired manner. A non-deterministic way would involve parsing some of the code like method signatures, to heuristically determine if the pattern is implemented. > Generate code in JPA entities to implement the mutual registration pattern > -------------------------------------------------------------------------- > > Key: FORGE-1115 > URL: https://issues.jboss.org/browse/FORGE-1115 > Project: Forge > Issue Type: Feature Request > Components: Builtin Plugins > Affects Versions: 1.3.3.Final > Reporter: Vineet Reynolds > Fix For: 1.x Future, 2.x Future > > > It would be preferable to generate code to implement [the mutual registration pattern|http://www.two-sdg.demon.co.uk/curbralan/papers/MutualRegistration.pdf]. This would ensure that changes to bidirectional relationships are propagated through methods invoked on the JPA entity, instead of delegating this logic to the business services. Not implementing this, would result in [object corruption issues|http://en.wikibooks.org/wiki/Java_Persistence/Relationships#Object...]. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1115) Generate code in JPA entities to implement the mutual registration pattern

by Vineet Reynolds (JIRA)

Vineet Reynolds created FORGE-1115: -------------------------------------- Summary: Generate code in JPA entities to implement the mutual registration pattern Key: FORGE-1115 URL: https://issues.jboss.org/browse/FORGE-1115 Project: Forge Issue Type: Feature Request Components: Builtin Plugins Affects Versions: 1.3.3.Final Reporter: Vineet Reynolds Fix For: 1.x Future, 2.x Future It would be preferable to generate code to implement [the mutual registration pattern|http://www.two-sdg.demon.co.uk/curbralan/papers/MutualRegistration.pdf]. This would ensure that changes to bidirectional relationships are propagated through methods invoked on the JPA entity, instead of delegating this logic to the business services. Not implementing this, would result in [object corruption issues|http://en.wikibooks.org/wiki/Java_Persistence/Relationships#Object...]. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGEPLUGINS-131) AngularJS scaffold should discover the REST endpoints instead of making assumptions

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGEPLUGINS-131?page=com.atlassian.jira.... ] Vineet Reynolds closed FORGEPLUGINS-131. ---------------------------------------- Resolution: Done Pushed upstream: https://github.com/forge/angularjs-scaffoldx-plugin/commit/b5a9c5dc83b3f5... > AngularJS scaffold should discover the REST endpoints instead of making assumptions > ----------------------------------------------------------------------------------- > > Key: FORGEPLUGINS-131 > URL: https://issues.jboss.org/browse/FORGEPLUGINS-131 > Project: Forge Plugins > Issue Type: Feature Request > Components: AngularJS Scaffold > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > > The AngularJS scaffold should attempt to discover the REST endpoints corresponding to the JPA entities instead of assuming that they are present at the URL {{/<entityName>+s}} location under the root URL for JAX-RS resources. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGEPLUGINS-131) AngularJS scaffold should discover the REST endpoints instead of making assumptions

by Vineet Reynolds (JIRA)

Vineet Reynolds created FORGEPLUGINS-131: -------------------------------------------- Summary: AngularJS scaffold should discover the REST endpoints instead of making assumptions Key: FORGEPLUGINS-131 URL: https://issues.jboss.org/browse/FORGEPLUGINS-131 Project: Forge Plugins Issue Type: Feature Request Components: AngularJS Scaffold Reporter: Vineet Reynolds Assignee: Vineet Reynolds The AngularJS scaffold should attempt to discover the REST endpoints corresponding to the JPA entities instead of assuming that they are present at the URL {{/<entityName>+s}} location under the root URL for JAX-RS resources. -- 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, 7 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues August 2013