January 2016 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-957) Create "Stacks" addon, that allows providing stack implementations to supply default values in dialogs

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-957?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-957: ---------------------------------- Fix Version/s: (was: 3.0.0.CR1) > Create "Stacks" addon, that allows providing stack implementations to supply default values in dialogs > ------------------------------------------------------------------------------------------------------ > > Key: FORGE-957 > URL: https://issues.jboss.org/browse/FORGE-957 > Project: Forge > Issue Type: Feature Request > Components: Blessed Plugins > Affects Versions: 2.0.0.Alpha5 > Reporter: Lincoln Baxter III > Assignee: George Gastaldi > > This will allow things like, detecting that the user is on Wildfly AS, and subsequently selecting appropriate versions of specifications, libraries, and other setup configurations. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-957) Create "Stacks" addon, that allows providing stack implementations to supply default values in dialogs

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-957?page=com.atlassian.jira.plugin.... ] George Gastaldi reopened FORGE-957: ----------------------------------- > Create "Stacks" addon, that allows providing stack implementations to supply default values in dialogs > ------------------------------------------------------------------------------------------------------ > > Key: FORGE-957 > URL: https://issues.jboss.org/browse/FORGE-957 > Project: Forge > Issue Type: Feature Request > Components: Blessed Plugins > Affects Versions: 2.0.0.Alpha5 > Reporter: Lincoln Baxter III > Assignee: George Gastaldi > Fix For: 3.0.0.CR1 > > > This will allow things like, detecting that the user is on Wildfly AS, and subsequently selecting appropriate versions of specifications, libraries, and other setup configurations. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-957) Create "Stacks" addon, that allows providing stack implementations to supply default values in dialogs

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-957?page=com.atlassian.jira.plugin.... ] George Gastaldi closed FORGE-957. --------------------------------- Fix Version/s: 3.0.0.CR1 (was: 3.x Future) Assignee: George Gastaldi Resolution: Won't Do Closing this issue as "Won't Do", since it makes more sense to add this feature in the projects addon > Create "Stacks" addon, that allows providing stack implementations to supply default values in dialogs > ------------------------------------------------------------------------------------------------------ > > Key: FORGE-957 > URL: https://issues.jboss.org/browse/FORGE-957 > Project: Forge > Issue Type: Feature Request > Components: Blessed Plugins > Affects Versions: 2.0.0.Alpha5 > Reporter: Lincoln Baxter III > Assignee: George Gastaldi > Fix For: 3.0.0.CR1 > > > This will allow things like, detecting that the user is on Wildfly AS, and subsequently selecting appropriate versions of specifications, libraries, and other setup configurations. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-957) Create "Stacks" addon, that allows providing stack implementations to supply default values in dialogs

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-957?page=com.atlassian.jira.plugin.... ] George Gastaldi closed FORGE-957. --------------------------------- Resolution: Done > Create "Stacks" addon, that allows providing stack implementations to supply default values in dialogs > ------------------------------------------------------------------------------------------------------ > > Key: FORGE-957 > URL: https://issues.jboss.org/browse/FORGE-957 > Project: Forge > Issue Type: Feature Request > Components: Blessed Plugins > Affects Versions: 2.0.0.Alpha5 > Reporter: Lincoln Baxter III > Assignee: George Gastaldi > > This will allow things like, detecting that the user is on Wildfly AS, and subsequently selecting appropriate versions of specifications, libraries, and other setup configurations. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2316) Brainstorming on introducing "Stacks"

by Anonymous (JIRA)

[ https://issues.jboss.org/browse/FORGE-2316?page=com.atlassian.jira.plugin... ] Issue was automatically transitioned when George Gastaldi created pull request #592 in GitHub --------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Brainstorming on introducing "Stacks" > ------------------------------------- > > Key: FORGE-2316 > URL: https://issues.jboss.org/browse/FORGE-2316 > Project: Forge > Issue Type: Sub-task > Reporter: Antonio Goncalves > Fix For: 3.x Future > > > At the moment Forge generates code without having a real notion of a technical stack. For example, creating a JPA Entity for a Java EE 6 application could be different from a Java EE 7 application : > * The {{persistence.xml}} version if different (2.0 / 2.1) > * The {{properties}} are different (e.g. schema generation in 2.1) > * The syntax is different ({{List<MyEntity> m = new ArrayList<MyEntity>}} while it could use diamond syntax for a Java EE 7 stack) > The stack could be choosen when the project is created : > * {{project-new --named myproj}} : let's the developper use Forge without any special stack > * {{project-new --named myproj --stack JavaEE7}} : the generated code will follow Java EE 7 > h3. Possible stacks > A stack would bundle certain facets. Therefore we could have as many stacks as needed. As an example, we could have the following stacks : > * Java EE 6 : JPA 2.0, CDI 1.0, JSF 2.0, Bean Validation 1.0, JTA 1.1 > * Java EE 7 : JPA 2.1, CDI 1.1, JSF 2.2, Bean Validation 1.1, JTA 1.2, Batch 1.0 > * Micro Java EE 7 Service: JPA 2.1, CDI 1.1, JSF 2.2, Bean Validation 1.1, JTA 1.2, Batch 1.0 (but with special Microservice configuration) > * Java EE 8 : JPA 2.1, CDI 2.0, JSF 2.3, Bean Validation 1.2, JTA 1.2, Batch 1.0, JCache 1.1, MVC 1.0 > * Spring 3.x > * Spring 4.x > * .... > h3. Differences in having stacks > h4. Filtering commands > When you pick up a Stack, it gives you access or not to certain commands. For example, if you create a project with a Java EE 6 stack, you won't have access to any Batch, MVC... commands > {code:title=Java EE 6 stack} > $ project-new --named myproj --stack JavaEE6 > $ jpa-new-entity --named MyEntity > {code} > {code:title=Java EE 7 stack} > $ project-new --named myproj --stack JavaEE7 > $ jpa-new-entity --named MyEntity > $ mvc-new-controller --named MyController // only available on EE7 > {code} > h4. Setting up command versions > When you pick up a Stack, it filters the commands that have the right version for the right stack. For example, if you create a Java EE 6 stack, you will get JPA 2.0 commands, for a Java EE 7 stack, the JPA 2.1 commands. Also, the {{version}} parameters will be disabled > {code:title=No stack} > $ project-new --named myproj > $ jpa-new-entity --named MyEntity --jpaVersion 2.1 > $ cdi-new-bean --named MyBean --cdiVersion 1.1 > {code} > {code:title=Java EE 6 stack} > $ project-new --named myproj --stack JavaEE6 > $ jpa-new-entity --named MyEntity // no --jpaVersion because it is automatically set to 2.0 > {code} > {code:title=Java EE 7 stack} > $ project-new --named myproj --stack JavaEE7 > $ jpa-new-entity --named MyEntity // no --jpaVersion because it is automatically set to 2.1 > $ jpa-new-converter --named MyConvert // JPA Converters are only available in 2.1 > {code} > h4. API to define a Stack > A stack could be defined with a fluent API such as : > {code} > stack("JavaEE7").includes(JavaEE7Facet).includes(JPA2.1Facet).excludes(SpringFacet) > stack("JavaEE7").includes(JavaEE7Facet).includes(JPA2.1Facet).allowsFeature(WildflySwarm) > stack("MyOwnStacks").includes(JavaEE7Stack).includes(MyFacet).includes(YourFacet) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2316) Brainstorming on introducing "Stacks"

by Jess Sightler (JIRA)

[ https://issues.jboss.org/browse/FORGE-2316?page=com.atlassian.jira.plugin... ] Jess Sightler commented on FORGE-2316: -------------------------------------- The JIRA states that the version parameter will be disabled. I am not sure that is exactly the right thing to do. It might be desirable in some cases to target one stack (eg, EE 7), but generate an entity for an older stack that is backwards compatible. Maybe a warning would be better in this case? > Brainstorming on introducing "Stacks" > ------------------------------------- > > Key: FORGE-2316 > URL: https://issues.jboss.org/browse/FORGE-2316 > Project: Forge > Issue Type: Sub-task > Reporter: Antonio Goncalves > Fix For: 3.x Future > > > At the moment Forge generates code without having a real notion of a technical stack. For example, creating a JPA Entity for a Java EE 6 application could be different from a Java EE 7 application : > * The {{persistence.xml}} version if different (2.0 / 2.1) > * The {{properties}} are different (e.g. schema generation in 2.1) > * The syntax is different ({{List<MyEntity> m = new ArrayList<MyEntity>}} while it could use diamond syntax for a Java EE 7 stack) > The stack could be choosen when the project is created : > * {{project-new --named myproj}} : let's the developper use Forge without any special stack > * {{project-new --named myproj --stack JavaEE7}} : the generated code will follow Java EE 7 > h3. Possible stacks > A stack would bundle certain facets. Therefore we could have as many stacks as needed. As an example, we could have the following stacks : > * Java EE 6 : JPA 2.0, CDI 1.0, JSF 2.0, Bean Validation 1.0, JTA 1.1 > * Java EE 7 : JPA 2.1, CDI 1.1, JSF 2.2, Bean Validation 1.1, JTA 1.2, Batch 1.0 > * Micro Java EE 7 Service: JPA 2.1, CDI 1.1, JSF 2.2, Bean Validation 1.1, JTA 1.2, Batch 1.0 (but with special Microservice configuration) > * Java EE 8 : JPA 2.1, CDI 2.0, JSF 2.3, Bean Validation 1.2, JTA 1.2, Batch 1.0, JCache 1.1, MVC 1.0 > * Spring 3.x > * Spring 4.x > * .... > h3. Differences in having stacks > h4. Filtering commands > When you pick up a Stack, it gives you access or not to certain commands. For example, if you create a project with a Java EE 6 stack, you won't have access to any Batch, MVC... commands > {code:title=Java EE 6 stack} > $ project-new --named myproj --stack JavaEE6 > $ jpa-new-entity --named MyEntity > {code} > {code:title=Java EE 7 stack} > $ project-new --named myproj --stack JavaEE7 > $ jpa-new-entity --named MyEntity > $ mvc-new-controller --named MyController // only available on EE7 > {code} > h4. Setting up command versions > When you pick up a Stack, it filters the commands that have the right version for the right stack. For example, if you create a Java EE 6 stack, you will get JPA 2.0 commands, for a Java EE 7 stack, the JPA 2.1 commands. Also, the {{version}} parameters will be disabled > {code:title=No stack} > $ project-new --named myproj > $ jpa-new-entity --named MyEntity --jpaVersion 2.1 > $ cdi-new-bean --named MyBean --cdiVersion 1.1 > {code} > {code:title=Java EE 6 stack} > $ project-new --named myproj --stack JavaEE6 > $ jpa-new-entity --named MyEntity // no --jpaVersion because it is automatically set to 2.0 > {code} > {code:title=Java EE 7 stack} > $ project-new --named myproj --stack JavaEE7 > $ jpa-new-entity --named MyEntity // no --jpaVersion because it is automatically set to 2.1 > $ jpa-new-converter --named MyConvert // JPA Converters are only available in 2.1 > {code} > h4. API to define a Stack > A stack could be defined with a fluent API such as : > {code} > stack("JavaEE7").includes(JavaEE7Facet).includes(JPA2.1Facet).excludes(SpringFacet) > stack("JavaEE7").includes(JavaEE7Facet).includes(JPA2.1Facet).allowsFeature(WildflySwarm) > stack("MyOwnStacks").includes(JavaEE7Stack).includes(MyFacet).includes(YourFacet) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2573) Introduce Optional<F> Faceted.getFacetAsOptional(Class<F>)

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2573?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-2573. ---------------------------------- Resolution: Done > Introduce Optional<F> Faceted.getFacetAsOptional(Class<F>) > ---------------------------------------------------------- > > Key: FORGE-2573 > URL: https://issues.jboss.org/browse/FORGE-2573 > Project: Forge > Issue Type: Enhancement > Components: Facets > Affects Versions: 3.0.0.Beta1 > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 3.0.0.CR1 > > > It would be nice to have a method that would return a JDK 8's {{java.util.Optional}} when getting a facet -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2573) Introduce Optional<F> Faceted.getOptionalFacet(Class<F>)

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2573?page=com.atlassian.jira.plugin... ] George Gastaldi reopened FORGE-2573: ------------------------------------ > Introduce Optional<F> Faceted.getOptionalFacet(Class<F>) > -------------------------------------------------------- > > Key: FORGE-2573 > URL: https://issues.jboss.org/browse/FORGE-2573 > Project: Forge > Issue Type: Enhancement > Components: Facets > Affects Versions: 3.0.0.Beta1 > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 3.0.0.CR1 > > > It would be nice to have a method that would return a JDK 8's {{java.util.Optional}} when getting a facet -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2573) Introduce Optional<F> Faceted.getFacetAsOptional(Class<F>)

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2573?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-2573: ----------------------------------- Summary: Introduce Optional<F> Faceted.getFacetAsOptional(Class<F>) (was: Introduce Optional<F> Faceted.getOptionalFacet(Class<F>)) > Introduce Optional<F> Faceted.getFacetAsOptional(Class<F>) > ---------------------------------------------------------- > > Key: FORGE-2573 > URL: https://issues.jboss.org/browse/FORGE-2573 > Project: Forge > Issue Type: Enhancement > Components: Facets > Affects Versions: 3.0.0.Beta1 > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 3.0.0.CR1 > > > It would be nice to have a method that would return a JDK 8's {{java.util.Optional}} when getting a facet -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2573) Introduce Optional<F> Faceted.getOptionalFacet(Class<F>)

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2573?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-2573. ---------------------------------- Resolution: Done > Introduce Optional<F> Faceted.getOptionalFacet(Class<F>) > -------------------------------------------------------- > > Key: FORGE-2573 > URL: https://issues.jboss.org/browse/FORGE-2573 > Project: Forge > Issue Type: Enhancement > Components: Facets > Affects Versions: 3.0.0.Beta1 > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 3.0.0.CR1 > > > It would be nice to have a method that would return a JDK 8's {{java.util.Optional}} when getting a facet -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues January 2016