July 2013 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-997) bean new-bean not working for all types

by Hubert Schumacher (JIRA)

Hubert Schumacher created FORGE-997: --------------------------------------- Summary: bean new-bean not working for all types Key: FORGE-997 URL: https://issues.jboss.org/browse/FORGE-997 Project: Forge Issue Type: Bug Affects Versions: 1.3.2.Final Environment: Eclipse Kepler + Jboss tools 4 Reporter: Hubert Schumacher forge command "beans new-bean --type abc.import.cde.ExampleJava" throws exception if type has 'import' in its path. Maybe other magic words as well?! -- 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-996) Incorrect deletion logic is generation for OneToOne relationships and inverse sides of ManyToMany relationships

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-996?page=com.atlassian.jira.plugin.... ] Vineet Reynolds closed FORGE-996. --------------------------------- Fix Version/s: 1.3.3.Final Resolution: Done Pushed upstream: https://github.com/forge/core/commit/8c0103dc1748c45b947ed509faaaaa4fc93b... > Incorrect deletion logic is generation for OneToOne relationships and inverse sides of ManyToMany relationships > --------------------------------------------------------------------------------------------------------------- > > Key: FORGE-996 > URL: https://issues.jboss.org/browse/FORGE-996 > 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 > > > Given two classes {{Foo}} and {{Bar}} the following deletion code is generated for bidirectional OneToOne relationship between them: > {code:title=FooBean.java|borderStyle=solid} > Foo foo = deletableEntity.getFoo();deletableEntity.setBar(null);this.entityManager.merge(foo); > {code} > {code:title=BarBean.java|borderStyle=solid} > Example bar = deletableEntity.getBar();deletableEntity.setFoo(null);this.entityManager.merge(bar); > {code} > This is incorrect - the setters on the {{deletableEntity}} should not be invoked. -- 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-996) Incorrect deletion logic is generation for OneToOne relationships and inverse sides of ManyToMany relationships

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-996?page=com.atlassian.jira.plugin.... ] Vineet Reynolds updated FORGE-996: ---------------------------------- Assignee: Vineet Reynolds Affects Version/s: 1.3.2.Final Component/s: Scaffold > Incorrect deletion logic is generation for OneToOne relationships and inverse sides of ManyToMany relationships > --------------------------------------------------------------------------------------------------------------- > > Key: FORGE-996 > URL: https://issues.jboss.org/browse/FORGE-996 > Project: Forge > Issue Type: Bug > Components: Scaffold > Affects Versions: 1.3.2.Final > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > > Given two classes {{Foo}} and {{Bar}} the following deletion code is generated for bidirectional OneToOne relationship between them: > {code:title=FooBean.java|borderStyle=solid} > Foo foo = deletableEntity.getFoo();deletableEntity.setBar(null);this.entityManager.merge(foo); > {code} > {code:title=BarBean.java|borderStyle=solid} > Example bar = deletableEntity.getBar();deletableEntity.setFoo(null);this.entityManager.merge(bar); > {code} > This is incorrect - the setters on the {{deletableEntity}} should not be invoked. -- 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-996) Incorrect deletion logic is generation for OneToOne relationships and inverse sides of ManyToMany relationships

by Vineet Reynolds (JIRA)

Vineet Reynolds created FORGE-996: ------------------------------------- Summary: Incorrect deletion logic is generation for OneToOne relationships and inverse sides of ManyToMany relationships Key: FORGE-996 URL: https://issues.jboss.org/browse/FORGE-996 Project: Forge Issue Type: Bug Reporter: Vineet Reynolds Given two classes {{Foo}} and {{Bar}} the following deletion code is generated for bidirectional OneToOne relationship between them: {code:title=FooBean.java|borderStyle=solid} Foo foo = deletableEntity.getFoo();deletableEntity.setBar(null);this.entityManager.merge(foo); {code} {code:title=BarBean.java|borderStyle=solid} Example bar = deletableEntity.getBar();deletableEntity.setFoo(null);this.entityManager.merge(bar); {code} This is incorrect - the setters on the {{deletableEntity}} should not be invoked. -- 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-593) Forge swallows first character of user input after restarting (typically from plugin installation)

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-593?page=com.atlassian.jira.plugin.... ] Vineet Reynolds updated FORGE-593: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/forge/core/pull/328 Fixed by ensuring that the new console reader thread has a chance to acquire a lock on the console inputstream. This is more or less done by ensuring that the previous reader thread shuts down cleanly. The available() method is used to detect if a blocking read() should be performed on the console inputstream. This prevents/reduces the possibility of the reader thread from blocking on the console during a Forge restart triggered by a plugin installation. Additionally, during shutdown of the console, the reader thread is interrupted should it have acquired a monitor on the console inputstream, thus allowing for a clean shutdown. > Forge swallows first character of user input after restarting (typically from plugin installation) > -------------------------------------------------------------------------------------------------- > > Key: FORGE-593 > URL: https://issues.jboss.org/browse/FORGE-593 > Project: Forge > Issue Type: Bug > Components: UI - Shell > Affects Versions: 1.0.5.Final > Reporter: Lincoln Baxter III > Assignee: Vineet Reynolds > Labels: annoying > Fix For: 1.x Future > > Attachments: threaddump-1373073105033.tdump > > > 'forge install-plugin openshift' > Then type something. The first character you type will not be displayed or read. -- 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-593) Forge swallows first character of user input after restarting (typically from plugin installation)

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-593?page=com.atlassian.jira.plugin.... ] Vineet Reynolds updated FORGE-593: ---------------------------------- Attachment: threaddump-1373073105033.tdump Attached a thread dump showing that the new console reader thread (thread-19) started on a Forge restart is in BLOCKED state, due to the existing console reader thread (thread-12) having already acquired the desired lock. > Forge swallows first character of user input after restarting (typically from plugin installation) > -------------------------------------------------------------------------------------------------- > > Key: FORGE-593 > URL: https://issues.jboss.org/browse/FORGE-593 > Project: Forge > Issue Type: Bug > Components: UI - Shell > Affects Versions: 1.0.5.Final > Reporter: Lincoln Baxter III > Assignee: Vineet Reynolds > Labels: annoying > Fix For: 1.x Future > > Attachments: threaddump-1373073105033.tdump > > > 'forge install-plugin openshift' > Then type something. The first character you type will not be displayed or read. -- 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-593) Forge swallows first character of user input after restarting (typically from plugin installation)

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-593?page=com.atlassian.jira.plugin.... ] Vineet Reynolds reassigned FORGE-593: ------------------------------------- Assignee: Vineet Reynolds > Forge swallows first character of user input after restarting (typically from plugin installation) > -------------------------------------------------------------------------------------------------- > > Key: FORGE-593 > URL: https://issues.jboss.org/browse/FORGE-593 > Project: Forge > Issue Type: Bug > Components: UI - Shell > Affects Versions: 1.0.5.Final > Reporter: Lincoln Baxter III > Assignee: Vineet Reynolds > Labels: annoying > Fix For: 1.x Future > > > 'forge install-plugin openshift' > Then type something. The first character you type will not be displayed or read. -- 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-995) The generated hashcode() and equals() methods should not reference the hardcoded 'id' field

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-995?page=com.atlassian.jira.plugin.... ] Vineet Reynolds reassigned FORGE-995: ------------------------------------- Assignee: Vineet Reynolds > The generated hashcode() and equals() methods should not reference the hardcoded 'id' field > ------------------------------------------------------------------------------------------- > > Key: FORGE-995 > URL: https://issues.jboss.org/browse/FORGE-995 > Project: Forge > Issue Type: Enhancement > Components: Parsers / File Manipulation > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > Priority: Minor > > The field name(s) should be provided as a parameter -- 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-995) The generated hashcode() and equals() methods should not reference the hardcoded 'id' field

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-995?page=com.atlassian.jira.plugin.... ] Vineet Reynolds updated FORGE-995: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/forge/java-parser/pull/2 This is an API breaking change due to the introduction of a new parameter in the method. The new implementation does away with the hardcoded field. It also generates equals and hashcode methods that are closer to the typically generated ones in IDEs. > The generated hashcode() and equals() methods should not reference the hardcoded 'id' field > ------------------------------------------------------------------------------------------- > > Key: FORGE-995 > URL: https://issues.jboss.org/browse/FORGE-995 > Project: Forge > Issue Type: Enhancement > Components: Parsers / File Manipulation > Reporter: Vineet Reynolds > Priority: Minor > > The field name(s) should be provided as a parameter -- 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-995) The generated hashcode() and equals() methods should not reference the hardcoded 'id' field

by Vineet Reynolds (JIRA)

Vineet Reynolds created FORGE-995: ------------------------------------- Summary: The generated hashcode() and equals() methods should not reference the hardcoded 'id' field Key: FORGE-995 URL: https://issues.jboss.org/browse/FORGE-995 Project: Forge Issue Type: Enhancement Components: Parsers / File Manipulation Reporter: Vineet Reynolds Priority: Minor The field name(s) should be provided as a parameter -- 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