June 2015 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-2353) Check if we have all the needed Facets for Java EE 6 and Java EE 7 projects

by Antonio Goncalves (JIRA)

Antonio Goncalves created FORGE-2353: ---------------------------------------- Summary: Check if we have all the needed Facets for Java EE 6 and Java EE 7 projects Key: FORGE-2353 URL: https://issues.jboss.org/browse/FORGE-2353 Project: Forge Issue Type: Sub-task Components: Java EE Affects Versions: 2.16.1.Final Reporter: Antonio Goncalves Assignee: Antonio Goncalves Fix For: 2.x Future JPA 2.0, 2.1, EJB 3.0, 3.1, Servlet 3.0, 3.1...... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

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

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-2316?page=com.atlassian.jira.plugin... ] Antonio Goncalves commented on FORGE-2316: ------------------------------------------ See https://github.com/jboss-developer/jboss-stacks > Brainstorming on introducing "Stacks" > ------------------------------------- > > Key: FORGE-2316 > URL: https://issues.jboss.org/browse/FORGE-2316 > Project: Forge > Issue Type: Task > Reporter: Antonio Goncalves > Fix For: 2.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} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2352) JPA: New Field creates an unknown B type for byte[] types

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2352?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-2352. ---------------------------------- Fix Version/s: 2.16.2.Final (was: 2.x Future) Resolution: Done > JPA: New Field creates an unknown B type for byte[] types > --------------------------------------------------------- > > Key: FORGE-2352 > URL: https://issues.jboss.org/browse/FORGE-2352 > Project: Forge > Issue Type: Bug > Components: Java EE > Affects Versions: 2.16.1.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Priority: Critical > Fix For: 2.16.2.Final > > > When running {{jpa-new-field --named blob_field --type byte[] --lob}} in a JPA entity, the generated field is > {code:java} > @Lob > @Column(length = 2147483647) > private B blob_field; > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2352) JPA: New Field creates an unknown B type for byte[] types

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2352?page=com.atlassian.jira.plugin... ] Work on FORGE-2352 started by George Gastaldi. ---------------------------------------------- > JPA: New Field creates an unknown B type for byte[] types > --------------------------------------------------------- > > Key: FORGE-2352 > URL: https://issues.jboss.org/browse/FORGE-2352 > Project: Forge > Issue Type: Bug > Components: Java EE > Affects Versions: 2.16.1.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Priority: Critical > Fix For: 2.x Future > > > When running {{jpa-new-field --named blob_field --type byte[] --lob}} in a JPA entity, the generated field is > {code:java} > @Lob > @Column(length = 2147483647) > private B blob_field; > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2352) JPA: New Field creates an unknown B type for byte[] types

by George Gastaldi (JIRA)

George Gastaldi created FORGE-2352: -------------------------------------- Summary: JPA: New Field creates an unknown B type for byte[] types Key: FORGE-2352 URL: https://issues.jboss.org/browse/FORGE-2352 Project: Forge Issue Type: Bug Components: Java EE Affects Versions: 2.16.1.Final Reporter: George Gastaldi Assignee: George Gastaldi Priority: Critical Fix For: 2.x Future When running {{jpa-new-field --named blob_field --type byte[] --lob}} in a JPA entity, the generated field is {code:java} @Lob @Column(length = 2147483647) private B blob_field; {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2351) addon-add-dependency fails to autocomplete

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2351?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-2351. ---------------------------------- Resolution: Done > addon-add-dependency fails to autocomplete > ------------------------------------------ > > Key: FORGE-2351 > URL: https://issues.jboss.org/browse/FORGE-2351 > Project: Forge > Issue Type: Feature Request > Components: Addon Development > Affects Versions: 2.16.1.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 2.16.2.Final > > > {quote} > <agoncal> BTW I couldn't make addon-add-dependency work > <gastaldi> addon-add-dependency --addon org.jboss.forge.addon:projects,2.16.1.Final > <agoncal> Pressing TAB I can get as far as "addon-add-dependency --addon org." and then, no completion after "org." > <gastaldi> ah yes > <gastaldi> I see that too > <agoncal> gastaldi Good. Works if I type the entire line > {quote} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2351) addon-add-dependency fails to autocomplete

by George Gastaldi (JIRA)

George Gastaldi created FORGE-2351: -------------------------------------- Summary: addon-add-dependency fails to autocomplete Key: FORGE-2351 URL: https://issues.jboss.org/browse/FORGE-2351 Project: Forge Issue Type: Feature Request Components: Addon Development Affects Versions: 2.16.1.Final Reporter: George Gastaldi Assignee: George Gastaldi Fix For: 2.16.2.Final {quote} <agoncal> BTW I couldn't make addon-add-dependency work <gastaldi> addon-add-dependency --addon org.jboss.forge.addon:projects,2.16.1.Final <agoncal> Pressing TAB I can get as far as "addon-add-dependency --addon org." and then, no completion after "org." <gastaldi> ah yes <gastaldi> I see that too <agoncal> gastaldi Good. Works if I type the entire line {quote} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2349) maven-jar-plugin version should be set when creating an addon

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2349?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-2349. ---------------------------------- Assignee: George Gastaldi Fix Version/s: 2.16.2.Final (was: 2.x Future) Resolution: Done > maven-jar-plugin version should be set when creating an addon > ------------------------------------------------------------- > > Key: FORGE-2349 > URL: https://issues.jboss.org/browse/FORGE-2349 > Project: Forge > Issue Type: Enhancement > Components: Addon Development > Affects Versions: 2.16.1.Final > Reporter: Antonio Goncalves > Assignee: George Gastaldi > Fix For: 2.16.2.Final > > > When creating an addon with the command : > {code} > project-new --named helloAddon --type addon > {code} > The version of the {{maven-jar-plugin}} is not set : > {code} > <build> > <finalName>helloAddon</finalName> > <plugins> > <plugin> > <artifactId>maven-jar-plugin</artifactId> > <executions> > ... > {code} > The Maven waring tells us to set a version : > {code} > [WARNING] Some problems were encountered while building the effective model for org.helloAddon:helloAddon:jar:1.0.0-SNAPSHOT > [WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-jar-plugin is missing. @ line 52, column 15 > [WARNING] > [WARNING] It is highly recommended to fix these problems because they threaten the stability of your build. > {code} > [At the moment it's 2.6|http://mvnrepository.com/artifact/org.apache.maven.plugins/maven-jar-...] -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2350) In addon-new-annotated-ui-command name should be renamed to named

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2350?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-2350. ---------------------------------- Assignee: George Gastaldi Fix Version/s: 2.16.2.Final (was: 2.x Future) Resolution: Done > In addon-new-annotated-ui-command name should be renamed to named > ----------------------------------------------------------------- > > Key: FORGE-2350 > URL: https://issues.jboss.org/browse/FORGE-2350 > Project: Forge > Issue Type: Sub-task > Components: UI - API > Affects Versions: 2.16.1.Final > Reporter: Antonio Goncalves > Assignee: George Gastaldi > Fix For: 2.16.2.Final > > > In all the commands, the name is always called {{named}} but not in {{addon-new-annotated-ui-command}} where it is called {{commandName}}. It should be renamed : > {code} > addon-new-annotated-ui-command --named myCommand > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2350) In addon-new-annotated-ui-command name should be renamed to named

by Antonio Goncalves (JIRA)

Antonio Goncalves created FORGE-2350: ---------------------------------------- Summary: In addon-new-annotated-ui-command name should be renamed to named Key: FORGE-2350 URL: https://issues.jboss.org/browse/FORGE-2350 Project: Forge Issue Type: Sub-task Components: UI - API Affects Versions: 2.16.1.Final Reporter: Antonio Goncalves Fix For: 2.x Future In all the commands, the name is always called {{named}} but not in {{addon-new-annotated-ui-command}} where it is called {{commandName}}. It should be renamed : {code} addon-new-annotated-ui-command --named myCommand {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues June 2015