October 2013 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-1247) Project Type should be Separated From Build System

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1247?page=com.atlassian.jira.plugin... ] Lincoln Baxter III updated FORGE-1247: -------------------------------------- Attachment: Screen Shot 2013-10-08 at 12.23.06 PM.png > Project Type should be Separated From Build System > -------------------------------------------------- > > Key: FORGE-1247 > URL: https://issues.jboss.org/browse/FORGE-1247 > Project: Forge > Issue Type: Feature Request > Components: Blessed Plugins, Build Tools - Gradle, Build Tools - Maven, Plugin API > Affects Versions: 2.0.0.Alpha13 > Reporter: Lincoln Baxter III > Fix For: 2.x Future > > Attachments: Screen Shot 2013-10-08 at 12.23.06 PM.png > > -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-989) Support rollback of installed addons

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-989?page=com.atlassian.jira.plugin.... ] George Gastaldi commented on FORGE-989: --------------------------------------- Usage of Git to manage the addon repository versioning is a solution > Support rollback of installed addons > ------------------------------------- > > Key: FORGE-989 > URL: https://issues.jboss.org/browse/FORGE-989 > Project: Forge > Issue Type: Feature Request > Components: Addon Manager > Affects Versions: 2.0.0.Alpha6 > Reporter: George Gastaldi > Assignee: George Gastaldi > Priority: Critical > Fix For: 2.x Future > > > After an installation is performed, it should be possible to revert the repository to a previous state. > It should be possible to log every install/remove request for each addon and group them by transaction savepoints. > Eg: > - Install Addon A which depends on B,C,D ( C and D already installed) > Log: > Transaction #1 > Addon A: INSTALLED > Addon B: INSTALLED > - Install Addon E which depends on A > Log: > Transaction #2 > Addon E: INSTALLED > Rollback of each transaction should have the following behavior: > - Rollback of Transaction #2 should remove Addon E. > - Rollback of Transaction #1 should remove A, B. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1251) Scaffolding should support generation of standalone forms/views

by Lincoln Baxter III (JIRA)

Lincoln Baxter III created FORGE-1251: ----------------------------------------- Summary: Scaffolding should support generation of standalone forms/views Key: FORGE-1251 URL: https://issues.jboss.org/browse/FORGE-1251 Project: Forge Issue Type: Feature Request Components: Scaffold Affects Versions: 2.0.0.Alpha13 Reporter: Lincoln Baxter III Fix For: 2.x Future Scaffolding is a bit monolithic at the moment. It should be possible to create a single Create/View/Edit/List/Search form from a JPA entity. The source and destination files should be selectable. The generation should not require the scaffold to be installed in a given project if possible. If a project is required, installation of dependencies or other source files should probably not be required (e.g. CSS files and other content should be optional.) I am really thinking about generating bare, un-styled pages here. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1250) All Java types are not necessarily MemberHolders

by Matt Benson (JIRA)

[ https://issues.jboss.org/browse/FORGE-1250?page=com.atlassian.jira.plugin... ] Work on FORGE-1250 started by Matt Benson. > All Java types are not necessarily MemberHolders > ------------------------------------------------ > > Key: FORGE-1250 > URL: https://issues.jboss.org/browse/FORGE-1250 > Project: Forge > Issue Type: Feature Request > Components: Parsers / File Manipulation > Affects Versions: 2.x Future > Reporter: Matt Benson > Assignee: Matt Benson > -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1250) All Java types are not necessarily MemberHolders

by Matt Benson (JIRA)

Matt Benson created FORGE-1250: ---------------------------------- Summary: All Java types are not necessarily MemberHolders Key: FORGE-1250 URL: https://issues.jboss.org/browse/FORGE-1250 Project: Forge Issue Type: Feature Request Components: Parsers / File Manipulation Affects Versions: 2.x Future Reporter: Matt Benson Assignee: Matt Benson -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1249) JavaAnnotationImpl should not implement InterfaceCapable

by Matt Benson (JIRA)

[ https://issues.jboss.org/browse/FORGE-1249?page=com.atlassian.jira.plugin... ] Matt Benson reassigned FORGE-1249: ---------------------------------- Assignee: Matt Benson > JavaAnnotationImpl should not implement InterfaceCapable > -------------------------------------------------------- > > Key: FORGE-1249 > URL: https://issues.jboss.org/browse/FORGE-1249 > Project: Forge > Issue Type: Feature Request > Components: Parsers / File Manipulation > Affects Versions: 2.x Future > Reporter: Matt Benson > Assignee: Matt Benson > -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1249) JavaAnnotationImpl should not implement InterfaceCapable

by Matt Benson (JIRA)

[ https://issues.jboss.org/browse/FORGE-1249?page=com.atlassian.jira.plugin... ] Work on FORGE-1249 started by Matt Benson. > JavaAnnotationImpl should not implement InterfaceCapable > -------------------------------------------------------- > > Key: FORGE-1249 > URL: https://issues.jboss.org/browse/FORGE-1249 > Project: Forge > Issue Type: Feature Request > Components: Parsers / File Manipulation > Affects Versions: 2.x Future > Reporter: Matt Benson > Assignee: Matt Benson > -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1249) JavaAnnotationImpl should not implement InterfaceCapable

by Matt Benson (JIRA)

Matt Benson created FORGE-1249: ---------------------------------- Summary: JavaAnnotationImpl should not implement InterfaceCapable Key: FORGE-1249 URL: https://issues.jboss.org/browse/FORGE-1249 Project: Forge Issue Type: Feature Request Components: Parsers / File Manipulation Affects Versions: 2.x Future Reporter: Matt Benson -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-796) Refactor JavaParser to distinguish between Mutable and Immutable Type Models in a typesafe way

by Matt Benson (JIRA)

[ https://issues.jboss.org/browse/FORGE-796?page=com.atlassian.jira.plugin.... ] Matt Benson commented on FORGE-796: ----------------------------------- Interested parties please see https://github.com/forge/java-parser/tree/refactor-hierarchy where the proposed API for java-parser v2 is under construction; the basic overview of changes is: * extract read functionality from {{JavaSource}} to a new {{JavaType}} interface * {{JavaSource}} moved to package {{org.jboss.forge.parser.java.source}} * for a given interface {{org.jboss.forge.parser.java.*}}, extract write functionality to {{org.jboss.forge.parser.java.source.*Source}} e.g., {{org.jboss.forge.parser.java.JavaClass}} now contains read functionality only and {{org.jboss.forge.parser.java.source.JavaClassSource}} is now the equivalent of the old RW interface. Additionally the {{JavaParserProvider}} interface has been greatly simplified and the {{JavaParser}} API entry-point has been modified to use {{java.util.ServiceLoader}} and take over the input overloading duties that were formerly the responsibility of a {{JavaParserProvider}} implementation. > Refactor JavaParser to distinguish between Mutable and Immutable Type Models in a typesafe way > ---------------------------------------------------------------------------------------------- > > Key: FORGE-796 > URL: https://issues.jboss.org/browse/FORGE-796 > Project: Forge > Issue Type: Feature Request > Components: Parsers / File Manipulation > Reporter: Lincoln Baxter III > Assignee: Matt Benson > Fix For: 2.0.0.Final > > > The Java Parser Type Hierarchy should support Read-only and writeable Types. Thus we could implement the Parser using things like Java Reflection for Read-only access, or with Javassist CtClass / Apache BCEL for reading and writing .class files. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-796) Refactor JavaParser to distinguish between Mutable and Immutable Type Models in a typesafe way

by Matt Benson (JIRA)

[ https://issues.jboss.org/browse/FORGE-796?page=com.atlassian.jira.plugin.... ] Matt Benson reassigned FORGE-796: --------------------------------- Assignee: Matt Benson > Refactor JavaParser to distinguish between Mutable and Immutable Type Models in a typesafe way > ---------------------------------------------------------------------------------------------- > > Key: FORGE-796 > URL: https://issues.jboss.org/browse/FORGE-796 > Project: Forge > Issue Type: Feature Request > Components: Parsers / File Manipulation > Reporter: Lincoln Baxter III > Assignee: Matt Benson > Fix For: 2.0.0.Final > > > The Java Parser Type Hierarchy should support Read-only and writeable Types. Thus we could implement the Parser using things like Java Reflection for Read-only access, or with Javassist CtClass / Apache BCEL for reading and writing .class files. -- 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, 6 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues October 2013