July 2014 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-1712) Create composite command for Java EE setup

by Jason Porter (JIRA)

[ https://issues.jboss.org/browse/FORGE-1712?page=com.atlassian.jira.plugin... ] Jason Porter commented on FORGE-1712: ------------------------------------- Would this have a series of questions for people to answer, or is it simply delegating to the various commands? > Create composite command for Java EE setup > ------------------------------------------ > > Key: FORGE-1712 > URL: https://issues.jboss.org/browse/FORGE-1712 > Project: Forge > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 2.3.0.Final > Reporter: Arun Gupta > Assignee: George Gastaldi > Labels: Starter > Fix For: 2.x Future > > > Currently every spec need to be explicitly configured as: > servlet-setup; cdi-setup; jpa-setup --container JBOSS_EAP6; rest-setup; constraint-setup; faces-setup; ejb-setup; scaffold-setup > It would be great if a composite command such as "javaee6-setup" can be provided as an ease-of-use. Later "javaee7-setup" can be provided. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1594) Being able to create a new View

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1594?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-1594: ----------------------------------- Labels: starter (was: ) > Being able to create a new View > ------------------------------- > > Key: FORGE-1594 > URL: https://issues.jboss.org/browse/FORGE-1594 > Project: Forge > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Scaffold > Affects Versions: 2.0.0.Final > Reporter: Antonio Goncalves > Assignee: Antonio Goncalves > Priority: Minor > Labels: starter > Fix For: 2.x Future > > > At the moment the only way to generate JSF pages is with scaffolding. When you create an application, you realize that these scaffolded pages are not enough and that you need to create new ones. To save time and help the developer in creating new pages, it would be good to have a command such : > {code} > faces-new-view --named mypage > {code} > This will create a mypage.xhtml on the root of the webapp directory. You could also give a different directory with : > {code} > faces-new-view --named mypage --targetDirectory admin > {code} > This will create the page under webapp/admin/mypage.xhtml. > {code} > <?xml version='1.0' encoding='UTF-8' ?> > <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> > <ui:composition xmlns="http://www.w3.org/1999/xhtml" > xmlns:h="http://xmlns.jcp.org/jsf/html" > xmlns:f="http://xmlns.jcp.org/jsf/core" > xmlns:ui="http://xmlns.jcp.org/jsf/facelets" > template="/resources/scaffold/pageTemplate.xhtml"> > <ui:param name="pageTitle" value="mypage"/> > <ui:define name="header"> > mypage > </ui:define> > <ui:define name="subheader"> > mypage > </ui:define> > <ui:define name="footer"/> > <ui:define name="main"> > </ui:define> > </ui:composition> > {code} > The name of the page {{mypage}} is used for the title, header, subheader. But we could customize this using optional attributes for title, header, subheader : > {code} > faces-new-view --named mypage --targetDirectory admin --title Administration Page --header Admin Header --subheader Admin Sub Header > {code} > It would just create a minimum JSF page such as : > {code} > <?xml version='1.0' encoding='UTF-8' ?> > <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> > <ui:composition xmlns="http://www.w3.org/1999/xhtml" > xmlns:h="http://xmlns.jcp.org/jsf/html" > xmlns:f="http://xmlns.jcp.org/jsf/core" > xmlns:ui="http://xmlns.jcp.org/jsf/facelets" > template="/resources/scaffold/pageTemplate.xhtml"> > <ui:param name="pageTitle" value="Administration Page"/> > <ui:define name="header"> > Admin Header > </ui:define> > <ui:define name="subheader"> > Admin Sub Header > </ui:define> > <ui:define name="footer"/> > <ui:define name="main"> > </ui:define> > </ui:composition> > {code} > If there were several templates, we could do : > {code} > faces-new-view --named mypage --template MyTemplate.xhtml > {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.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1927) Numbered lists are not properly styled in the rendered documentation

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1927?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-1927: ----------------------------------- Parent: FORGE-1319 Issue Type: Sub-task (was: Bug) > Numbered lists are not properly styled in the rendered documentation > -------------------------------------------------------------------- > > Key: FORGE-1927 > URL: https://issues.jboss.org/browse/FORGE-1927 > Project: Forge > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Website > Reporter: George Gastaldi > Fix For: 2.x Future > > > Original document: https://github.com/forge/docs/blob/master/tutorials/How-to-get-your-addon... > Rendered document: http://forge.jboss.org/document/how-to-get-your-addon-listed-in-the-forge... -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1874) Migrate Maven commands from Forge 1

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-1874?page=com.atlassian.jira.plugin... ] Antonio Goncalves updated FORGE-1874: ------------------------------------- Parent: FORGE-1926 Issue Type: Sub-task (was: Feature Request) > Migrate Maven commands from Forge 1 > ----------------------------------- > > Key: FORGE-1874 > URL: https://issues.jboss.org/browse/FORGE-1874 > Project: Forge > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: UI - Shell > Affects Versions: 2.6.0.Final > Reporter: Antonio Goncalves > Fix For: 2.x Future > > > In Forge 1.x we had Maven commands, it would be good to have the same capabilities in Forge 2.x > {code} > [test] $ mvn > [ARG (of type java.lang.String[])] > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1291) Create Faces commands to create/register new PhaseListener objects

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-1291?page=com.atlassian.jira.plugin... ] Antonio Goncalves updated FORGE-1291: ------------------------------------- Parent: FORGE-1926 Issue Type: Sub-task (was: Feature Request) > Create Faces commands to create/register new PhaseListener objects > ------------------------------------------------------------------ > > Key: FORGE-1291 > URL: https://issues.jboss.org/browse/FORGE-1291 > Project: Forge > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Builtin Plugins, Java EE > Affects Versions: 2.0.0.Alpha14 > Reporter: Lincoln Baxter III > Fix For: 2.x Future > > -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1237) Create EJB Commands to manage ApplicationException settings in ejb-jar.xml

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-1237?page=com.atlassian.jira.plugin... ] Antonio Goncalves updated FORGE-1237: ------------------------------------- Parent: FORGE-1926 Issue Type: Sub-task (was: Feature Request) > Create EJB Commands to manage ApplicationException settings in ejb-jar.xml > -------------------------------------------------------------------------- > > Key: FORGE-1237 > URL: https://issues.jboss.org/browse/FORGE-1237 > Project: Forge > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Java EE > Affects Versions: 2.0.0.Alpha12 > Reporter: Lincoln Baxter III > Fix For: 2.x Future > > -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1463) Create Faces Command to create new View

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-1463?page=com.atlassian.jira.plugin... ] Antonio Goncalves closed FORGE-1463. ------------------------------------ Resolution: Duplicate Issue Duplicates [FORGE-1594] > Create Faces Command to create new View > --------------------------------------- > > Key: FORGE-1463 > URL: https://issues.jboss.org/browse/FORGE-1463 > Project: Forge > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Builtin Plugins > Affects Versions: 2.0.0.CR1 > Reporter: Lincoln Baxter III > Fix For: 2.x Future > > -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1594) Being able to create a new View

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-1594?page=com.atlassian.jira.plugin... ] Antonio Goncalves updated FORGE-1594: ------------------------------------- Summary: Being able to create a new View (was: Being able to create an empty JSF page) > Being able to create a new View > ------------------------------- > > Key: FORGE-1594 > URL: https://issues.jboss.org/browse/FORGE-1594 > Project: Forge > Issue Type: Sub-task > Security Level: Public(Everyone can see) > 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 pages is with scaffolding. When you create an application, you realize that these scaffolded pages are not enough and that you need to create new ones. To save time and help the developer in creating new pages, it would be good to have a command such : > {code} > faces-new-view --named mypage > {code} > This will create a mypage.xhtml on the root of the webapp directory. You could also give a different directory with : > {code} > faces-new-view --named mypage --targetDirectory admin > {code} > This will create the page under webapp/admin/mypage.xhtml. > {code} > <?xml version='1.0' encoding='UTF-8' ?> > <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> > <ui:composition xmlns="http://www.w3.org/1999/xhtml" > xmlns:h="http://xmlns.jcp.org/jsf/html" > xmlns:f="http://xmlns.jcp.org/jsf/core" > xmlns:ui="http://xmlns.jcp.org/jsf/facelets" > template="/resources/scaffold/pageTemplate.xhtml"> > <ui:param name="pageTitle" value="mypage"/> > <ui:define name="header"> > mypage > </ui:define> > <ui:define name="subheader"> > mypage > </ui:define> > <ui:define name="footer"/> > <ui:define name="main"> > </ui:define> > </ui:composition> > {code} > The name of the page {{mypage}} is used for the title, header, subheader. But we could customize this using optional attributes for title, header, subheader : > {code} > faces-new-view --named mypage --targetDirectory admin --title Administration Page --header Admin Header --subheader Admin Sub Header > {code} > It would just create a minimum JSF page such as : > {code} > <?xml version='1.0' encoding='UTF-8' ?> > <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> > <ui:composition xmlns="http://www.w3.org/1999/xhtml" > xmlns:h="http://xmlns.jcp.org/jsf/html" > xmlns:f="http://xmlns.jcp.org/jsf/core" > xmlns:ui="http://xmlns.jcp.org/jsf/facelets" > template="/resources/scaffold/pageTemplate.xhtml"> > <ui:param name="pageTitle" value="Administration Page"/> > <ui:define name="header"> > Admin Header > </ui:define> > <ui:define name="subheader"> > Admin Sub Header > </ui:define> > <ui:define name="footer"/> > <ui:define name="main"> > </ui:define> > </ui:composition> > {code} > If there were several templates, we could do : > {code} > faces-new-view --named mypage --template MyTemplate.xhtml > {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.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1615) Being able to create Bean Validation artifacts

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-1615?page=com.atlassian.jira.plugin... ] Antonio Goncalves closed FORGE-1615. ------------------------------------ Resolution: Done Remaining issues have been moved to [FORGE-1926] > Being able to create Bean Validation artifacts > ---------------------------------------------- > > Key: FORGE-1615 > URL: https://issues.jboss.org/browse/FORGE-1615 > Project: Forge > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Scaffold > Affects Versions: 2.1.1.Final > Reporter: Antonio Goncalves > Fix For: 2.x Future > > > See sub-tasks -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1927) Numbered lists are not properly styled in the rendered documentation

by George Gastaldi (JIRA)

George Gastaldi created FORGE-1927: -------------------------------------- Summary: Numbered lists are not properly styled in the rendered documentation Key: FORGE-1927 URL: https://issues.jboss.org/browse/FORGE-1927 Project: Forge Issue Type: Bug Security Level: Public (Everyone can see) Components: Website Reporter: George Gastaldi Fix For: 2.x Future Original document: https://github.com/forge/docs/blob/master/tutorials/How-to-get-your-addon... Rendered document: http://forge.jboss.org/document/how-to-get-your-addon-listed-in-the-forge... -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues July 2014