October 2014 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-2086) Being able to create a new CDI extension

by Antonio Goncalves (JIRA)

Antonio Goncalves created FORGE-2086: ---------------------------------------- Summary: Being able to create a new CDI extension Key: FORGE-2086 URL: https://issues.jboss.org/browse/FORGE-2086 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 be able to create a new CDI extension. A basic command could just be : {code} cdi-new-extension --named MyExtension {code} This will generate the following code as well as enabling : {code} class MyExtension implements Extension { } {code} The extension could be enabled with just an attribute : {code} cdi-new-extension --named MyExtension --enable=true {code} This will create the {{META-INF/services/javax.enterprise.inject.spi.Extension}} file and would declare the extension within the file. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2085) Improving the cdi-new-bean command

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-2085?page=com.atlassian.jira.plugin... ] Antonio Goncalves updated FORGE-2085: ------------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/forge/core/pull/519 > Improving the cdi-new-bean command > ---------------------------------- > > Key: FORGE-2085 > URL: https://issues.jboss.org/browse/FORGE-2085 > Project: Forge > Issue Type: Sub-task > Components: Java EE > Affects Versions: 2.12.1.Final > Reporter: Antonio Goncalves > Assignee: Antonio Goncalves > Fix For: 2.x Future > > > At the moment the {{cdi-new-bean}} command takes the following parameters : > {code} > cdi-new-bean --named --scoped --targetPackage > {code} > It would be good to have a few extra ones : > {code} > cdi-new-bean --named MyBean --scoped SESSION --qualifier Production --alternative=true --withNamed=true > {code} > This would generate : > {code} > @SessionScoped > @Production > @Alternative > @Named > public class MyBean > { > } > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2085) Improving the cdi-new-bean command

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-2085?page=com.atlassian.jira.plugin... ] Antonio Goncalves reassigned FORGE-2085: ---------------------------------------- Assignee: Antonio Goncalves > Improving the cdi-new-bean command > ---------------------------------- > > Key: FORGE-2085 > URL: https://issues.jboss.org/browse/FORGE-2085 > Project: Forge > Issue Type: Sub-task > Components: Java EE > Affects Versions: 2.12.1.Final > Reporter: Antonio Goncalves > Assignee: Antonio Goncalves > Fix For: 2.x Future > > > At the moment the {{cdi-new-bean}} command takes the following parameters : > {code} > cdi-new-bean --named --scoped --targetPackage > {code} > It would be good to have a few extra ones : > {code} > cdi-new-bean --named MyBean --scoped SESSION --qualifier Production --alternative=true --withNamed=true > {code} > This would generate : > {code} > @SessionScoped > @Production > @Alternative > @Named > public class MyBean > { > } > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2085) Improving the cdi-new-bean command

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-2085?page=com.atlassian.jira.plugin... ] Antonio Goncalves updated FORGE-2085: ------------------------------------- Description: At the moment the {{cdi-new-bean}} command takes the following parameters : {code} cdi-new-bean --named --scoped --targetPackage {code} It would be good to have a few extra ones : {code} cdi-new-bean --named MyBean --scoped SESSION --qualifier Production --alternative=true --withNamed=true {code} This would generate : {code} @SessionScoped @Production @Alternative @Named public class MyBean { } {code} was: At the moment the {{cdi-new-bean}} command takes the following parameters : {code} cdi-new-bean --named --scoped --targetPackage {code} It would be good to have a few extra ones : {code} cdi-new-bean --named MyBean --scoped SESSION --qualifier Production --alternative=true --atNamed=true {code} This would generate : {code} @SessionScoped @Production @Alternative @Named public class MyBean { } {code} > Improving the cdi-new-bean command > ---------------------------------- > > Key: FORGE-2085 > URL: https://issues.jboss.org/browse/FORGE-2085 > Project: Forge > Issue Type: Sub-task > Components: Java EE > Affects Versions: 2.12.1.Final > Reporter: Antonio Goncalves > Fix For: 2.x Future > > > At the moment the {{cdi-new-bean}} command takes the following parameters : > {code} > cdi-new-bean --named --scoped --targetPackage > {code} > It would be good to have a few extra ones : > {code} > cdi-new-bean --named MyBean --scoped SESSION --qualifier Production --alternative=true --withNamed=true > {code} > This would generate : > {code} > @SessionScoped > @Production > @Alternative > @Named > public class MyBean > { > } > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2085) Improving the cdi-new-bean command

by Antonio Goncalves (JIRA)

Antonio Goncalves created FORGE-2085: ---------------------------------------- Summary: Improving the cdi-new-bean command Key: FORGE-2085 URL: https://issues.jboss.org/browse/FORGE-2085 Project: Forge Issue Type: Sub-task Components: Java EE Affects Versions: 2.12.1.Final Reporter: Antonio Goncalves Fix For: 2.x Future At the moment the {{cdi-new-bean}} command takes the following parameters : {code} cdi-new-bean --named --scoped --targetPackage {code} It would be good to have a few extra ones : {code} cdi-new-bean --named MyBean --scoped SESSION --qualifier Production --alternative=true --atNamed=true {code} This would generate : {code} @SessionScoped @Production @Alternative @Named public class MyBean { } {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[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-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} 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 @PersistenceContext 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 --named=true {code} {code} public class DatabaseProducer { @Produces @Production @Alternative @RequestScoped @Named @PersistenceContext 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-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} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2081) Being able to add a new CDI event producer to an existing class

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-2081?page=com.atlassian.jira.plugin... ] Antonio Goncalves updated FORGE-2081: ------------------------------------- Description: It would be useful to have a command to add a new CDI event producer to an existing class. A command such as : {code} cdi-add-event-producer --named firePurchaseOrder --type PurchaseOrder {code} Would add to an existing class the following code : {code} @Inject private Event<PurchaseOrder> eventPurchaseOrder; public void firePurchaseOrder() { PurchaseOrder purchaseOrder = new PurchaseOrder(); event.fire(order); } {code} was: It would be useful to have a command to add a new CDI event producer to an existing class. A command such as : {code} cdi-add-event-producer --named event --type PurchaseOrder {code} Would add to an existing class the following code : {code} @Inject private Event<PurchaseOrder> event; public void firePurchaseOrder() { PurchaseOrder purchaseOrder = new PurchaseOrder(); event.fire(order); } {code} > Being able to add a new CDI event producer to an existing class > --------------------------------------------------------------- > > Key: FORGE-2081 > URL: https://issues.jboss.org/browse/FORGE-2081 > 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 useful to have a command to add a new CDI event producer to an existing class. A command such as : > {code} > cdi-add-event-producer --named firePurchaseOrder --type PurchaseOrder > {code} > Would add to an existing class the following code : > {code} > @Inject > private Event<PurchaseOrder> eventPurchaseOrder; > public void firePurchaseOrder() > { > PurchaseOrder purchaseOrder = new PurchaseOrder(); > event.fire(order); > } > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2082) Being able to add a new CDI event observer to an existing class

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-2082?page=com.atlassian.jira.plugin... ] Antonio Goncalves updated FORGE-2082: ------------------------------------- Description: It would be useful to have a command to add a new CDI event observer to an existing class. A command such as : {code} cdi-add-event-observer --named observePurchaseOrder --type PurchaseOrder {code} Would add to an existing class the following code : {code} public void observePurchaseOrder(@Observes PurchaseOrder purchaseOrder) { } {code} was: It would be useful to have a command to add a new CDI event observer to an existing class. A command such as : {code} cdi-add-event-observer --named po --type PurchaseOrder {code} Would add to an existing class the following code : {code} public void observePurchaseOrder(@Observes PurchaseOrder po) { } {code} > Being able to add a new CDI event observer to an existing class > --------------------------------------------------------------- > > Key: FORGE-2082 > URL: https://issues.jboss.org/browse/FORGE-2082 > 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 useful to have a command to add a new CDI event observer to an existing class. A command such as : > {code} > cdi-add-event-observer --named observePurchaseOrder --type PurchaseOrder > {code} > Would add to an existing class the following code : > {code} > public void observePurchaseOrder(@Observes PurchaseOrder purchaseOrder) > { > } > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2084) support sub-shells?

by James Strachan (JIRA)

James Strachan created FORGE-2084: ------------------------------------- Summary: support sub-shells? Key: FORGE-2084 URL: https://issues.jboss.org/browse/FORGE-2084 Project: Forge Issue Type: Feature Request Reporter: James Strachan when working in a particular area (e.g. kubernetes- / project- / jpa- or whatnot) all the command tend to be prefixed by "$area-" which can lead to a bit of extra typing when performing lots of related commands in a particular area. To avoid typing the prefix a lot I wonder if we should support a kinda 'sub shell' thing where if a user is gonna be working for a while on an area (say project- or jpa-) they could just enter the sub shell / domain. e.g. {code} [foo] $ list-facets Command: list-facets was not found. [foo] $ project-list-facest ... [foo] $ project now in the *project* sub shell. Type 'exit' to leave [foo:project] $ list-facets ... [foo:project] $ exit [foo] $ list-facets Command: list-facets was not found. {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2083) support !foo and !! commands

by James Strachan (JIRA)

James Strachan created FORGE-2083: ------------------------------------- Summary: support !foo and !! commands Key: FORGE-2083 URL: https://issues.jboss.org/browse/FORGE-2083 Project: Forge Issue Type: Feature Request Reporter: James Strachan with any shell its handy to re-run previous commands (e.g. to re-run an addon --install command) by referring to the prefix of the command. e.g. {code} $ !addon addon-install --coordinate foo:bar,1.0-SNAPSHOT $ !! addon-install --coordinate foo:bar,1.0-SNAPSHOT {code} Being able to do things like {code} $ history | grep cheese {code} would be handy too -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 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 2014