May 2014 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-1793) Commands faces-new-validator and faces-new-converter do not work with faces-setup

by Antonio Goncalves (JIRA)

Antonio Goncalves created FORGE-1793: ---------------------------------------- Summary: Commands faces-new-validator and faces-new-converter do not work with faces-setup Key: FORGE-1793 URL: https://issues.jboss.org/browse/FORGE-1793 Project: Forge Issue Type: Feature Request Components: Java EE Affects Versions: 2.5.0.Final Reporter: Antonio Goncalves Both commands {{faces-new-validator}} and {{faces-new-converter}} generate Java code but which doesn't build. That's because {{faces-setup}} needs to be executed first to add the dependency on JSF on the {{pom.xml}}. Maybe both commands need to {{implements PrerequisiteCommandsProvider}} and override the method {{getPrerequisiteCommands}} as : {code} @Override public NavigationResult getPrerequisiteCommands(UIContext context) { NavigationResultBuilder builder = NavigationResultBuilder.create(); Project project = getSelectedProject(context); if (project != null) { if (!project.hasFacet(FacesFacet.class)) { builder.add(FacesSetupWizard.class); } } return builder.build(); } {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (FORGE-1792) Add scopes to a the faces-new-bean command

by Antonio Goncalves (JIRA)

Antonio Goncalves created FORGE-1792: ---------------------------------------- Summary: Add scopes to a the faces-new-bean command Key: FORGE-1792 URL: https://issues.jboss.org/browse/FORGE-1792 Project: Forge Issue Type: Sub-task Components: Java EE Affects Versions: 2.5.0.Final Reporter: Antonio Goncalves Fix For: 2.x Future The command {{faces-new-bean}} should be able to add a scope. Then, depending on the scope, the generated code would be different (e.g. implements Serializable for most of the other stateful scopes) {code} faces-new-bean --named MyBean --scoped Conversation {code} This would generate the following code {code} @Named @ConversationScoped public class MyBean implements Serializable { @Inject private Conversation conversation; public String begin() { conversation.begin(); } public String end() { conversation.end(); } } {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (FORGE-1595) Being able to create an empty JSF backing bean

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-1595?page=com.atlassian.jira.plugin... ] Antonio Goncalves updated FORGE-1595: ------------------------------------- Description: At the moment the only way to generate JSF backing beans is with scaffolding. To save time and help the developer in creating new backing beans, it would be good to have a command such : {code} faces-new-bean --named MyBean {code} This will create a {{MyBean}}, with no scope, under the {{view}} package. You could also give a different sub-package with : {code} faces-new-page --named MyBean --targetPackage view.admin {code} This will create the page under {{view/admin/MyBean.java}}. {code} @Named public class MyBean { } {code} was: At the moment the only way to generate JSF backing beans is with scaffolding. To save time and help the developer in creating new backing beans, it would be good to have a command such : {code} faces-new-bean --named MyBean {code} This will create a {{MyBean}}, of scope request, under the {{view}} package. You could also give a different sub-package with : {code} faces-new-page --named MyBean --targetPackage view.admin {code} This will create the page under {{view/admin/MyBean.java}}. {code} @Named @RequestScoped public class MyBean { } {code} Then, depending on the scope, the generated code would be different (e.g. implements Serializable for most of the other stateful scopes) {code} faces-new-bean --named MyBean --scoped Conversation {code} This would generate the following code {code} @Named @ConversationScoped public class MyBean implements Serializable { @Inject private Conversation conversation; public String begin() { conversation.begin(); } public String end() { conversation.end(); } } {code} PS : I'm on holidays skiing, and the internet connection is really bad. So I could search for similar JIRAs if they existed > Being able to create an empty JSF backing bean > ---------------------------------------------- > > Key: FORGE-1595 > URL: https://issues.jboss.org/browse/FORGE-1595 > Project: Forge > Issue Type: Sub-task > Components: Scaffold > Affects Versions: 2.0.0.Final > Reporter: Antonio Goncalves > Assignee: Antonio Goncalves > Priority: Minor > Fix For: 2.x Future > > > At the moment the only way to generate JSF backing beans is with scaffolding. To save time and help the developer in creating new backing beans, it would be good to have a command such : > {code} > faces-new-bean --named MyBean > {code} > This will create a {{MyBean}}, with no scope, under the {{view}} package. You could also give a different sub-package with : > {code} > faces-new-page --named MyBean --targetPackage view.admin > {code} > This will create the page under {{view/admin/MyBean.java}}. > {code} > @Named > public class MyBean { > } > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (FORGE-1595) Being able to create an empty JSF backing bean

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-1595?page=com.atlassian.jira.plugin... ] Antonio Goncalves updated FORGE-1595: ------------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/forge/core/pull/452 > Being able to create an empty JSF backing bean > ---------------------------------------------- > > Key: FORGE-1595 > URL: https://issues.jboss.org/browse/FORGE-1595 > Project: Forge > Issue Type: Sub-task > Components: Scaffold > Affects Versions: 2.0.0.Final > Reporter: Antonio Goncalves > Assignee: Antonio Goncalves > Priority: Minor > Fix For: 2.x Future > > > At the moment the only way to generate JSF backing beans is with scaffolding. To save time and help the developer in creating new backing beans, it would be good to have a command such : > {code} > faces-new-bean --named MyBean > {code} > This will create a {{MyBean}}, of scope request, under the {{view}} package. You could also give a different sub-package with : > {code} > faces-new-page --named MyBean --targetPackage view.admin > {code} > This will create the page under {{view/admin/MyBean.java}}. > {code} > @Named > @RequestScoped > public class MyBean { > } > {code} > Then, depending on the scope, the generated code would be different (e.g. implements Serializable for most of the other stateful scopes) > {code} > faces-new-bean --named MyBean --scoped Conversation > {code} > This would generate the following code > {code} > @Named > @ConversationScoped > public class MyBean implements Serializable { > @Inject > private Conversation conversation; > public String begin() { > conversation.begin(); > } > public String end() { > conversation.end(); > } > } > {code} > PS : I'm on holidays skiing, and the internet connection is really bad. So I could search for similar JIRAs if they existed -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (FORGE-1595) Being able to create an empty JSF backing bean

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-1595?page=com.atlassian.jira.plugin... ] Antonio Goncalves reassigned FORGE-1595: ---------------------------------------- Assignee: Antonio Goncalves > Being able to create an empty JSF backing bean > ---------------------------------------------- > > Key: FORGE-1595 > URL: https://issues.jboss.org/browse/FORGE-1595 > Project: Forge > Issue Type: Sub-task > Components: Scaffold > Affects Versions: 2.0.0.Final > Reporter: Antonio Goncalves > Assignee: Antonio Goncalves > Priority: Minor > Fix For: 2.x Future > > > At the moment the only way to generate JSF backing beans is with scaffolding. To save time and help the developer in creating new backing beans, it would be good to have a command such : > {code} > faces-new-bean --named MyBean > {code} > This will create a {{MyBean}}, of scope request, under the {{view}} package. You could also give a different sub-package with : > {code} > faces-new-page --named MyBean --targetPackage view.admin > {code} > This will create the page under {{view/admin/MyBean.java}}. > {code} > @Named > @RequestScoped > public class MyBean { > } > {code} > Then, depending on the scope, the generated code would be different (e.g. implements Serializable for most of the other stateful scopes) > {code} > faces-new-bean --named MyBean --scoped Conversation > {code} > This would generate the following code > {code} > @Named > @ConversationScoped > public class MyBean implements Serializable { > @Inject > private Conversation conversation; > public String begin() { > conversation.begin(); > } > public String end() { > conversation.end(); > } > } > {code} > PS : I'm on holidays skiing, and the internet connection is really bad. So I could search for similar JIRAs if they existed -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ROASTER-12) Shade the JDT dependencies into Roaster-JDT

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/ROASTER-12?page=com.atlassian.jira.plugin... ] George Gastaldi updated ROASTER-12: ----------------------------------- Status: Closed (was: Pull Request Sent) Resolution: Done Pull request merged, thanks! > Shade the JDT dependencies into Roaster-JDT > ------------------------------------------- > > Key: ROASTER-12 > URL: https://issues.jboss.org/browse/ROASTER-12 > Project: Roaster > Issue Type: Feature Request > Components: JDT > Affects Versions: 2.3.0.Final > Reporter: George Gastaldi > Assignee: Lincoln Baxter III > Fix For: 2.3.1.Final > > > The current JDT version used conflicts with ECJ in Drools. We should shade the JDT classes since we don't expect people to use them directly with Roaster. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ROASTER-12) Shade the JDT dependencies into Roaster-JDT

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/ROASTER-12?page=com.atlassian.jira.plugin... ] George Gastaldi updated ROASTER-12: ----------------------------------- Status: Pull Request Sent (was: Reopened) Git Pull Request: https://github.com/forge/roaster/pull/15 > Shade the JDT dependencies into Roaster-JDT > ------------------------------------------- > > Key: ROASTER-12 > URL: https://issues.jboss.org/browse/ROASTER-12 > Project: Roaster > Issue Type: Feature Request > Components: JDT > Affects Versions: 2.3.0.Final > Reporter: George Gastaldi > Assignee: Lincoln Baxter III > Fix For: 2.3.1.Final > > > The current JDT version used conflicts with ECJ in Drools. We should shade the JDT classes since we don't expect people to use them directly with Roaster. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (FORGE-1791) Upgrade to Aesh 0.54

by George Gastaldi (JIRA)

George Gastaldi created FORGE-1791: -------------------------------------- Summary: Upgrade to Aesh 0.54 Key: FORGE-1791 URL: https://issues.jboss.org/browse/FORGE-1791 Project: Forge Issue Type: Component Upgrade Components: UI - Shell Affects Versions: 2.5.0.Final Reporter: George Gastaldi Fix For: 2.5.1.Final -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (FORGE-1790) Make adding addon deps easier in getDeployment().

by Ondrej Zizka (JIRA)

Ondrej Zizka created FORGE-1790: ----------------------------------- Summary: Make adding addon deps easier in getDeployment(). Key: FORGE-1790 URL: https://issues.jboss.org/browse/FORGE-1790 Project: Forge Issue Type: Feature Request Reporter: Ondrej Zizka Currently, the deps need to be stated twice - once in annotations, and then in getDeployment(). If getDeployment() wasn't static, one could get that using reflection. But Arquillian needs getDeployment static. This also limits usage of subclassing, because subclass can't add dependencies to it's parent. Would be nice to come up with some solution to this. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ROASTER-12) Shade the JDT dependencies into Roaster-JDT

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/ROASTER-12?page=com.atlassian.jira.plugin... ] George Gastaldi commented on ROASTER-12: ---------------------------------------- Excellent! Can you submit a Pull Request with your changes? Thank you. > Shade the JDT dependencies into Roaster-JDT > ------------------------------------------- > > Key: ROASTER-12 > URL: https://issues.jboss.org/browse/ROASTER-12 > Project: Roaster > Issue Type: Feature Request > Components: JDT > Affects Versions: 2.3.0.Final > Reporter: George Gastaldi > Assignee: Lincoln Baxter III > Fix For: 2.3.1.Final > > > The current JDT version used conflicts with ECJ in Drools. We should shade the JDT classes since we don't expect people to use them directly with Roaster. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues May 2014