November 2013 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-816) Field command should "pick-up" the newly created field to provide a better user experience with Constraint command

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-816?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III closed FORGE-816. ------------------------------------ Resolution: Won't Fix Feature freeze in Forge 1 dictates that this issue will not be fixed. > Field command should "pick-up" the newly created field to provide a better user experience with Constraint command > ------------------------------------------------------------------------------------------------------------------ > > Key: FORGE-816 > URL: https://issues.jboss.org/browse/FORGE-816 > Project: Forge > Issue Type: Enhancement > Components: Builtin Plugins > Affects Versions: 1.2.2.Final > Reporter: Lincoln Baxter III > Labels: starter > Fix For: 1.x Future > > > {code} > entity --named Customer > field string --named firstName > constraint size --min 0 --max 25 > {code} > Currently, the user must CD into the field in order to add constraints, which is not the most natural interaction. > This will not break scripts because field is still a member of a JavaResource, so new-field should still be available (must verify.) -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (FORGE-193) Validate plugin @Alias, @Command, and @Option names to ensure no duplicates occur

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-193?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III closed FORGE-193. ------------------------------------ Resolution: Won't Fix This will not be fixed in Forge 1. > Validate plugin @Alias, @Command, and @Option names to ensure no duplicates occur > --------------------------------------------------------------------------------- > > Key: FORGE-193 > URL: https://issues.jboss.org/browse/FORGE-193 > Project: Forge > Issue Type: Feature Request > Components: Plugin API, UI - Shell > Affects Versions: 1.0.0.Alpha3 > Reporter: Lincoln Baxter III > Fix For: 2.x Future > > > Should be invalid for same resource scopes > @Alias("whee") > @Alias("whee") > Should be invalid in same command: > @Option(name="named") > @Option(name="named") > And so on... > Or, it should be possible to reference by Fully Qualified Name if this situation does arise (for @Alias.) -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (FORGE-179) The 'open' and 'edit' commands should be configurable

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-179?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III closed FORGE-179. ------------------------------------ Resolution: Won't Fix Will not be fixed. > The 'open' and 'edit' commands should be configurable > ----------------------------------------------------- > > Key: FORGE-179 > URL: https://issues.jboss.org/browse/FORGE-179 > Project: Forge > Issue Type: Enhancement > Components: Builtin Plugins > Affects Versions: 1.0.0.Alpha3 > Reporter: Lincoln Baxter III > Assignee: Koen Aers > Labels: Starter > Fix For: 1.x Future > > > 'open' and 'edit' currently use the default system application, but if hooks were provided into this system, they could instead be used to open files using a user-specified application, or even trigger editors to open in JBoss Tools. > Koen, I am asigning this to you because I want your feedback here. If running forge in eclipse, these commands should probably be a no-op, and your eclipse system will simply intercept the output and open/edit the desired file, yes? -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (FORGE-162) Reload the current project/resource metadata when filesystem changes occur

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-162?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III closed FORGE-162. ------------------------------------ Assignee: Lincoln Baxter III Fix Version/s: 2.0.0.Beta4 (was: 2.x Future) Resolution: Done Implemented via ProjectCache and the FileMonitor API. > Reload the current project/resource metadata when filesystem changes occur > -------------------------------------------------------------------------- > > Key: FORGE-162 > URL: https://issues.jboss.org/browse/FORGE-162 > Project: Forge > Issue Type: Enhancement > Components: Event Bus, Resources API > Affects Versions: 1.0.0.Alpha4 > Reporter: Lincoln Baxter III > Assignee: Lincoln Baxter III > Fix For: 2.0.0.Beta4 > > > When project filesystem changes occur, the project can be in a relatively inconsistent state, where facets are not available but are still registered (this is currently detected, but we should probably just fix this the real way by reloading the project metadata) -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (FORGE-379) Add user profiles

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-379?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III closed FORGE-379. ------------------------------------ Resolution: Won't Fix We are attempting to work on this by improving the usability in different ways. Mostly via elimination of prompts altogether, and simply showing a set of changes that the user gets to accept or reject. > Add user profiles > ----------------- > > Key: FORGE-379 > URL: https://issues.jboss.org/browse/FORGE-379 > Project: Forge > Issue Type: Feature Request > Components: Usability > Affects Versions: 1.0.0.Beta3 > Reporter: Pete Muir > Fix For: 2.x Future > > > At the moment Forge assumes that every user needs the same level of hand-holding. This means that advanced users are shortchanged (as they want more control) and newbies can get lost. Introducing a number of user profiles (e.g. newbie, intermediate, god) could help here. For example, if in newbie mode, the faces plugin wouldn't ask if you wanted to change from jar -> war packaging, assuming that the person does... -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (FORGE-1283) JBoss Forge definition in Website

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1283?page=com.atlassian.jira.plugin... ] Lincoln Baxter III updated FORGE-1283: -------------------------------------- Fix Version/s: 2.x Future > JBoss Forge definition in Website > --------------------------------- > > Key: FORGE-1283 > URL: https://issues.jboss.org/browse/FORGE-1283 > Project: Forge > Issue Type: Enhancement > Components: Website > Affects Versions: 2.x Future > Reporter: George Gastaldi > Priority: Trivial > Fix For: 2.x Future > > > The website does not make clear what Forge really is. It would be nice if Forge could be summarized in one statement in the website. -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (FORGE-978) Introduce support for scaffolding immutable types

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-978?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III updated FORGE-978: ------------------------------------- Fix Version/s: 2.x Future > Introduce support for scaffolding immutable types > ------------------------------------------------- > > Key: FORGE-978 > URL: https://issues.jboss.org/browse/FORGE-978 > Project: Forge > Issue Type: Feature Request > Components: Scaffold > Affects Versions: 1.3.2.Final > Reporter: Vineet Reynolds > Priority: Minor > Fix For: 2.x Future > > > Currently JPA entities detected as immutable types are exempted from scaffolding (due to FORGE-917). However if these types are composed in other entities then the generated scaffold becomes no-functional/buggy (FORGE-972). > Therefore, it makes sense to properly scaffold such entities. Detection of the correct constructor for the immutable type is paramount to generating the scaffold correctly. > It may be necessary to create additional mutable types that mirror the immutable type, for usage in the CDI beans. This would also enable the use of EL expressions in the Facelets whose usage will not result in PropertyNotWritableException exceptions being thrown. -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (FORGE-1267) rest/ResourceGeneratorUtil generates bogus id name from Method

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1267?page=com.atlassian.jira.plugin... ] Lincoln Baxter III updated FORGE-1267: -------------------------------------- Fix Version/s: 2.x Future > rest/ResourceGeneratorUtil generates bogus id name from Method > -------------------------------------------------------------- > > Key: FORGE-1267 > URL: https://issues.jboss.org/browse/FORGE-1267 > Project: Forge > Issue Type: Bug > Components: Java EE APIs > Affects Versions: 1.4.2.Final, 2.0.0.Alpha13 > Reporter: Thomas Maslen > Priority: Minor > Fix For: 2.x Future > > > The "rest endpoint-from-entity" command uses this class (ResourceGeneratorUtil). > Everything works fine if the @Id annotation is attached to a field. > However, if the @Id annotation is attached to the setXYZ() or getXYZ() method, ResourceGeneratorUtil ends up producing an incorrect name for the id property: the name should be "xyz" but this class incorrectly produces "txyz". > The problem is that the code in ResourceGeneratorUtil invokes substring(2) when it should actually have used substring(3). One site in the class correctly uses substring(3) but there are four other sites that use substring(2). > The workaround is to attach @Id to the field, not to the setter or getter methods. > Probably this bug has lain low because (a) the "entity" command always attaches @Id to the field, and (b) the JBoss Tools "New JPA Entity" wizard has an "Access Type" radio button that defaults to using the field, so the bug is only triggered if you explicitly change the radio button (or use an editor to attach the @Id annotation). -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (FORGE-1321) Failure to install addons when using Artifactory repositories using centrally secured passwords

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1321?page=com.atlassian.jira.plugin... ] Lincoln Baxter III updated FORGE-1321: -------------------------------------- Fix Version/s: 2.x Future > Failure to install addons when using Artifactory repositories using centrally secured passwords > ----------------------------------------------------------------------------------------------- > > Key: FORGE-1321 > URL: https://issues.jboss.org/browse/FORGE-1321 > Project: Forge > Issue Type: Bug > Components: Build Tools - Maven > Affects Versions: 2.0.0.Beta3 > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > Fix For: 2.x Future > > > After FORGE-1307, Forge seems to be able to access secure repositories, but fails to install the addon: > {noformat} > forge-distribution-2.0.0.Beta2$ ./bin/forge --install shell > Using Forge at forge-distribution-2.0.0.Beta2 > Warning: JAVA_HOME environment variable is not set. > Downloading: http://xxxxxx/artifactory/repo/org/jboss/forge/addon/shell/maven-metadata... > Downloading: http://xxxxxx/artifactory/repo/org/jboss/forge/addon/shell/maven-metadata... > java.lang.IllegalArgumentException: No Artifact version found for org.jboss.forge.addon:shell > at org.jboss.forge.bootstrap.Bootstrap.install(Bootstrap.java:199) > at org.jboss.forge.bootstrap.Bootstrap.<init>(Bootstrap.java:144) > at org.jboss.forge.bootstrap.Bootstrap.main(Bootstrap.java:88) > > Forge version [2.0.0.Beta1] > {noformat} > The Artifactory repository used this feature: http://www.jfrog.com/confluence/display/RTF/Centrally+Secure+Passwords > Additional info: > {noformat} > <dbeer> think I have found part of issue I have removed security constraint briefly from our server and is now downloading a load of forge addon snapshots, will investigate the security further tomorrow > {noformat} -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (FORGE-1252) Support Maven enhanced AddonRepository implementation

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1252?page=com.atlassian.jira.plugin... ] Lincoln Baxter III updated FORGE-1252: -------------------------------------- Fix Version/s: 2.x Future > Support Maven enhanced AddonRepository implementation > ----------------------------------------------------- > > Key: FORGE-1252 > URL: https://issues.jboss.org/browse/FORGE-1252 > Project: Forge > Issue Type: Feature Request > Components: Furnace (Container) > Affects Versions: 2.0.0.Alpha13 > Reporter: Lincoln Baxter III > Fix For: 2.x Future > > > This would basically be a repository that delegates required artifacts to the local maven repository, preventing the need for an IO expensive install operation. > ..... > we could always make a versioned repository with the native filesystem > 10:57 it would be simpler and less error prone than relying on a full VCS integration provided by either the OS or the runtime tools > 10:57 it takes more spcae > 10:57 space > 10:57 but it is simpler > 10:58 i think that the best solution would be to implement a fully maven-backed solution > 10:58 that simply uses pointers into the local maven repository isntead of copying JAR files > 10:58 then we don't duplicate any space -- 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

11 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues November 2013