February 2013 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-609) @RequiresFacet and @RequiresProject should be Interceptor bindings instead of static constraints.

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-609?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-609: ---------------------------------- Fix Version/s: 1.2.2.Final (was: 1.2.1.Final) > @RequiresFacet and @RequiresProject should be Interceptor bindings instead of static constraints. > ------------------------------------------------------------------------------------------------- > > Key: FORGE-609 > URL: https://issues.jboss.org/browse/FORGE-609 > Project: Forge > Issue Type: Enhancement > Components: Plugin API, Shell > Affects Versions: 1.0.5.Final > Reporter: Lincoln Baxter III > Fix For: 1.2.2.Final > > > This would also incorporate FORGE-214, since these constraints could now be used on any bean Class or method. -- 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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-662) Faces scaffold should display a message after saving entities

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-662?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-662: ---------------------------------- Fix Version/s: 1.2.2.Final (was: 1.2.1.Final) > Faces 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: 1.2.2.Final > > > 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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-665) JavaParser should support TypeSafe parsing/generation of method bodies/statements

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-665?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-665: ---------------------------------- Fix Version/s: 1.2.2.Final (was: 1.2.1.Final) > JavaParser should support TypeSafe parsing/generation of method bodies/statements > --------------------------------------------------------------------------------- > > Key: FORGE-665 > URL: https://issues.jboss.org/browse/FORGE-665 > Project: Forge > Issue Type: Enhancement > Components: Parsers / File Manipulation > Affects Versions: 1.0.6.Final > Reporter: Lincoln Baxter III > Fix For: 1.2.2.Final > > > The JavaParser needs to support fine-grained manipulation of method bodies. -- 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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-659) MovePlugin fails while moving java classes

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-659?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-659: ---------------------------------- Fix Version/s: 1.2.2.Final (was: 1.2.1.Final) > MovePlugin fails while moving java classes > ------------------------------------------ > > Key: FORGE-659 > URL: https://issues.jboss.org/browse/FORGE-659 > Project: Forge > Issue Type: Bug > Components: Builtin Plugins > Reporter: George Gastaldi > Labels: annoying > Fix For: 1.2.2.Final > > > Having a class in a package, when you try to move that class to another package, the following error is thrown: > {code:java} > [exemplo] model $ ls > Cidade.java UnidadeFederativa.java > [exemplo] model $ mv Cidade.java ex01/Cidade.java > ***ERROR*** [mv] no such child: null > {code} > Probably we should give a better description, or say that this feature isn't supported yet. > Moving a class to another package includes refactoring the whole project, in order to avoid compilation errors. -- 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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-604) Add support for Java EE 6 Full Profile

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-604?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-604: ---------------------------------- Fix Version/s: 1.2.2.Final (was: 1.2.1.Final) > Add support for Java EE 6 Full Profile > -------------------------------------- > > Key: FORGE-604 > URL: https://issues.jboss.org/browse/FORGE-604 > Project: Forge > Issue Type: Task > Components: Java EE APIs > Affects Versions: 1.0.5.Final > Environment: All > Reporter: Christopher Volk > Fix For: 1.2.2.Final > > > Add support for Java EE 6 Full profile, including multi-module support (cli/maven/ear) and EAR packaging. > The EAR packaging should be fairly "easy" to implement. The maven side of multi-module should be similarly "easy". CLI multi-module support is something I would expect to take up most of this effort. > I believe this to be a critical feature - serious enterprise software requires Full Profile, and Forge would be even more useful for bootstrapping and developing against the Full Profile than even the Web Profile. I know that almost all the apps I work on professionally require Full Profile. > This would be a real home run, IMHO, especially in the wake of JBoss AS7.1's Full Profile Compliance :-) -- 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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-782) Forge should support multiple repositories

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-782?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-782: ---------------------------------- Fix Version/s: 1.2.2.Final (was: 1.2.1.Final) > Forge should support multiple repositories > ------------------------------------------ > > Key: FORGE-782 > URL: https://issues.jboss.org/browse/FORGE-782 > Project: Forge > Issue Type: Feature Request > Components: Plugin Repository > Affects Versions: 1.2.0.Final > Reporter: John Ament > Fix For: 1.2.2.Final > > > Forge currently has a DEFAULT_PLUGIN_REPO but no way to have additional plugin repos. It should be possible for companies to have internal repositories for plugins that may not be open source. > Workaround right now is to copy the yaml file locally and add other proprietary plugins to it. -- 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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-679) Add a step explaining how to import and use the Forge code formatter

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-679?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-679: ---------------------------------- Fix Version/s: 1.2.2.Final (was: 1.2.1.Final) > Add a step explaining how to import and use the Forge code formatter > -------------------------------------------------------------------- > > Key: FORGE-679 > URL: https://issues.jboss.org/browse/FORGE-679 > Project: Forge > Issue Type: Task > Components: Website > Reporter: George Gastaldi > Fix For: 1.2.2.Final > > > In http://forge.jboss.org/docs/get_involved/contribute.html there is a step missing about using the Forge code formatter in Eclipse -- 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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-693) Need an auto-update feature for plugins

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-693?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-693: ---------------------------------- Fix Version/s: 1.2.2.Final (was: 1.2.1.Final) > Need an auto-update feature for plugins > --------------------------------------- > > Key: FORGE-693 > URL: https://issues.jboss.org/browse/FORGE-693 > Project: Forge > Issue Type: Feature Request > Reporter: George Gastaldi > Fix For: 1.2.2.Final > > > FORGE-217 auto-updates the core and the core plugins. There should be a way to update the current installed plugins. > Depending on the time taken to check, this could be done in the Forge startup. -- 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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-715) Error while working with resources named as Java/FSH keywords

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-715?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-715: ---------------------------------- Fix Version/s: 1.2.2.Final (was: 1.2.1.Final) > Error while working with resources named as Java/FSH keywords > ------------------------------------------------------------- > > Key: FORGE-715 > URL: https://issues.jboss.org/browse/FORGE-715 > Project: Forge > Issue Type: Bug > Components: Forge Scripting Language, Shell > Affects Versions: 1.1.2.Final > Reporter: George Gastaldi > Labels: annoying > Fix For: 1.2.2.Final > > > Type the following: > {code} > cd for > {code} > The following error is thrown > {code} > ***ERROR*** Exception encountered: 6 (type "set VERBOSE true" to enable stack traces) > {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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-699) create a plugin for WildcardImportResolver

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-699?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-699: ---------------------------------- Fix Version/s: 1.2.2.Final (was: 1.2.1.Final) > create a plugin for WildcardImportResolver > ------------------------------------------ > > Key: FORGE-699 > URL: https://issues.jboss.org/browse/FORGE-699 > Project: Forge > Issue Type: Story > Components: Parsers / File Manipulation > Affects Versions: 1.1.1.Final > Reporter: fiorenzo pizza > Assignee: fiorenzo pizza > Fix For: 1.2.2.Final > > > 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

13 years, 3 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues February 2013