October 2015 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-2485) Upgrade to Furnace 2.22.5.Final

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2485?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-2485. ---------------------------------- Resolution: Done > Upgrade to Furnace 2.22.5.Final > ------------------------------- > > Key: FORGE-2485 > URL: https://issues.jboss.org/browse/FORGE-2485 > Project: Forge > Issue Type: Component Upgrade > Components: Furnace (Container) > Affects Versions: 2.19.2.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 2.20.0.Final > > > Support for Jandex index, Weld 2.3.0.Final and Arquillian 1.1.9.Final -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2485) Upgrade to Furnace 2.22.5.Final

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2485?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-2485: ----------------------------------- Summary: Upgrade to Furnace 2.22.5.Final (was: Upgrade to Furnace 2.22.4.Final) > Upgrade to Furnace 2.22.5.Final > ------------------------------- > > Key: FORGE-2485 > URL: https://issues.jboss.org/browse/FORGE-2485 > Project: Forge > Issue Type: Component Upgrade > Components: Furnace (Container) > Affects Versions: 2.19.2.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 2.20.0.Final > > > Support for Jandex index, Weld 2.3.0.Final and Arquillian 1.1.9.Final -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2485) Upgrade to Furnace 2.22.4.Final

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2485?page=com.atlassian.jira.plugin... ] George Gastaldi reopened FORGE-2485: ------------------------------------ > Upgrade to Furnace 2.22.4.Final > ------------------------------- > > Key: FORGE-2485 > URL: https://issues.jboss.org/browse/FORGE-2485 > Project: Forge > Issue Type: Component Upgrade > Components: Furnace (Container) > Affects Versions: 2.19.2.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 2.20.0.Final > > > Support for Jandex index, Weld 2.3.0.Final and Arquillian 1.1.9.Final -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FURNACE-46) JDK 8 as the minimum requirement

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FURNACE-46?page=com.atlassian.jira.plugin... ] George Gastaldi closed FURNACE-46. ---------------------------------- Fix Version/s: 3.0.0.Alpha1 (was: 3.x Future) Assignee: George Gastaldi Resolution: Done > JDK 8 as the minimum requirement > -------------------------------- > > Key: FURNACE-46 > URL: https://issues.jboss.org/browse/FURNACE-46 > Project: Forge: Furnace > Issue Type: Feature Request > Components: Runtime > Affects Versions: 2.17.1.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 3.0.0.Alpha1 > > > We should adopt JDK 8 as the minimum requirement at some point. > This issue should work as a link between another issues that depend on this to happen -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FURNACE-84) Set default Addon Compatibility Strategy to be LENIENT

by George Gastaldi (JIRA)

George Gastaldi created FURNACE-84: -------------------------------------- Summary: Set default Addon Compatibility Strategy to be LENIENT Key: FURNACE-84 URL: https://issues.jboss.org/browse/FURNACE-84 Project: Forge: Furnace Issue Type: Enhancement Components: Runtime Reporter: George Gastaldi Fix For: 3.x Future The reason for this is that addons developed for Furnace 2.x won't be loaded, even without having an API change. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2279) Renaming parameters so their either use camel case or dash

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2279?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-2279. ---------------------------------- Resolution: Done > Renaming parameters so their either use camel case or dash > ---------------------------------------------------------- > > Key: FORGE-2279 > URL: https://issues.jboss.org/browse/FORGE-2279 > Project: Forge > Issue Type: Sub-task > Components: UI - Shell > Affects Versions: 2.x Future > Reporter: Antonio Goncalves > Assignee: George Gastaldi > Fix For: 3.0.0.Alpha1 > > > One discussion that came once on #IRC was "shall we use camel case on the command parameters, or shall we be more 'unixy' and use a dash syntax". At the moment, most of the parameters have the following syntax : > {code} > --targetPackage > --targetLocation > --columnName > {code} > But a few parameters don't use camel case but the dash syntax : > {code} > --not-nullable > --not-insertable > --not-updatable > {code} > We should choose one syntax and stick to it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2279) Renaming parameters so their either use camel case or dash

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2279?page=com.atlassian.jira.plugin... ] George Gastaldi reopened FORGE-2279: ------------------------------------ The conversion algorithm is still not covering all use-cases. Reopening > Renaming parameters so their either use camel case or dash > ---------------------------------------------------------- > > Key: FORGE-2279 > URL: https://issues.jboss.org/browse/FORGE-2279 > Project: Forge > Issue Type: Sub-task > Components: UI - Shell > Affects Versions: 2.x Future > Reporter: Antonio Goncalves > Assignee: George Gastaldi > Fix For: 3.0.0.Alpha1 > > > One discussion that came once on #IRC was "shall we use camel case on the command parameters, or shall we be more 'unixy' and use a dash syntax". At the moment, most of the parameters have the following syntax : > {code} > --targetPackage > --targetLocation > --columnName > {code} > But a few parameters don't use camel case but the dash syntax : > {code} > --not-nullable > --not-insertable > --not-updatable > {code} > We should choose one syntax and stick to it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FURNACE-46) JDK 8 as the minimum requirement

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FURNACE-46?page=com.atlassian.jira.plugin... ] George Gastaldi updated FURNACE-46: ----------------------------------- Fix Version/s: 3.x Future (was: 2.x Future) > JDK 8 as the minimum requirement > -------------------------------- > > Key: FURNACE-46 > URL: https://issues.jboss.org/browse/FURNACE-46 > Project: Forge: Furnace > Issue Type: Feature Request > Components: Runtime > Affects Versions: 2.17.1.Final > Reporter: George Gastaldi > Fix For: 3.x Future > > > We should adopt JDK 8 as the minimum requirement at some point. > This issue should work as a link between another issues that depend on this to happen -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2279) Renaming parameters so their either use camel case or dash

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2279?page=com.atlassian.jira.plugin... ] George Gastaldi commented on FORGE-2279: ---------------------------------------- Yes, it should work for all parameter names afaik. About the {{--show-parameters}} option that may not work properly because commands can decide which parameters to show on runtime > Renaming parameters so their either use camel case or dash > ---------------------------------------------------------- > > Key: FORGE-2279 > URL: https://issues.jboss.org/browse/FORGE-2279 > Project: Forge > Issue Type: Sub-task > Components: UI - Shell > Affects Versions: 2.x Future > Reporter: Antonio Goncalves > Assignee: George Gastaldi > Fix For: 3.0.0.Alpha1 > > > One discussion that came once on #IRC was "shall we use camel case on the command parameters, or shall we be more 'unixy' and use a dash syntax". At the moment, most of the parameters have the following syntax : > {code} > --targetPackage > --targetLocation > --columnName > {code} > But a few parameters don't use camel case but the dash syntax : > {code} > --not-nullable > --not-insertable > --not-updatable > {code} > We should choose one syntax and stick to it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2279) Renaming parameters so their either use camel case or dash

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-2279?page=com.atlassian.jira.plugin... ] Antonio Goncalves commented on FORGE-2279: ------------------------------------------ Done ? For all the parameters ? BTW, is there a way to list all the parameters of all the commands (something like {{command-list --show-parameters}}). It would be helpful to review all the naming conventions > Renaming parameters so their either use camel case or dash > ---------------------------------------------------------- > > Key: FORGE-2279 > URL: https://issues.jboss.org/browse/FORGE-2279 > Project: Forge > Issue Type: Sub-task > Components: UI - Shell > Affects Versions: 2.x Future > Reporter: Antonio Goncalves > Assignee: George Gastaldi > Fix For: 3.0.0.Alpha1 > > > One discussion that came once on #IRC was "shall we use camel case on the command parameters, or shall we be more 'unixy' and use a dash syntax". At the moment, most of the parameters have the following syntax : > {code} > --targetPackage > --targetLocation > --columnName > {code} > But a few parameters don't use camel case but the dash syntax : > {code} > --not-nullable > --not-insertable > --not-updatable > {code} > We should choose one syntax and stick to it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues October 2015