July 2014 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGEPLUGINS-167) Support conditional creation of REST resources

by Vineet Reynolds (JIRA)

Vineet Reynolds created FORGEPLUGINS-167: -------------------------------------------- Summary: Support conditional creation of REST resources Key: FORGEPLUGINS-167 URL: https://issues.jboss.org/browse/FORGEPLUGINS-167 Project: Forge Plugins/Addons Issue Type: Feature Request Security Level: Public (Everyone can see) Components: AngularJS Scaffold Reporter: Vineet Reynolds Assignee: Vineet Reynolds REST resources should be created only when the user requires them, failing which existing REST resources may be overwritten by the {{scaffold-generate}} command. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1898) Dashes in the project name makes jpa-new-entity execution to fail

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1898?page=com.atlassian.jira.plugin... ] Lincoln Baxter III commented on FORGE-1898: ------------------------------------------- I think this should be resolved by validation in the targetPackage fields. Thoughts? > Dashes in the project name makes jpa-new-entity execution to fail > ----------------------------------------------------------------- > > Key: FORGE-1898 > URL: https://issues.jboss.org/browse/FORGE-1898 > Project: Forge > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Java EE > Affects Versions: 2.6.0.Final > Reporter: George Gastaldi > Assignee: Matej Briskar > Fix For: 2.x Future > > > Create a project named {{a-project-for-example}} and create a new JPA Entity. It should fail with a Roaster error. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1898) Dashes in the project name makes jpa-new-entity execution to fail

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1898?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-1898: ----------------------------------- Description: Create a project named {{a-project-for-example}} and create a new JPA Entity. It should fail with a Roaster error. (was: Create a project named {{a-project-with-dashes}} and create a new JPA Entity. It should fail with a Roaster error.) > Dashes in the project name makes jpa-new-entity execution to fail > ----------------------------------------------------------------- > > Key: FORGE-1898 > URL: https://issues.jboss.org/browse/FORGE-1898 > Project: Forge > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Java EE > Affects Versions: 2.6.0.Final > Reporter: George Gastaldi > Assignee: Matej Briskar > Fix For: 2.x Future > > > Create a project named {{a-project-for-example}} and create a new JPA Entity. It should fail with a Roaster error. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1622) It would be good if Aesh had access to export variables

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1622?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1622. ---------------------------------- Resolution: Done Thanks > It would be good if Aesh had access to export variables > ------------------------------------------------------- > > Key: FORGE-1622 > URL: https://issues.jboss.org/browse/FORGE-1622 > Project: Forge > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: UI - Shell > Affects Versions: 2.1.1.Final > Reporter: Antonio Goncalves > Assignee: Daniel Cunha > Priority: Minor > Fix For: 2.7.0.Final > > > This would be a "nice to have" feature from the shell command line. > I'm under OS X and I have a set of variables that I've exported. As an example, all my code is under {{$CODE_HOME}}. It would be good if I code {{cd $CODE_HOME}} when I'm in Aesh : > {code} > ~$ cd $CODE_HOME // Under OS X > ~/Documents/Code$ forge // Entering Forge > _____ > | ___|__ _ __ __ _ ___ > | |_ / _ \| `__/ _` |/ _ \ \\ > | _| (_) | | | (_| | __/ // > |_| \___/|_| \__, |\___| > |___/ > JBoss Forge, version [ 2.1.1.Final ] - JBoss, by Red Hat, Inc. > [Code]$ cd ~ > [antoniombp]$ cd $CODE_HOME // Good if it goes to the right directory > [antoniombp]$ echo $CODE_HOME // Doesn't have access to the exported variable > [antoniombp]$ > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1622) It would be good if Aesh had access to export variables

by Daniel Cunha (JIRA)

[ https://issues.jboss.org/browse/FORGE-1622?page=com.atlassian.jira.plugin... ] Daniel Cunha commented on FORGE-1622: ------------------------------------- [~gastaldi] Aesh problem fixed. https://issues.jboss.org/browse/AESH-266 https://github.com/aeshell/aesh/pull/93 > It would be good if Aesh had access to export variables > ------------------------------------------------------- > > Key: FORGE-1622 > URL: https://issues.jboss.org/browse/FORGE-1622 > Project: Forge > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: UI - Shell > Affects Versions: 2.1.1.Final > Reporter: Antonio Goncalves > Assignee: Daniel Cunha > Priority: Minor > Fix For: 2.7.0.Final > > > This would be a "nice to have" feature from the shell command line. > I'm under OS X and I have a set of variables that I've exported. As an example, all my code is under {{$CODE_HOME}}. It would be good if I code {{cd $CODE_HOME}} when I'm in Aesh : > {code} > ~$ cd $CODE_HOME // Under OS X > ~/Documents/Code$ forge // Entering Forge > _____ > | ___|__ _ __ __ _ ___ > | |_ / _ \| `__/ _` |/ _ \ \\ > | _| (_) | | | (_| | __/ // > |_| \___/|_| \__, |\___| > |___/ > JBoss Forge, version [ 2.1.1.Final ] - JBoss, by Red Hat, Inc. > [Code]$ cd ~ > [antoniombp]$ cd $CODE_HOME // Good if it goes to the right directory > [antoniombp]$ echo $CODE_HOME // Doesn't have access to the exported variable > [antoniombp]$ > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1863) Create a GenerateHashcodeEquals command inside the dev-tools-java addon.

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1863?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1863. ---------------------------------- Fix Version/s: 2.7.0.Final Resolution: Done Thanks! > Create a GenerateHashcodeEquals command inside the dev-tools-java addon. > ------------------------------------------------------------------------ > > Key: FORGE-1863 > URL: https://issues.jboss.org/browse/FORGE-1863 > Project: Forge > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Matej Briskar > Assignee: Matej Briskar > Fix For: 2.7.0.Final > > -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1916) Add versioning and exception handling to JAX-RS scaffolding

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1916?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-1916: ----------------------------------- Status: Closed (was: Pull Request Sent) Fix Version/s: 2.7.0.Final (was: 2.x Future) Resolution: Done Changes merged;. Thanks [~edewit] > Add versioning and exception handling to JAX-RS scaffolding > ----------------------------------------------------------- > > Key: FORGE-1916 > URL: https://issues.jboss.org/browse/FORGE-1916 > Project: Forge > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Burr Sutter > Assignee: George Gastaldi > Priority: Critical > Fix For: 2.7.0.Final > > > Eric to provide the changes to the JAX-RS endpoint code to allow for entity versioning and dealing with update conflicts. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1906) Web Root path in Scaffold should be "/" by default in the UI input

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1906?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-1906: ----------------------------------- Status: Closed (was: Pull Request Sent) Fix Version/s: 2.7.0.Final (was: 2.x Future) Resolution: Done > Web Root path in Scaffold should be "/" by default in the UI input > ------------------------------------------------------------------ > > Key: FORGE-1906 > URL: https://issues.jboss.org/browse/FORGE-1906 > Project: Forge > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Scaffold > Affects Versions: 2.5.0.Final > Reporter: George Gastaldi > Assignee: Vineet Reynolds > Fix For: 2.7.0.Final > > > Attention must be paid since this could affect scaffold of existing addons (AngularJS and Faces) -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1907) Spec version pages should be displayed last

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-1907?page=com.atlassian.jira.plugin... ] Vineet Reynolds commented on FORGE-1907: ---------------------------------------- I'm not sure if this is the right thing to do. The spec artifacts need to be installed before the scaffold generation step. Displaying these pages at the end would prevent that and result in errors during scaffold generation (since the facets would not have been installed). > Spec version pages should be displayed last > ------------------------------------------- > > Key: FORGE-1907 > URL: https://issues.jboss.org/browse/FORGE-1907 > Project: Forge > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Java EE > Affects Versions: 2.6.0.Final > Reporter: George Gastaldi > Fix For: 2.x Future > > > AngularJS scaffold and other JavaEE commands ask for spec versions. It should be placed in the last page, since the user can finish the wizard and use the default value. > This is more of a user experience improvement. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1906) Web Root path in Scaffold should be "/" by default in the UI input

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-1906?page=com.atlassian.jira.plugin... ] Vineet Reynolds updated FORGE-1906: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/forge/core/pull/482 This is more or less a cosmetic change. The underlying scaffold providers are currently wired to use empty string ("") as the default and using a slash instead would cause incorrect scaffolds to be generated. Therefore, the slash is converted back to an empty string during processing. > Web Root path in Scaffold should be "/" by default in the UI input > ------------------------------------------------------------------ > > Key: FORGE-1906 > URL: https://issues.jboss.org/browse/FORGE-1906 > Project: Forge > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Scaffold > Affects Versions: 2.5.0.Final > Reporter: George Gastaldi > Assignee: Vineet Reynolds > Fix For: 2.x Future > > > Attention must be paid since this could affect scaffold of existing addons (AngularJS and Faces) -- 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