January 2016 - forge-issues - Jboss List Archives

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

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2316?page=com.atlassian.jira.plugin... ] George Gastaldi commented on FORGE-2316: ---------------------------------------- Thinking of adding this to the {{Project}} interface, wdyt? : {code:java} default Stack getStack() { StackBuilder stackBuilder = StackBuilder.stack("Project Stack"); for (StackFacet facet : getFacets(StackFacet.class)) { stackBuilder.includes(facet.getStack()); } return stackBuilder; } {code} > 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)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2574) Introduce ShellContext.getCommandLine()

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2574?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-2574. ---------------------------------- Fix Version/s: 3.0.0.Beta2 (was: 3.x Future) Assignee: George Gastaldi Resolution: Done > Introduce ShellContext.getCommandLine() > --------------------------------------- > > Key: FORGE-2574 > URL: https://issues.jboss.org/browse/FORGE-2574 > Project: Forge > Issue Type: Bug > Affects Versions: 3.0.0.Beta1 > Reporter: Claus Ibsen > Assignee: George Gastaldi > Fix For: 3.0.0.Beta2 > > > See ticket for background > https://github.com/fabric8io/fabric8/issues/5586 > We have noticed this happens when the addon command is using a wizard (steps). We have a command that depends on what Camel component you chose, has N+ steps with at most 20 options per step. The options is a mix between required=true or required=false options. However 98% is required=false. > What we have noticed is that if we provide all the nessasary information as arguments to the command, then no matter what, then forge turns on the interactive mode, and prompts the end users to select/enter values for all the options in the *LAST* step. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2574) Introduce ShellContext.getCommandLine()

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2574?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-2574: ----------------------------------- Summary: Introduce ShellContext.getCommandLine() (was: Executing an addon command from CLI and passing in all required options from command line, causes interactive mode regardless) > Introduce ShellContext.getCommandLine() > --------------------------------------- > > Key: FORGE-2574 > URL: https://issues.jboss.org/browse/FORGE-2574 > Project: Forge > Issue Type: Bug > Affects Versions: 3.0.0.Beta1 > Reporter: Claus Ibsen > Fix For: 3.0.0.Beta2 > > > See ticket for background > https://github.com/fabric8io/fabric8/issues/5586 > We have noticed this happens when the addon command is using a wizard (steps). We have a command that depends on what Camel component you chose, has N+ steps with at most 20 options per step. The options is a mix between required=true or required=false options. However 98% is required=false. > What we have noticed is that if we provide all the nessasary information as arguments to the command, then no matter what, then forge turns on the interactive mode, and prompts the end users to select/enter values for all the options in the *LAST* step. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2575) Upgrade to Roaster 2.18.0.Final

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2575?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-2575. ---------------------------------- Resolution: Done > Upgrade to Roaster 2.18.0.Final > ------------------------------- > > Key: FORGE-2575 > URL: https://issues.jboss.org/browse/FORGE-2575 > Project: Forge > Issue Type: Component Upgrade > Components: Parsers / File Manipulation > Affects Versions: 3.0.0.Beta1 > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 3.0.0.Beta2 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2574) Executing an addon command from CLI and passing in all required options from command line, causes interactive mode regardless

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2574?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-2574: ----------------------------------- Fix Version/s: 3.x Future > Executing an addon command from CLI and passing in all required options from command line, causes interactive mode regardless > ----------------------------------------------------------------------------------------------------------------------------- > > Key: FORGE-2574 > URL: https://issues.jboss.org/browse/FORGE-2574 > Project: Forge > Issue Type: Bug > Affects Versions: 3.0.0.Beta1 > Reporter: Claus Ibsen > Fix For: 3.x Future > > > See ticket for background > https://github.com/fabric8io/fabric8/issues/5586 > We have noticed this happens when the addon command is using a wizard (steps). We have a command that depends on what Camel component you chose, has N+ steps with at most 20 options per step. The options is a mix between required=true or required=false options. However 98% is required=false. > What we have noticed is that if we provide all the nessasary information as arguments to the command, then no matter what, then forge turns on the interactive mode, and prompts the end users to select/enter values for all the options in the *LAST* step. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2574) Executing an addon command from CLI and passing in all required options from command line, causes interactive mode regardless

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2574?page=com.atlassian.jira.plugin... ] George Gastaldi commented on FORGE-2574: ---------------------------------------- According to https://github.com/fabric8io/fabric8/issues/5586, it was decided to add an attribute in {{ShellContext}} specifying the provided arguments when the command is executed > Executing an addon command from CLI and passing in all required options from command line, causes interactive mode regardless > ----------------------------------------------------------------------------------------------------------------------------- > > Key: FORGE-2574 > URL: https://issues.jboss.org/browse/FORGE-2574 > Project: Forge > Issue Type: Bug > Affects Versions: 3.0.0.Beta1 > Reporter: Claus Ibsen > > See ticket for background > https://github.com/fabric8io/fabric8/issues/5586 > We have noticed this happens when the addon command is using a wizard (steps). We have a command that depends on what Camel component you chose, has N+ steps with at most 20 options per step. The options is a mix between required=true or required=false options. However 98% is required=false. > What we have noticed is that if we provide all the nessasary information as arguments to the command, then no matter what, then forge turns on the interactive mode, and prompts the end users to select/enter values for all the options in the *LAST* step. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2575) Upgrade to Roaster 2.18.0.Final

by George Gastaldi (JIRA)

George Gastaldi created FORGE-2575: -------------------------------------- Summary: Upgrade to Roaster 2.18.0.Final Key: FORGE-2575 URL: https://issues.jboss.org/browse/FORGE-2575 Project: Forge Issue Type: Component Upgrade Components: Parsers / File Manipulation Affects Versions: 3.0.0.Beta1 Reporter: George Gastaldi Assignee: George Gastaldi Fix For: 3.0.0.CR1 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ROASTER-90) implementInterface ignores basic types

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/ROASTER-90?page=com.atlassian.jira.plugin... ] George Gastaldi closed ROASTER-90. ---------------------------------- Resolution: Done > implementInterface ignores basic types > -------------------------------------- > > Key: ROASTER-90 > URL: https://issues.jboss.org/browse/ROASTER-90 > Project: Roaster > Issue Type: Bug > Components: JDT > Affects Versions: 2.17.4.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 2.18.0.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ROASTER-90) implementInterface ignores basic types

by George Gastaldi (JIRA)

George Gastaldi created ROASTER-90: -------------------------------------- Summary: implementInterface ignores basic types Key: ROASTER-90 URL: https://issues.jboss.org/browse/ROASTER-90 Project: Roaster Issue Type: Bug Components: JDT Affects Versions: 2.17.4.Final Reporter: George Gastaldi Assignee: George Gastaldi Fix For: 2.18.0.Final -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2574) Executing an addon command from CLI and passing in all required options from command line, causes interactive mode regardless

by Claus Ibsen (JIRA)

Claus Ibsen created FORGE-2574: ---------------------------------- Summary: Executing an addon command from CLI and passing in all required options from command line, causes interactive mode regardless Key: FORGE-2574 URL: https://issues.jboss.org/browse/FORGE-2574 Project: Forge Issue Type: Bug Affects Versions: 3.0.0.Beta1 Reporter: Claus Ibsen See ticket for background https://github.com/fabric8io/fabric8/issues/5586 We have noticed this happens when the addon command is using a wizard (steps). We have a command that depends on what Camel component you chose, has N+ steps with at most 20 options per step. The options is a mix between required=true or required=false options. However 98% is required=false. What we have noticed is that if we provide all the nessasary information as arguments to the command, then no matter what, then forge turns on the interactive mode, and prompts the end users to select/enter values for all the options in the *LAST* step. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 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 January 2016