February 2015 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-2079) Being able to create a new CDI producer field

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-2079?page=com.atlassian.jira.plugin... ] Antonio Goncalves updated FORGE-2079: ------------------------------------- Description: It would be good to have a command to add a CDI producer field to an existing class. A simple command such as : {code} cdi-add-producer-field --named em --type javax.persistence.EntityManager {code} Would generate : {code} public class DatabaseProducer { @Produces private EntityManager em; } {code} Then, we can have more attributes : {code} cdi-add-producer-field --named em --type javax.persistence.EntityManager --qualifier Production --alternative=true --scoped Request --atNamed=true {code} {code} public class DatabaseProducer { @Produces @Production @Alternative @RequestScoped @Named private EntityManager em; } {code} was: It would be good to have a command to add a CDI producer field to an existing class. A simple command such as : {code} cdi-new-producer-field --named em --type javax.persistence.EntityManager {code} Would generate : {code} public class DatabaseProducer { @Produces private EntityManager em; } {code} Then, we can have more attributes : {code} cdi-new-producer-field --named em --type javax.persistence.EntityManager --qualifier Production --alternative=true --scoped Request --atNamed=true {code} {code} public class DatabaseProducer { @Produces @Production @Alternative @RequestScoped @Named private EntityManager em; } {code} > Being able to create a new CDI producer field > --------------------------------------------- > > Key: FORGE-2079 > URL: https://issues.jboss.org/browse/FORGE-2079 > Project: Forge > Issue Type: Sub-task > Components: Java EE > Affects Versions: 2.12.1.Final > Reporter: Antonio Goncalves > Fix For: 2.x Future > > > It would be good to have a command to add a CDI producer field to an existing class. A simple command such as : > {code} > cdi-add-producer-field --named em --type javax.persistence.EntityManager > {code} > Would generate : > {code} > public class DatabaseProducer > { > @Produces > private EntityManager em; > } > {code} > Then, we can have more attributes : > {code} > cdi-add-producer-field --named em --type javax.persistence.EntityManager --qualifier Production --alternative=true --scoped Request --atNamed=true > {code} > {code} > public class DatabaseProducer > { > @Produces > @Production > @Alternative > @RequestScoped > @Named > private EntityManager em; > } > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (FORGE-2232) Documenting how to create and test a command that creates Java code

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-2232?page=com.atlassian.jira.plugin... ] Antonio Goncalves reassigned FORGE-2232: ---------------------------------------- Assignee: George Gastaldi > Documenting how to create and test a command that creates Java code > ------------------------------------------------------------------- > > Key: FORGE-2232 > URL: https://issues.jboss.org/browse/FORGE-2232 > Project: Forge > Issue Type: Sub-task > Components: Documentation > Affects Versions: 2.14.0.Final > Reporter: Antonio Goncalves > Assignee: George Gastaldi > Fix For: 2.x Future > > > A {{new}} command -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (FORGE-2235) Documenting how to create and test a command that scaffolds code

by Antonio Goncalves (JIRA)

Antonio Goncalves created FORGE-2235: ---------------------------------------- Summary: Documenting how to create and test a command that scaffolds code Key: FORGE-2235 URL: https://issues.jboss.org/browse/FORGE-2235 Project: Forge Issue Type: Sub-task Components: Documentation Affects Versions: 2.14.0.Final Reporter: Antonio Goncalves Fix For: 2.x Future -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (FORGE-2234) Documenting how to create and test a command that creates or updates text or XML

by Antonio Goncalves (JIRA)

Antonio Goncalves created FORGE-2234: ---------------------------------------- Summary: Documenting how to create and test a command that creates or updates text or XML Key: FORGE-2234 URL: https://issues.jboss.org/browse/FORGE-2234 Project: Forge Issue Type: Sub-task Components: Documentation Affects Versions: 2.14.0.Final Reporter: Antonio Goncalves Fix For: 2.x Future -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (FORGE-2233) Documenting how to create and test a command that updates Java code

by Antonio Goncalves (JIRA)

Antonio Goncalves created FORGE-2233: ---------------------------------------- Summary: Documenting how to create and test a command that updates Java code Key: FORGE-2233 URL: https://issues.jboss.org/browse/FORGE-2233 Project: Forge Issue Type: Sub-task Components: Documentation Affects Versions: 2.14.0.Final Reporter: Antonio Goncalves Fix For: 2.x Future A {{add}} command -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (FORGE-2231) Documenting how to create and test Forge commands

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-2231?page=com.atlassian.jira.plugin... ] Antonio Goncalves updated FORGE-2231: ------------------------------------- Summary: Documenting how to create and test Forge commands (was: Documentating how to create and test Forge commands) > Documenting how to create and test Forge commands > ------------------------------------------------- > > Key: FORGE-2231 > URL: https://issues.jboss.org/browse/FORGE-2231 > Project: Forge > Issue Type: Task > Components: Documentation > Affects Versions: 2.14.0.Final > Reporter: Antonio Goncalves > Fix For: 2.x Future > > > The idea is to document the way we create and test new commands. This will be a joined effort between a Forge expert and a Forge novice so we get the right level of documentation. > Each subtasks document a certain type of command -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (FORGE-2232) Documenting how to create and test a command that creates Java code

by Antonio Goncalves (JIRA)

Antonio Goncalves created FORGE-2232: ---------------------------------------- Summary: Documenting how to create and test a command that creates Java code Key: FORGE-2232 URL: https://issues.jboss.org/browse/FORGE-2232 Project: Forge Issue Type: Sub-task Components: Documentation Affects Versions: 2.14.0.Final Reporter: Antonio Goncalves Fix For: 2.x Future A {{new}} command -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (FORGE-2231) Documentating how to create and test Forge commands

by Antonio Goncalves (JIRA)

Antonio Goncalves created FORGE-2231: ---------------------------------------- Summary: Documentating how to create and test Forge commands Key: FORGE-2231 URL: https://issues.jboss.org/browse/FORGE-2231 Project: Forge Issue Type: Task Components: Documentation Affects Versions: 2.14.0.Final Reporter: Antonio Goncalves Fix For: 2.x Future The idea is to document the way we create and test new commands. This will be a joined effort between a Forge expert and a Forge novice so we get the right level of documentation. Each subtasks document a certain type of command -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (FORGE-2230) CoordinateBuilder should set null for empty parts of G:A:P:C:V

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2230?page=com.atlassian.jira.plugin... ] George Gastaldi commented on FORGE-2230: ---------------------------------------- Instead of null, we should ensure that empty strings are returned instead, in order to avoid statements like: {{if (coordinate.getPackaging()== null || coordinate.getPackaging().isEmpty()}} > CoordinateBuilder should set null for empty parts of G:A:P:C:V > -------------------------------------------------------------- > > Key: FORGE-2230 > URL: https://issues.jboss.org/browse/FORGE-2230 > Project: Forge > Issue Type: Enhancement > Components: Dependencies > Affects Versions: 2.14.0.Final > Reporter: Ondrej Zizka > > CoordinateBuilder, when given "G:A:::V", should set P and C to null. Having them empty strings is no good. > Consider machine-provided lists contaning: > org.foo:foo-bar:::4.1.2 > This should end with the same result as parsing > org.foo:foo-bar:4.1.2 > whereas it ends up with P and C set to empty strings, and forces the user of the api to do extra check for an empty string value. > Related: > "Malformed coordinate. Should be groupId:artifactId:[packaging]:[classifier]:[version]"); > should read > "Malformed coordinate. Should be groupId:artifactId:[packaging:[classifier:]][version]"); > And javadoc's > <groupId>:<artifactId>[:<packaging>[:<classifier>]]:<version> > should read > <groupId>:<artifactId>[:<packaging>[:<classifier>]]:[<version>] -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (FORGE-2230) CoordinateBuilder should set null for empty parts of G:A:P:C:V

by Ondrej Zizka (JIRA)

[ https://issues.jboss.org/browse/FORGE-2230?page=com.atlassian.jira.plugin... ] Ondrej Zizka updated FORGE-2230: -------------------------------- Description: CoordinateBuilder, when given "G:A:::V", should set P and C to null. Having them empty strings is no good. Consider machine-provided lists contaning: org.foo:foo-bar:::4.1.2 This should end with the same result as parsing org.foo:foo-bar:4.1.2 whereas it ends up with P and C set to empty strings, and forces the user of the api to do extra check for an empty string value. Related: "Malformed coordinate. Should be groupId:artifactId:[packaging]:[classifier]:[version]"); should read "Malformed coordinate. Should be groupId:artifactId:[packaging:[classifier:]][version]"); And javadoc's <groupId>:<artifactId>[:<packaging>[:<classifier>]]:<version> should read <groupId>:<artifactId>[:<packaging>[:<classifier>]]:[<version>] was: CoordinateBuilder, when given "G:A:::V", should set P and C to null. Having them empty strings is no good. Consider machine-provided lists contaning: org.foo:foo-bar:::4.1.2 This should end with the same result as parsing org.foo:foo-bar:4.1.2 whereas it ends up with P and C set to empty strings, and forces the user of the api to do extra check for an empty string value. Related: "Malformed coordinate. Should be groupId:artifactId:[packaging]:[classifier]:[version]"); should read "Malformed coordinate. Should be groupId:artifactId:[packaging:[classifier:]][version]"); > CoordinateBuilder should set null for empty parts of G:A:P:C:V > -------------------------------------------------------------- > > Key: FORGE-2230 > URL: https://issues.jboss.org/browse/FORGE-2230 > Project: Forge > Issue Type: Enhancement > Components: Dependencies > Affects Versions: 2.14.0.Final > Reporter: Ondrej Zizka > > CoordinateBuilder, when given "G:A:::V", should set P and C to null. Having them empty strings is no good. > Consider machine-provided lists contaning: > org.foo:foo-bar:::4.1.2 > This should end with the same result as parsing > org.foo:foo-bar:4.1.2 > whereas it ends up with P and C set to empty strings, and forces the user of the api to do extra check for an empty string value. > Related: > "Malformed coordinate. Should be groupId:artifactId:[packaging]:[classifier]:[version]"); > should read > "Malformed coordinate. Should be groupId:artifactId:[packaging:[classifier:]][version]"); > And javadoc's > <groupId>:<artifactId>[:<packaging>[:<classifier>]]:<version> > should read > <groupId>:<artifactId>[:<packaging>[:<classifier>]]:[<version>] -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues February 2015