September 2015 - forge-issues - Jboss List Archives

[JBoss JIRA] (FURNACE-79) Upgrade to Weld 2.3.0.Final

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FURNACE-79?page=com.atlassian.jira.plugin... ] George Gastaldi closed FURNACE-79. ---------------------------------- Resolution: Done > Upgrade to Weld 2.3.0.Final > --------------------------- > > Key: FURNACE-79 > URL: https://issues.jboss.org/browse/FURNACE-79 > Project: Forge: Furnace > Issue Type: Component Upgrade > Components: Container - CDI > Affects Versions: 2.21.0.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 2.22.1.Final > > > http://weld.cdi-spec.org/news/2015/09/18/weld-230Final/ -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FURNACE-79) Upgrade to Weld 2.3.0.Final

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FURNACE-79?page=com.atlassian.jira.plugin... ] George Gastaldi updated FURNACE-79: ----------------------------------- Fix Version/s: 2.22.1.Final (was: 2.22.0.Final) > Upgrade to Weld 2.3.0.Final > --------------------------- > > Key: FURNACE-79 > URL: https://issues.jboss.org/browse/FURNACE-79 > Project: Forge: Furnace > Issue Type: Component Upgrade > Components: Container - CDI > Affects Versions: 2.21.0.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 2.22.1.Final > > > http://weld.cdi-spec.org/news/2015/09/18/weld-230Final/ -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FURNACE-79) Upgrade to Weld 2.3.0.Final

by George Gastaldi (JIRA)

George Gastaldi created FURNACE-79: -------------------------------------- Summary: Upgrade to Weld 2.3.0.Final Key: FURNACE-79 URL: https://issues.jboss.org/browse/FURNACE-79 Project: Forge: Furnace Issue Type: Component Upgrade Components: Container - CDI Affects Versions: 2.21.0.Final Reporter: George Gastaldi Assignee: George Gastaldi Fix For: 2.21.1.Final http://weld.cdi-spec.org/news/2015/09/18/weld-230Final/ -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2470) List of JIRAs Antoine and Antonio would like to get fixed for their Devoxx Univeristy (by mid-November 2015)

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-2470?page=com.atlassian.jira.plugin... ] Antonio Goncalves updated FORGE-2470: ------------------------------------- Description: Here are a few JIRAs that would get to be implemented so it makes the talk smoother : * [FORGE-2374] - Being able to generate an abstract or final Java class implementing serialiazable or not * [ROASTER-51] - Add interface or abstract class should implement inherited methods * [FORGE-2466] - Cannot use '~' in most of the command parameters * [FORGE-1580] - Having more flexible templating to integrate JSF pages better * [FORGE-2099] - scaffold-generate command should have a --targetPackage attribute * [FORGE-1808] - Being able to have inheritance in CDI * [FORGE-1594] - Being able to create a new JSF View * [FORGE-2081] - Being able to add a new CDI event producer to an existing class * [FORGE-2079] - Being able to add a new CDI producer field * [FORGE-2225] - Being able to add a new CDI producer method to an existing class * [FORGE-2468] - Being able to add methods to an existing JSF backing bean * [FORGE-2318] - Being able to setup a logger was: Here are a few JIRAs that would get to be implemented so it makes the talk smoother : * [FORGE-2374] - Being able to generate an abstract or final Java class implementing serialiazable or not * [ROASTER-51] - Add interface or abstract class should implement inherited methods * [FORGE-2466] - Cannot use '~' in most of the command parameters * [FORGE-1580] - Integrating the generated JSF pages better into a entire web application * [FORGE-2099] - scaffold-generate command should have a --targetPackage attribute * [FORGE-1808] - Being able to have inheritance in CDI * [FORGE-1594] - Being able to create a new JSF View * [FORGE-2081] - Being able to add a new CDI event producer to an existing class * [FORGE-2079] - Being able to add a new CDI producer field * [FORGE-2225] - Being able to add a new CDI producer method to an existing class * [FORGE-2468] - Being able to add methods to an existing JSF backing bean * [FORGE-2318] - Being able to setup a logger > List of JIRAs Antoine and Antonio would like to get fixed for their Devoxx Univeristy (by mid-November 2015) > ------------------------------------------------------------------------------------------------------------ > > Key: FORGE-2470 > URL: https://issues.jboss.org/browse/FORGE-2470 > Project: Forge > Issue Type: Task > Components: Brainstorming > Affects Versions: 2.19.0.Final > Reporter: Antonio Goncalves > Fix For: 2.x Future > > > Here are a few JIRAs that would get to be implemented so it makes the talk smoother : > * [FORGE-2374] - Being able to generate an abstract or final Java class implementing serialiazable or not > * [ROASTER-51] - Add interface or abstract class should implement inherited methods > * [FORGE-2466] - Cannot use '~' in most of the command parameters > * [FORGE-1580] - Having more flexible templating to integrate JSF pages better > * [FORGE-2099] - scaffold-generate command should have a --targetPackage attribute > * [FORGE-1808] - Being able to have inheritance in CDI > * [FORGE-1594] - Being able to create a new JSF View > * [FORGE-2081] - Being able to add a new CDI event producer to an existing class > * [FORGE-2079] - Being able to add a new CDI producer field > * [FORGE-2225] - Being able to add a new CDI producer method to an existing class > * [FORGE-2468] - Being able to add methods to an existing JSF backing bean > * [FORGE-2318] - Being able to setup a logger -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1580) Having more flexible templating to integrate JSF pages better

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-1580?page=com.atlassian.jira.plugin... ] Antonio Goncalves updated FORGE-1580: ------------------------------------- Summary: Having more flexible templating to integrate JSF pages better (was: Integrating the generated JSF pages better into a entire web application) > Having more flexible templating to integrate JSF pages better > ------------------------------------------------------------- > > Key: FORGE-1580 > URL: https://issues.jboss.org/browse/FORGE-1580 > Project: Forge > Issue Type: Feature Request > Components: Scaffold > Affects Versions: 2.0.0.Final > Reporter: Antonio Goncalves > Fix For: 2.x Future > > > I often use Forge to create separate administration pages that will fit an entire web application (a bit like in TicketMonster). The problem is that all JSF pages use {{pageTemplate.xhtml}} and this template declares a header, footer and navigation menu. So the other pages of the web site cannot use this template. > Forge could either : > * use 2 level of templates : the {{pageTemplate.xhtml}} only does the header and footer, and we had a new {{forgeTemplate.xhtml}} that uses {{pageTemplate.xhtml}} and adds a navigation menu > * we only use {{pageTemplate.xhtml}} but the template actually includes a {{header.xhtml}}, {{footer.xhtml}} and {{navigation.xhtml}} page (with the {{<ui:include>}} tag) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2470) List of JIRAs Antoine and Antonio would like to get fixed for their Devoxx Univeristy (by mid-November 2015)

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-2470?page=com.atlassian.jira.plugin... ] Antonio Goncalves updated FORGE-2470: ------------------------------------- Description: Here are a few JIRAs that would get to be implemented so it makes the talk smoother : * [FORGE-2374] - Being able to generate an abstract or final Java class implementing serialiazable or not * [ROASTER-51] - Add interface or abstract class should implement inherited methods * [FORGE-2466] - Cannot use '~' in most of the command parameters * [FORGE-1580] - Integrating the generated JSF pages better into a entire web application * [FORGE-2099] - scaffold-generate command should have a --targetPackage attribute * [FORGE-1808] - Being able to have inheritance in CDI * [FORGE-1594] - Being able to create a new JSF View * [FORGE-2081] - Being able to add a new CDI event producer to an existing class * [FORGE-2079] - Being able to add a new CDI producer field * [FORGE-2225] - Being able to add a new CDI producer method to an existing class * [FORGE-2468] - Being able to add methods to an existing JSF backing bean * [FORGE-2318] - Being able to setup a logger was: Here are a few JIRAs that would get to be implemented so it makes the talk smoother : * [FORGE-2374] - Being able to generate an abstract or final Java class implementing serialiazable or not * [ROASTER-51] - Add interface or abstract class should implement inherited methods * [FORGE-2466] - Cannot use '~' in most of the command parameters * [FORGE-2099] - scaffold-generate command should have a --targetPackage attribute * [FORGE-1808] - Being able to have inheritance in CDI * [FORGE-1478] - Being able to have inheritance in JPA * [FORGE-1594] - Being able to create a new JSF View * [FORGE-2081] - Being able to add a new CDI event producer to an existing class * [FORGE-2079] - Being able to add a new CDI producer field * [FORGE-2225] - Being able to add a new CDI producer method to an existing class * [FORGE-2468] - Being able to add methods to an existing JSF backing bean * [FORGE-2318] - Being able to setup a logger > List of JIRAs Antoine and Antonio would like to get fixed for their Devoxx Univeristy (by mid-November 2015) > ------------------------------------------------------------------------------------------------------------ > > Key: FORGE-2470 > URL: https://issues.jboss.org/browse/FORGE-2470 > Project: Forge > Issue Type: Task > Components: Brainstorming > Affects Versions: 2.19.0.Final > Reporter: Antonio Goncalves > Fix For: 2.x Future > > > Here are a few JIRAs that would get to be implemented so it makes the talk smoother : > * [FORGE-2374] - Being able to generate an abstract or final Java class implementing serialiazable or not > * [ROASTER-51] - Add interface or abstract class should implement inherited methods > * [FORGE-2466] - Cannot use '~' in most of the command parameters > * [FORGE-1580] - Integrating the generated JSF pages better into a entire web application > * [FORGE-2099] - scaffold-generate command should have a --targetPackage attribute > * [FORGE-1808] - Being able to have inheritance in CDI > * [FORGE-1594] - Being able to create a new JSF View > * [FORGE-2081] - Being able to add a new CDI event producer to an existing class > * [FORGE-2079] - Being able to add a new CDI producer field > * [FORGE-2225] - Being able to add a new CDI producer method to an existing class > * [FORGE-2468] - Being able to add methods to an existing JSF backing bean > * [FORGE-2318] - Being able to setup a logger -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1580) Integrating the generated JSF pages better into a entire web application

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-1580?page=com.atlassian.jira.plugin... ] Antonio Goncalves updated FORGE-1580: ------------------------------------- Description: I often use Forge to create separate administration pages that will fit an entire web application (a bit like in TicketMonster). The problem is that all JSF pages use {{pageTemplate.xhtml}} and this template declares a header, footer and navigation menu. So the other pages of the web site cannot use this template. Forge could either : * use 2 level of templates : the {{pageTemplate.xhtml}} only does the header and footer, and we had a new {{forgeTemplate.xhtml}} that uses {{pageTemplate.xhtml}} and adds a navigation menu * we only use {{pageTemplate.xhtml}} but the template actually includes a {{header.xhtml}}, {{footer.xhtml}} and {{navigation.xhtml}} page (with the {{<ui:include>}} tag) was: I often use Forge to create separate administration pages that will fit an entire web application (a bit like in TicketMonster). The problem is that all JSF pages use {{pageTemplate.xhtml}} and this template declares a navigation menu. So the other pages of the web site cannot use this template. Forge could either : * use 2 level of templates : the {{pageTemplate.xhtml}} only does the header and footer, and we had a new {{forgeTemplate.xhtml}} that uses {{pageTemplate.xhtml}} and adds a navigation menu * we only use {{pageTemplate.xhtml}} but the menu is an external component that could only be used by Forge pages. > Integrating the generated JSF pages better into a entire web application > ------------------------------------------------------------------------ > > Key: FORGE-1580 > URL: https://issues.jboss.org/browse/FORGE-1580 > Project: Forge > Issue Type: Feature Request > Components: Scaffold > Affects Versions: 2.0.0.Final > Reporter: Antonio Goncalves > Fix For: 2.x Future > > > I often use Forge to create separate administration pages that will fit an entire web application (a bit like in TicketMonster). The problem is that all JSF pages use {{pageTemplate.xhtml}} and this template declares a header, footer and navigation menu. So the other pages of the web site cannot use this template. > Forge could either : > * use 2 level of templates : the {{pageTemplate.xhtml}} only does the header and footer, and we had a new {{forgeTemplate.xhtml}} that uses {{pageTemplate.xhtml}} and adds a navigation menu > * we only use {{pageTemplate.xhtml}} but the template actually includes a {{header.xhtml}}, {{footer.xhtml}} and {{navigation.xhtml}} page (with the {{<ui:include>}} tag) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2484) java-new-enum-const should follow the naming convention

by Antonio Goncalves (JIRA)

Antonio Goncalves created FORGE-2484: ---------------------------------------- Summary: java-new-enum-const should follow the naming convention Key: FORGE-2484 URL: https://issues.jboss.org/browse/FORGE-2484 Project: Forge Issue Type: Sub-task Components: Java EE Affects Versions: 2.19.1.Final Reporter: Antonio Goncalves Fix For: 2.x Future At the moment to add a new constant to an enum we type : {code} java-new-enum-const VISA ; {code} To follow the other commands, it should have a {{named}} parameter {code} java-new-enum-const --name VISA ; java-new-enum-const --name MASTER_CARD ; java-new-enum-const --name AMERICAN_EXPRESS ; {code} Changing {{new}} to {{add}} we could end up with : {code} java-add-enum-const --name VISA ; java-add-enum-const --name MASTER_CARD ; java-add-enum-const --name AMERICAN_EXPRESS ; {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2484) java-new-enum-const should follow the naming convention

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-2484?page=com.atlassian.jira.plugin... ] Antonio Goncalves updated FORGE-2484: ------------------------------------- Description: At the moment to add a new constant to an enum we type : {code} java-new-enum-const VISA ; {code} To follow the other commands, it should have a {{named}} parameter {code} java-new-enum-const --named VISA ; java-new-enum-const --named MASTER_CARD ; java-new-enum-const --named AMERICAN_EXPRESS ; {code} Changing {{new}} to {{add}} we could end up with : {code} java-add-enum-const --named VISA ; java-add-enum-const --named MASTER_CARD ; java-add-enum-const --named AMERICAN_EXPRESS ; {code} was: At the moment to add a new constant to an enum we type : {code} java-new-enum-const VISA ; {code} To follow the other commands, it should have a {{named}} parameter {code} java-new-enum-const --name VISA ; java-new-enum-const --name MASTER_CARD ; java-new-enum-const --name AMERICAN_EXPRESS ; {code} Changing {{new}} to {{add}} we could end up with : {code} java-add-enum-const --name VISA ; java-add-enum-const --name MASTER_CARD ; java-add-enum-const --name AMERICAN_EXPRESS ; {code} > java-new-enum-const should follow the naming convention > ------------------------------------------------------- > > Key: FORGE-2484 > URL: https://issues.jboss.org/browse/FORGE-2484 > Project: Forge > Issue Type: Sub-task > Components: Java EE > Affects Versions: 2.19.1.Final > Reporter: Antonio Goncalves > Fix For: 2.x Future > > > At the moment to add a new constant to an enum we type : > {code} > java-new-enum-const VISA ; > {code} > To follow the other commands, it should have a {{named}} parameter > {code} > java-new-enum-const --named VISA ; > java-new-enum-const --named MASTER_CARD ; > java-new-enum-const --named AMERICAN_EXPRESS ; > {code} > Changing {{new}} to {{add}} we could end up with : > {code} > java-add-enum-const --named VISA ; > java-add-enum-const --named MASTER_CARD ; > java-add-enum-const --named AMERICAN_EXPRESS ; > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2483) SLF4J jars are missing in database-tools

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2483?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-2483. ---------------------------------- Resolution: Done > SLF4J jars are missing in database-tools > ---------------------------------------- > > Key: FORGE-2483 > URL: https://issues.jboss.org/browse/FORGE-2483 > Project: Forge > Issue Type: Bug > Components: Database Tools > Affects Versions: 2.19.1.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Priority: Blocker > Fix For: 2.19.2.Final > > > Hibernate tools 4.3.1.Final depend directly on SLF4j APIs. The addon should also have the SLF4J API + JDK14 JARs bundled -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues September 2015