November 2013 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-233) Allow user to specify a custom Eclipse formatting profile

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-233?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III updated FORGE-233: ------------------------------------- Fix Version/s: 2.x Future (was: 1.x Future) > Allow user to specify a custom Eclipse formatting profile > --------------------------------------------------------- > > Key: FORGE-233 > URL: https://issues.jboss.org/browse/FORGE-233 > Project: Forge > Issue Type: Feature Request > Components: Parsers / File Manipulation > Affects Versions: 1.0.0.Alpha3 > Reporter: Dan Allen > Labels: Starter > Fix For: 2.x Future > > > Allow the user to specify an Eclipse formatting profile in the local configuration (~/.forge). When creating (or updating) Java files, use the Eclipse formatter (or alternative) to format the code using the formatting profile. -- 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-662) Generated Scaffold should display a message after saving entities

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-662?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III closed FORGE-662. ------------------------------------ Fix Version/s: (was: 2.x Future) Resolution: Rejected Forge 1 already prints file modification notifications. Forge 2 will display the accept-changes dialog. > Generated Scaffold should display a message after saving entities > ----------------------------------------------------------------- > > Key: FORGE-662 > URL: https://issues.jboss.org/browse/FORGE-662 > Project: Forge > Issue Type: Feature Request > Components: Scaffold > Reporter: George Gastaldi > Priority: Minor > > A message saying "Entity ... was sucessfully saved" should be displayed after a save operation is done. -- 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-662) Generated Scaffold should display a message after saving entities

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-662?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III updated FORGE-662: ------------------------------------- Fix Version/s: 2.x Future (was: 1.x Future) > Generated Scaffold should display a message after saving entities > ----------------------------------------------------------------- > > Key: FORGE-662 > URL: https://issues.jboss.org/browse/FORGE-662 > Project: Forge > Issue Type: Feature Request > Components: Scaffold > Reporter: George Gastaldi > Priority: Minor > Fix For: 2.x Future > > > A message saying "Entity ... was sucessfully saved" should be displayed after a save operation is done. -- 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-910) In View Beans, Search predicate for boolean fields is not supported

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-910?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III updated FORGE-910: ------------------------------------- Fix Version/s: 2.x Future (was: 1.x Future) > In View Beans, Search predicate for boolean fields is not supported > ------------------------------------------------------------------- > > Key: FORGE-910 > URL: https://issues.jboss.org/browse/FORGE-910 > Project: Forge > Issue Type: Feature Request > Components: Scaffold > Affects Versions: 1.2.3.Final > Environment: Linux 3.8, Firefox. > Reporter: Hanine Hanynowsky > Priority: Minor > Fix For: 2.x Future > > > In View Beans, Search predicate for boolean fields is not supported. > > Jboss Forge generates the View Bean with search support using JPA criteria expressions for fields of type String and Entity objects but it does not for boolean fields. > Is this not supported? A bug? A feature request? Or simply that it's not possible to use boolean fields with JPA predicate isLike & equ -- 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-699) create a plugin for WildcardImportResolver

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-699?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III updated FORGE-699: ------------------------------------- Fix Version/s: 2.x Future (was: 1.x Future) > create a plugin for WildcardImportResolver > ------------------------------------------ > > Key: FORGE-699 > URL: https://issues.jboss.org/browse/FORGE-699 > Project: Forge > Issue Type: Feature Request > Components: Parsers / File Manipulation > Affects Versions: 1.1.1.Final > Reporter: fiorenzo pizza > Assignee: fiorenzo pizza > Fix For: 2.x Future > > > general notes > We need to create some WildcardImportResolver (Responsible for providing additional import resolution functionality for situations where classes have referenced a package or wild-card import) > summary: > - when start creation of index --> new-project > - when update the index --> re-open project | add|remove plugins to the project | add|remove maven dependencies | add|remove new class inside forge project > - where save the index --> always > - how information to save for future search --> className, jarName (null if the class is in the project), packageName, absoluteClassName > - how search inside the index --> (ram hashmap? ram db?) > - how generate new entry for the index --> cdi event > general considerations > 1) when forge create a new-project we should create some structure to add all classes used referenced by project > 2) we need to add all classes required from some plugin (persistence|scaffolding..) > 2) we need to add all classes inside maven dependencies > 3) we need to add all classes created in the project > 4) we need remove all deleted classes > 5) we need to remove all classes inside dependecies removed > 6) we need to update the index files, when forge project is reopen (the user could modify the project out of forge) > problems > 1) with a lot of jars, the indexing process should be slow!! > 2) how synchronize the access to index > 3) how we should synchronize of index update? > requirements > 1) we need some fast library to extract classes from jar files > 2) we should use cdi event to start a single jar indexing > HOW CREATE INDEX FROM JAR: > possibile libraries: jandex, tattletale, jarindexer > FIRST CANDIDATE: JANDEX > i started to hack jandex code, because jandex is very fast. > Jandex opens the jar files using java jar utilities: JarFile jar = new JarFile(jarFile); > and for every class generate a ClassInfo object: ClassInfo info = indexer.index(jar.getInputStream(entry)); > For my test, i removed some methods inside jandex: we don't care about annotations inside classes. Also i removed the generation of file index. > questions: > 1) why don't use H2, the Java SQL database, for memorize all informations about classes? > How memorize for a single class: > 1) classname, jar name (with version), package name, complete name -- 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-451) Warn a user if generating relationship CRUD screens and HashCode/Equals are missing

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-451?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III updated FORGE-451: ------------------------------------- Fix Version/s: 2.x Future (was: 1.x Future) > Warn a user if generating relationship CRUD screens and HashCode/Equals are missing > ----------------------------------------------------------------------------------- > > Key: FORGE-451 > URL: https://issues.jboss.org/browse/FORGE-451 > Project: Forge > Issue Type: Feature Request > Components: Scaffold > Affects Versions: 1.0.6.Final > Reporter: Pete Muir > Labels: Starter > Fix For: 2.x Future > > > It's necessary to provide these on the entities in order for drop downs to work. If not provided, there should be a WARN message. -- 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-163) Add ability to generate Entity Query classes with Persistence plugin (using Named Queries)

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-163?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III updated FORGE-163: ------------------------------------- Fix Version/s: 2.x Future (was: 1.x Future) > Add ability to generate Entity Query classes with Persistence plugin (using Named Queries) > ------------------------------------------------------------------------------------------ > > Key: FORGE-163 > URL: https://issues.jboss.org/browse/FORGE-163 > Project: Forge > Issue Type: Feature Request > Components: Builtin Plugins, Java EE APIs > Affects Versions: 1.0.0.Beta1 > Reporter: Jason Porter > Priority: Minor > Fix For: 2.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-924) It is not possible to set default values for incoming prompts or respond for prompts automatically in forge scripts.

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-924?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III updated FORGE-924: ------------------------------------- Fix Version/s: 2.0.0.Alpha14 (was: 1.x Future) > It is not possible to set default values for incoming prompts or respond for prompts automatically in forge scripts. > -------------------------------------------------------------------------------------------------------------------- > > Key: FORGE-924 > URL: https://issues.jboss.org/browse/FORGE-924 > Project: Forge > Issue Type: Feature Request > Components: Forge Scripting Language > Affects Versions: 1.3.0.Final > Reporter: Ãbner Oliveira > Fix For: 2.0.0.Alpha14 > > > I'm writing a script to server as a start point to a trainning session in my company. I had some problems because some plugins hava prompts for select versions and there is no way to automatize the process. > I asked for solution in the #forge channel and one solution was expose the queueInputLines in some way. > The simplest solution is change the plugins to expose arguments in the commands to allow set the default value for incoming prompts. -- 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-924) It is not possible to set default values for incoming prompts or respond for prompts automatically in forge scripts.

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-924?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III closed FORGE-924. ------------------------------------ Assignee: Lincoln Baxter III Resolution: Done Fixed with Forge 2 UI API. You may now set default values or callbacks on UIInputComponent types. > It is not possible to set default values for incoming prompts or respond for prompts automatically in forge scripts. > -------------------------------------------------------------------------------------------------------------------- > > Key: FORGE-924 > URL: https://issues.jboss.org/browse/FORGE-924 > Project: Forge > Issue Type: Feature Request > Components: Forge Scripting Language > Affects Versions: 1.3.0.Final > Reporter: Ãbner Oliveira > Assignee: Lincoln Baxter III > Fix For: 2.0.0.Alpha14 > > > I'm writing a script to server as a start point to a trainning session in my company. I had some problems because some plugins hava prompts for select versions and there is no way to automatize the process. > I asked for solution in the #forge channel and one solution was expose the queueInputLines in some way. > The simplest solution is change the plugins to expose arguments in the commands to allow set the default value for incoming prompts. -- 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-786) Scaffolds shouldn't be so hard reliant on JPA Entities

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-786?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III updated FORGE-786: ------------------------------------- Fix Version/s: 2.x Future (was: 1.x Future) > Scaffolds shouldn't be so hard reliant on JPA Entities > ------------------------------------------------------ > > Key: FORGE-786 > URL: https://issues.jboss.org/browse/FORGE-786 > Project: Forge > Issue Type: Feature Request > Components: Builtin Plugins > Affects Versions: 1.2.0.Final > Reporter: John Ament > Fix For: 2.x Future > > > Scaffolds are really nice, however they all need to work against JPA entities. What if you're not dealing with an entity, and instead have a data transformation layer that occurs first? HTML5/CSS3 type frameworks use rest and as a result the underlying object state may differ. Need to better support a scaffolding for non JPA entity classes. -- 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 November 2013