October 2015 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-2515) project-new prints null in the CLI

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2515?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-2515. ---------------------------------- Fix Version/s: 2.20.1.Final 3.0.0.Alpha1 Assignee: George Gastaldi Resolution: Done Thanks for reporting this. I have fixed in https://github.com/forge/core/commit/331fe4455c006187f9b3d4eda1f8626e4f48... and the fix should be available in the next release > project-new prints null in the CLI > ---------------------------------- > > Key: FORGE-2515 > URL: https://issues.jboss.org/browse/FORGE-2515 > Project: Forge > Issue Type: Bug > Affects Versions: 2.20.0.Final > Reporter: Claus Ibsen > Assignee: George Gastaldi > Priority: Minor > Fix For: 2.20.1.Final, 3.0.0.Alpha1 > > > Notice the null in the label output for the project name > {code} > [forge-distribution-2.20.0.Final]$ project-new > ***INFO*** Required inputs not satisfied, entering interactive mode > ***INFO*** Required inputs not satisfied, entering interactive mode > * Project namenull: foo > ? Top level packagenull [org.foo]: > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2515) project-new prints null in the CLI

by Claus Ibsen (JIRA)

[ https://issues.jboss.org/browse/FORGE-2515?page=com.atlassian.jira.plugin... ] Claus Ibsen commented on FORGE-2515: ------------------------------------ The null was not in older releases > project-new prints null in the CLI > ---------------------------------- > > Key: FORGE-2515 > URL: https://issues.jboss.org/browse/FORGE-2515 > Project: Forge > Issue Type: Bug > Affects Versions: 2.20.0.Final > Reporter: Claus Ibsen > Priority: Minor > > Notice the null in the label output for the project name > {code} > [forge-distribution-2.20.0.Final]$ project-new > ***INFO*** Required inputs not satisfied, entering interactive mode > ***INFO*** Required inputs not satisfied, entering interactive mode > * Project namenull: foo > ? Top level packagenull [org.foo]: > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2515) project-new prints null in the CLI

by Claus Ibsen (JIRA)

Claus Ibsen created FORGE-2515: ---------------------------------- Summary: project-new prints null in the CLI Key: FORGE-2515 URL: https://issues.jboss.org/browse/FORGE-2515 Project: Forge Issue Type: Bug Affects Versions: 2.20.0.Final Reporter: Claus Ibsen Priority: Minor Notice the null in the label output for the project name {code} [forge-distribution-2.20.0.Final]$ project-new ***INFO*** Required inputs not satisfied, entering interactive mode ***INFO*** Required inputs not satisfied, entering interactive mode * Project namenull: foo ? Top level packagenull [org.foo]: {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2512) CommandScope is not active in IntellJ IDEA

by Rafael Pestano (JIRA)

[ https://issues.jboss.org/browse/FORGE-2512?page=com.atlassian.jira.plugin... ] Rafael Pestano edited comment on FORGE-2512 at 10/28/15 8:58 AM: ----------------------------------------------------------------- I can confirm this issue is fixed, created a [simple addon| https://github.com/rmpestano/forge2512] using command scoped works great. I'll investigate the issues I have with music addon and open another issue here if I discovery something. was (Author: kwintesencja): I can confirm this issue is fixed, created a [simple addon| https://github.com/rmpestano/forge2512] and command scoped works great. I'll investigate the issues I have with music addon and open another issue here if I discovery something. > CommandScope is not active in IntellJ IDEA > ------------------------------------------- > > Key: FORGE-2512 > URL: https://issues.jboss.org/browse/FORGE-2512 > Project: Forge > Issue Type: Bug > Components: UI - IntelliJ IDEA > Affects Versions: 2.20.0.Final > Reporter: Rafael Pestano > Assignee: George Gastaldi > > When we use @CommandScoped in addons on IntelliJ the scope is not activated throwing > WELD-001303: No active contexts for scope type org.jboss.forge.addon.ui.cdi.CommandScoped > A sample code is here at ¹ where *SongsFilter * is commandScoped. > I've also tried to activate it in IDEA plugin modifying UIContextImpl² but found some issues, more details at ³ . > [1] https://github.com/rmpestano/music-addon/issues/14 > [2] https://github.com/rmpestano/intellij-idea-plugin/commit/45757d714ecc0c0c... > [3] https://github.com/rmpestano/music-addon/blob/master/src/main/java/com/gi... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2512) CommandScope is not active in IntellJ IDEA

by Rafael Pestano (JIRA)

[ https://issues.jboss.org/browse/FORGE-2512?page=com.atlassian.jira.plugin... ] Rafael Pestano commented on FORGE-2512: --------------------------------------- I can confirm this issue is fixed, created a [simple addon| https://github.com/rmpestano/forge2512] and command scoped works great. I'll investigate the issues I have with music addon and open another issue here if I discovery something. > CommandScope is not active in IntellJ IDEA > ------------------------------------------- > > Key: FORGE-2512 > URL: https://issues.jboss.org/browse/FORGE-2512 > Project: Forge > Issue Type: Bug > Components: UI - IntelliJ IDEA > Affects Versions: 2.20.0.Final > Reporter: Rafael Pestano > Assignee: George Gastaldi > > When we use @CommandScoped in addons on IntelliJ the scope is not activated throwing > WELD-001303: No active contexts for scope type org.jboss.forge.addon.ui.cdi.CommandScoped > A sample code is here at ¹ where *SongsFilter * is commandScoped. > I've also tried to activate it in IDEA plugin modifying UIContextImpl² but found some issues, more details at ³ . > [1] https://github.com/rmpestano/music-addon/issues/14 > [2] https://github.com/rmpestano/intellij-idea-plugin/commit/45757d714ecc0c0c... > [3] https://github.com/rmpestano/music-addon/blob/master/src/main/java/com/gi... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FURNACE-88) Upgrade to Arquillian 1.1.10.Final

by George Gastaldi (JIRA)

George Gastaldi created FURNACE-88: -------------------------------------- Summary: Upgrade to Arquillian 1.1.10.Final Key: FURNACE-88 URL: https://issues.jboss.org/browse/FURNACE-88 Project: Forge: Furnace Issue Type: Component Upgrade Components: Test Harness Affects Versions: 2.22.5.Final Reporter: George Gastaldi Assignee: George Gastaldi Fix For: 2.22.6.Final -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FURNACE-87) Upgrade to Weld 2.3.1.Final

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FURNACE-87?page=com.atlassian.jira.plugin... ] George Gastaldi closed FURNACE-87. ---------------------------------- Resolution: Done > Upgrade to Weld 2.3.1.Final > --------------------------- > > Key: FURNACE-87 > URL: https://issues.jboss.org/browse/FURNACE-87 > Project: Forge: Furnace > Issue Type: Component Upgrade > Components: Container - CDI > Affects Versions: 2.22.5.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 2.22.6.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FURNACE-87) Upgrade to Weld 2.3.1.Final

by George Gastaldi (JIRA)

George Gastaldi created FURNACE-87: -------------------------------------- Summary: Upgrade to Weld 2.3.1.Final Key: FURNACE-87 URL: https://issues.jboss.org/browse/FURNACE-87 Project: Forge: Furnace Issue Type: Component Upgrade Components: Container - CDI Affects Versions: 2.22.5.Final Reporter: George Gastaldi Assignee: George Gastaldi Fix For: 2.22.6.Final -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2514) Renaming targets parameters

by Antonio Goncalves (JIRA)

Antonio Goncalves created FORGE-2514: ---------------------------------------- Summary: Renaming targets parameters Key: FORGE-2514 URL: https://issues.jboss.org/browse/FORGE-2514 Project: Forge Issue Type: Sub-task Affects Versions: 2.20.0.Final Reporter: Antonio Goncalves Fix For: 3.x Future At the moment we have different parameters to point at things : {code} --target --targetClass --targetEntity {code} We also have {{on}} but it could be {{to}} : {code} constraint-add --onProperty constraint-add --targetProperty constraint-add --toProperty {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1512) Renaming scaffold commands

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-1512?page=com.atlassian.jira.plugin... ] Antonio Goncalves updated FORGE-1512: ------------------------------------- Description: Had a chat with @VineetReynolds about the difference between scaffolding and generation. JSF scaffolding is just another code generation (we could keep the 'scaffolding' term when generating an entire app). So, to generate a JSF interface, we should use the following command : {code} faces-generate-pages-from-entities {code} We need to make the difference between scaffolding and generating. At the moment we choose the scaffolding provider like this : {code} scaffold-generate --provider {code} Instead we could have : {code} faces-scaffold --from-entities / --from-database rest-scaffold --from-entities / --from-database {code} But what about creating a new page from an entity ? {code} faces-new-page --from-entity rest-new-endpoint --from-entity {code} was: Had a chat with @VineetReynolds about the difference between scaffolding and generation. JSF scaffolding is just another code generation (we could keep the 'scaffolding' term when generating an entire app). So, to generate a JSF interface, we should use the following command : {code} faces-generate-pages-from-entities {code} > Renaming scaffold commands > -------------------------- > > Key: FORGE-1512 > URL: https://issues.jboss.org/browse/FORGE-1512 > Project: Forge > Issue Type: Sub-task > Components: UI - Shell > Affects Versions: 2.0.0.CR2 > Reporter: Antonio Goncalves > Fix For: 2.x Future > > > Had a chat with @VineetReynolds about the difference between scaffolding and generation. JSF scaffolding is just another code generation (we could keep the 'scaffolding' term when generating an entire app). > So, to generate a JSF interface, we should use the following command : > {code} > faces-generate-pages-from-entities > {code} > We need to make the difference between scaffolding and generating. At the moment we choose the scaffolding provider like this : > {code} > scaffold-generate --provider > {code} > Instead we could have : > {code} > faces-scaffold --from-entities / --from-database > rest-scaffold --from-entities / --from-database > {code} > But what about creating a new page from an entity ? > {code} > faces-new-page --from-entity > rest-new-endpoint --from-entity > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 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 2015