July 2013 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-1020) Create a documentation plan and outline for Forge 2

by Lincoln Baxter III (JIRA)

Lincoln Baxter III created FORGE-1020: ----------------------------------------- Summary: Create a documentation plan and outline for Forge 2 Key: FORGE-1020 URL: https://issues.jboss.org/browse/FORGE-1020 Project: Forge Issue Type: Task Components: Documentation Affects Versions: 2.0.0.Alpha6 Reporter: Lincoln Baxter III Similar to the following: https://docs.google.com/document/d/17B03_n1OpsdEcqnmha0ch13xjz1pikiEagLgk... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-869) Add a goal to the forge-maven-plugin to generate a graphviz (or other) file for the addon's dependencies

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-869?page=com.atlassian.jira.plugin.... ] George Gastaldi commented on FORGE-869: --------------------------------------- Interesting graph viewer app: http://gephi.org/ > Add a goal to the forge-maven-plugin to generate a graphviz (or other) file for the addon's dependencies > -------------------------------------------------------------------------------------------------------- > > Key: FORGE-869 > URL: https://issues.jboss.org/browse/FORGE-869 > Project: Forge > Issue Type: Feature Request > Components: Maven Plugin > Affects Versions: 2.0.0.Alpha2 > Reporter: George Gastaldi > Priority: Optional > Fix For: 2.x Future > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-869) Add a goal to the forge-maven-plugin to generate a graphviz (or other) file for the addon's dependencies

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-869?page=com.atlassian.jira.plugin.... ] George Gastaldi commented on FORGE-869: --------------------------------------- Graphviz filter for AsciiDoc: http://www.methods.co.nz/asciidoc/asciidoc-graphviz-sample.html > Add a goal to the forge-maven-plugin to generate a graphviz (or other) file for the addon's dependencies > -------------------------------------------------------------------------------------------------------- > > Key: FORGE-869 > URL: https://issues.jboss.org/browse/FORGE-869 > Project: Forge > Issue Type: Feature Request > Components: Maven Plugin > Affects Versions: 2.0.0.Alpha2 > Reporter: George Gastaldi > Priority: Optional > Fix For: 2.x Future > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGEPLUGINS-120) Invalid AngularJS controllers are generated

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGEPLUGINS-120?page=com.atlassian.jira.... ] Vineet Reynolds commented on FORGEPLUGINS-120: ---------------------------------------------- This is due to the type of the class lacking a primary key annotated with {{@Id}}. In this case, the entities generated from the Sakila-H2 model includes the {FilmActor} entity that contains an {{@EmbeddedId}} instead of a plain {{@Id}}. > Invalid AngularJS controllers are generated > ------------------------------------------- > > Key: FORGEPLUGINS-120 > URL: https://issues.jboss.org/browse/FORGEPLUGINS-120 > Project: Forge Plugins > Issue Type: Bug > Components: AngularJS Scaffold > Environment: AngularJS scaffold plugin v1.0.1.Final > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > > The following code is generated in the AngularJS controllers via the Scaffolding plugin: > {noformat} > if($scope.actor.filmActors){ > $.each($scope.actor.filmActors, function(idx, element) { > if(item. == element.) { > $scope.filmActorsSelection.push(wrappedObject); > } > }); > } > {noformat} > Note the invalid comparison expression. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGEPLUGINS-120) Invalid AngularJS controllers are generated

by Vineet Reynolds (JIRA)

Vineet Reynolds created FORGEPLUGINS-120: -------------------------------------------- Summary: Invalid AngularJS controllers are generated Key: FORGEPLUGINS-120 URL: https://issues.jboss.org/browse/FORGEPLUGINS-120 Project: Forge Plugins Issue Type: Bug Components: AngularJS Scaffold Environment: AngularJS scaffold plugin v1.0.1.Final Reporter: Vineet Reynolds Assignee: Vineet Reynolds The following code is generated in the AngularJS controllers via the Scaffolding plugin: {noformat} if($scope.actor.filmActors){ $.each($scope.actor.filmActors, function(idx, element) { if(item. == element.) { $scope.filmActorsSelection.push(wrappedObject); } }); } {noformat} Note the invalid comparison expression. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-192) Make Forge console i18n and L10n compatible

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-192?page=com.atlassian.jira.plugin.... ] Vineet Reynolds edited comment on FORGE-192 at 7/15/13 9:45 PM: ---------------------------------------------------------------- Well, just so that it doesn't get lost somewhere, we should not forget about handling the keyed in characters correctly. Curerntly, the jline fork we use does not handle input characters greater than 0x128 correctly. The following error (or something similar, except for the byte value) is displayed when a unicode character is input: {noformat} [no project] vineet $ ***ERROR*** Exception encountered: Invalid UTF-8 first byte: -127 (type "set VERBOSE true" to enable stack traces) {noformat} The following jline commit: https://github.com/jline/jline2/commit/f728bf8ea9beb4f25c77fb11b54e485e34... has changed the behaviour. I haven't verified is completely, but it's worth looking into. Also worth looking into is SBT, since they're using jline in someway or another, and still manage to get Unicode support for REPL. On Windows, it would be better to use Jansi since it provides APIs to read wide-chars : https://github.com/fusesource/jansi-native/pull/1. was (Author: vineet.reynolds): Well, just so that it doesn't get lost somewhere, we should not forget about handling the keyed in characters correctly. Curerntly, the jline fork we use does not handle input characters greater than 0x128 correctly. The following error (or something similar, except for the byte value) is displayed when a unicode character is input: {noformat} [no project] vineet $ ***ERROR*** Exception encountered: Invalid UTF-8 first byte: -127 (type "set VERBOSE true" to enable stack traces) {noformat} The following jline commit: https://github.com/jline/jline2/commit/f728bf8ea9beb4f25c77fb11b54e485e34... has changed the behaviour. I haven't verified is completely, but it's worth looking into. Also worth looking into is SBT, since they've used jline2 or a fork. > Make Forge console i18n and L10n compatible > ------------------------------------------- > > Key: FORGE-192 > URL: https://issues.jboss.org/browse/FORGE-192 > Project: Forge > Issue Type: Feature Request > Components: Brainstorming, UI - Shell > Affects Versions: 1.0.6.Final > Reporter: George Gastaldi > Fix For: 2.x Future > > > Forge should allow different languages to be used, so that the help messages and commands could be typed on the native speaker developer language. > Example: When a Brazilian Portuguese developer is creating a new project, he would type: "novo-projeto" instead of "new-project". -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-192) Make Forge console i18n and L10n compatible

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-192?page=com.atlassian.jira.plugin.... ] Vineet Reynolds commented on FORGE-192: --------------------------------------- Well, just so that it doesn't get lost somewhere, we should not forget about handling the keyed in characters correctly. Curerntly, the jline fork we use does not handle input characters greater than 0x128 correctly. The following error (or something similar, except for the byte value) is displayed when a unicode character is input: {noformat} [no project] vineet $ ***ERROR*** Exception encountered: Invalid UTF-8 first byte: -127 (type "set VERBOSE true" to enable stack traces) {noformat} The following jline commit: https://github.com/jline/jline2/commit/f728bf8ea9beb4f25c77fb11b54e485e34... has changed the behaviour. I haven't verified is completely, but it's worth looking into. Also worth looking into is SBT, since they've used jline2 or a fork. > Make Forge console i18n and L10n compatible > ------------------------------------------- > > Key: FORGE-192 > URL: https://issues.jboss.org/browse/FORGE-192 > Project: Forge > Issue Type: Feature Request > Components: Brainstorming, UI - Shell > Affects Versions: 1.0.6.Final > Reporter: George Gastaldi > Fix For: 2.x Future > > > Forge should allow different languages to be used, so that the help messages and commands could be typed on the native speaker developer language. > Example: When a Brazilian Portuguese developer is creating a new project, he would type: "novo-projeto" instead of "new-project". -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1017) A valid package name should be computed as default when prompting for a replacement in a JAVA_PACKAGE prompt

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-1017?page=com.atlassian.jira.plugin... ] Vineet Reynolds updated FORGE-1017: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/forge/core/pull/334 Compute a valid package name as default value for prompts of type JAVA_PACKAGE. It is possible for the computed value to be an empty string (or the default package in Java). > A valid package name should be computed as default when prompting for a replacement in a JAVA_PACKAGE prompt > ------------------------------------------------------------------------------------------------------------ > > Key: FORGE-1017 > URL: https://issues.jboss.org/browse/FORGE-1017 > Project: Forge > Issue Type: Enhancement > Affects Versions: 1.3.3.Final > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > > When an invalid package name is supplied as a value for an option whose {{PromptType}} is {{PromptType.JAVA_PACKAGE}}, then Forge prompt again for a valid value. No default is computed, and thus this is not friendly to scripts or to environments like the JBDS 7 Forge wizards where the shell is not accessible directly. > An enhancement is thus sought to compute a valid default value for such cases. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1019) Furnace SE fails to load AddonLifecycleProvider instances

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1019?page=com.atlassian.jira.plugin... ] Lincoln Baxter III closed FORGE-1019. ------------------------------------- Assignee: Lincoln Baxter III Fix Version/s: 2.0.0.Alpha7 Resolution: Done Resolved by adding a ModuleDependency to the Bootpath classlaoder before the Application classloader for passthrough ClassLoader delegation. > Furnace SE fails to load AddonLifecycleProvider instances > --------------------------------------------------------- > > Key: FORGE-1019 > URL: https://issues.jboss.org/browse/FORGE-1019 > Project: Forge > Issue Type: Feature Request > Components: Furnace (Container) > Affects Versions: 2.0.0.Alpha7 > Reporter: Lincoln Baxter III > Assignee: Lincoln Baxter III > Fix For: 2.0.0.Alpha7 > > > Due to the fact that Furnace SE delegates to the Application ClassLoader before teh Bootpath ClassLoader, ServiceLoader cannot instantiate instances of service interfaces from addons, causing lifecycle failures. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1019) Furnace SE fails to load AddonLifecycleProvider instances

by Lincoln Baxter III (JIRA)

Lincoln Baxter III created FORGE-1019: ----------------------------------------- Summary: Furnace SE fails to load AddonLifecycleProvider instances Key: FORGE-1019 URL: https://issues.jboss.org/browse/FORGE-1019 Project: Forge Issue Type: Feature Request Components: Furnace (Container) Affects Versions: 2.0.0.Alpha7 Reporter: Lincoln Baxter III Due to the fact that Furnace SE delegates to the Application ClassLoader before teh Bootpath ClassLoader, ServiceLoader cannot instantiate instances of service interfaces from addons, causing lifecycle failures. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 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 July 2013