May 2013 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-922) Forge JavaParser does not support Wildcard Imports "org.jboss.forge.*"

by Lincoln Baxter III (JIRA)

Lincoln Baxter III created FORGE-922: ---------------------------------------- Summary: Forge JavaParser does not support Wildcard Imports "org.jboss.forge.*" Key: FORGE-922 URL: https://issues.jboss.org/browse/FORGE-922 Project: Forge Issue Type: Enhancement Components: Parsers / File Manipulation Reporter: Lincoln Baxter III Fix For: 2.0.0.Alpha5 The JavaParser Annotation.getQualifiedName() will return "Column" instead of "javax.persistence.Column" for the following example class scenario. It should be able to understand the wildcard, given the proper metadata: {code}package demo.entities; import javax.persistence.*; @Entity public class Contact implements java.io.Serializable { @Id private @GeneratedValue(strategy = GenerationType.AUTO) @Column(name = "id", updatable = false, nullable = false) Long id = null; @Version private @Column(name = "version") int version = 0; public Long getId() { return this.id; } public void setId(final Long id) { this.id = id; } public int getVersion() { return this.version; } public void setVersion(final int version) { this.version = version; } @Override public boolean equals(Object that) { if (this == that) { return true; } if (that == null) { return false; } if (getClass() != that.getClass()) { return false; } if (id != null) { return id.equals(((Contact) that).id); } return super.equals(that); } @Override public int hashCode() { if (id != null) { return id.hashCode(); } return super.hashCode(); } private String name; public String getName() { return this.name; } public void setName(final String name) { this.name = name; } public String toString() { return "" + name; } }{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

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-920) Enhancements for JPA setup + new entity

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-920?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-920: ---------------------------------- Fix Version/s: 2.0.0.Alpha5 > Enhancements for JPA setup + new entity > --------------------------------------- > > Key: FORGE-920 > URL: https://issues.jboss.org/browse/FORGE-920 > Project: Forge > Issue Type: Enhancement > Affects Versions: 2.0.0.Alpha4 > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 2.0.0.Alpha5 > > > {quote} > <lincolnthree> the command should create a completely valid (with package declaration) java class, but it should be created directly in the target folder > ... > <lincolnthree> gastaldi: precisely, but if you are working on a project, does it default the value of targetDir to the full path of where the source will be created? > <lincolnthree> e.g: src/main/java/org/example/ > <gastaldi> it should be > <lincolnthree> ok trying > <lincolnthree> 1 sec > <lincolnthree> it doesn't > <gastaldi> it defaults to the selection you made before running the Wizard > <gastaldi> no ? > <gastaldi> let me see > <lincolnthree> it defaults to the selection, yes > <lincolnthree> but if you are selected in a project > <lincolnthree> it should use the FULL path to the correct location of the class > <lincolnthree> using the project JavaSourceFacet to get the proper location > ... > <lincolnthree> just use context.getInitialSelection() to find the nearest project in the hierarchy > <lincolnthree> also, make sure the command is disabled in the menu isEnabled() == false if no project is found > <lincolnthree> i think that will be enough for now > {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

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-920) Enhancements for JPA setup + new entity

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-920?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-920: ---------------------------------- Affects Version/s: 2.0.0.Alpha4 > Enhancements for JPA setup + new entity > --------------------------------------- > > Key: FORGE-920 > URL: https://issues.jboss.org/browse/FORGE-920 > Project: Forge > Issue Type: Enhancement > Affects Versions: 2.0.0.Alpha4 > Reporter: George Gastaldi > Assignee: George Gastaldi > > {quote} > <lincolnthree> the command should create a completely valid (with package declaration) java class, but it should be created directly in the target folder > ... > <lincolnthree> gastaldi: precisely, but if you are working on a project, does it default the value of targetDir to the full path of where the source will be created? > <lincolnthree> e.g: src/main/java/org/example/ > <gastaldi> it should be > <lincolnthree> ok trying > <lincolnthree> 1 sec > <lincolnthree> it doesn't > <gastaldi> it defaults to the selection you made before running the Wizard > <gastaldi> no ? > <gastaldi> let me see > <lincolnthree> it defaults to the selection, yes > <lincolnthree> but if you are selected in a project > <lincolnthree> it should use the FULL path to the correct location of the class > <lincolnthree> using the project JavaSourceFacet to get the proper location > ... > <lincolnthree> just use context.getInitialSelection() to find the nearest project in the hierarchy > <lincolnthree> also, make sure the command is disabled in the menu isEnabled() == false if no project is found > <lincolnthree> i think that will be enough for now > {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

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-920) Enhancements for JPA setup + new entity

by George Gastaldi (JIRA)

George Gastaldi created FORGE-920: ------------------------------------- Summary: Enhancements for JPA setup + new entity Key: FORGE-920 URL: https://issues.jboss.org/browse/FORGE-920 Project: Forge Issue Type: Enhancement Reporter: George Gastaldi Assignee: George Gastaldi {quote} <lincolnthree> the command should create a completely valid (with package declaration) java class, but it should be created directly in the target folder ... <lincolnthree> gastaldi: precisely, but if you are working on a project, does it default the value of targetDir to the full path of where the source will be created? <lincolnthree> e.g: src/main/java/org/example/ <gastaldi> it should be <lincolnthree> ok trying <lincolnthree> 1 sec <lincolnthree> it doesn't <gastaldi> it defaults to the selection you made before running the Wizard <gastaldi> no ? <gastaldi> let me see <lincolnthree> it defaults to the selection, yes <lincolnthree> but if you are selected in a project <lincolnthree> it should use the FULL path to the correct location of the class <lincolnthree> using the project JavaSourceFacet to get the proper location ... <lincolnthree> just use context.getInitialSelection() to find the nearest project in the hierarchy <lincolnthree> also, make sure the command is disabled in the menu isEnabled() == false if no project is found <lincolnthree> i think that will be enough for now {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

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-919) Document how to configure your own plugin repository

by George Gastaldi (JIRA)

George Gastaldi created FORGE-919: ------------------------------------- Summary: 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 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

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGEPLUGINS-114) org.jboss.tools.forge.ui.wizards

by Paul Leacu (JIRA)

Paul Leacu created FORGEPLUGINS-114: --------------------------------------- Summary: org.jboss.tools.forge.ui.wizards Key: FORGEPLUGINS-114 URL: https://issues.jboss.org/browse/FORGEPLUGINS-114 Project: Forge Plugins Issue Type: Bug Reporter: Paul Leacu Assignee: Koen Aers https://github.com/jbosstools/jbosstools-forge/blob/master/plugins/org.jb... Must support Java 1.6. -- 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, 7 months

1
0
0 / 0

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

by Vineet Reynolds (JIRA)

Vineet Reynolds created FORGE-918: ------------------------------------- Summary: 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 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, 7 months

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 Vineet Reynolds (JIRA)

Vineet Reynolds created FORGE-917: ------------------------------------- Summary: 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.3.0.Final, 1.0.5.Final Reporter: Vineet Reynolds Assignee: Vineet Reynolds 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, 7 months

1
0
0 / 0

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

by Vineet Reynolds (JIRA)

Vineet Reynolds created FORGE-916: ------------------------------------- Summary: 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.3.0.Final, 1.0.5.Final Reporter: Vineet Reynolds Assignee: Vineet Reynolds The generated Faces scaffold contains code to handle deletion. But this works only for all 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, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-915) Faces scaffold should use the server timezone instead of UTC for date and time fields

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-915?page=com.atlassian.jira.plugin.... ] Vineet Reynolds resolved FORGE-915. ----------------------------------- Fix Version/s: 1.3.1.Final Resolution: Done Pushed upstream https://github.com/forge/core/commit/026b56e06b55436e243a5926d62597357ec0... > Faces scaffold should use the server timezone instead of UTC for date and time fields > ------------------------------------------------------------------------------------- > > Key: FORGE-915 > URL: https://issues.jboss.org/browse/FORGE-915 > Project: Forge > Issue Type: Bug > 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 uses UTC to represent dates and times in all usages of {{h:outputText}}. This is the default behavior but is confusing and appears incorrect, since end-users would expect to see the dates and times from the perspective of the server timezone (which is used for storage). > Also, the stored dates are displayed with an offset of one day when the server timezone is ahead of UTC. -- 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, 7 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues May 2013