April 2012 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-555) tab completion appends wrongly escapes last space of a unique candidate

by Koen Aers (JIRA)

Koen Aers created FORGE-555: ------------------------------- Summary: tab completion appends wrongly escapes last space of a unique candidate Key: FORGE-555 URL: https://issues.jboss.org/browse/FORGE-555 Project: Forge Issue Type: Bug Reporter: Koen Aers Assignee: Koen Aers Fix For: 1.0.3.Final This is a glitch resulting from the implementation of FORGE-43: type 'new-pro' + tab results in 'new-project\ '. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

2
4
0 / 0

[JBoss JIRA] (FORGE-521) Fix the formatting of Forge-generated JPA entity

by Ivan St. Ivanov (JIRA)

Ivan St. Ivanov created FORGE-521: ------------------------------------- Summary: Fix the formatting of Forge-generated JPA entity Key: FORGE-521 URL: https://issues.jboss.org/browse/FORGE-521 Project: Forge Issue Type: Enhancement Components: Builtin Plugins Reporter: Ivan St. Ivanov Fix For: 1.0.2.Final An entity generated by Forge looks like this: package com.test.entity; // Some imports go here // below is the last import, and not only import java.lang.Override;@Entity public class Employee implements java.io.Serializable { It's ugly because the statements on the last line above should be on at least three (and at best four) separate lines: import java.lang.Override; @Entity public class Employee implements java.io.Serializable { -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

2
7
0 / 0

[JBoss JIRA] (FORGE-550) Should be able to list all available (not necessarily in use) scaffold providers

by Lincoln Baxter III (JIRA)

Lincoln Baxter III created FORGE-550: ---------------------------------------- Summary: Should be able to list all available (not necessarily in use) scaffold providers Key: FORGE-550 URL: https://issues.jboss.org/browse/FORGE-550 Project: Forge Issue Type: Enhancement Components: Scaffold Affects Versions: 1.0.2.Final Reporter: Lincoln Baxter III Right now the only way to "discover" which types of scaffold are installed is to either: a) Check your installed plugins b) type: "scaffold setup --scaffoldType <TAB>" and see which options it comes up with as completion proposals. It would be grand to have a "scaffold list-providers" command, to list and display basic information about each scaffold. E.g: {code} $ scaffold list-providers * Aerogear: Basic PoH5 & Rest Mobile Scaffolding * Faces: JavaServer Faces scaffolding * SpringMVC: What it sounds like... {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

2
6
0 / 0

[JBoss JIRA] (FORGE-32) FSHParser is too agressive (destroys command input)

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-32?page=com.atlassian.jira.plugin.s... ] Lincoln Baxter III updated FORGE-32: ------------------------------------ Fix Version/s: 1.0.5.Final (was: 1.0.4.Final) > FSHParser is too agressive (destroys command input) > --------------------------------------------------- > > Key: FORGE-32 > URL: https://issues.jboss.org/browse/FORGE-32 > Project: Forge > Issue Type: Bug > Components: Shell > Affects Versions: 1.0.0.Beta2 > Reporter: Lincoln Baxter III > Assignee: Mike Brock > Priority: Critical > Fix For: 1.0.5.Final > > > FSHParser is breaking up statements that clearly are not scripts: > [example] Customer.java $ prettyfaces mapping --resource /scaffold/customer/view.xhtml --pattern /customer/#{id} --id viewCustomer > ***INFO*** The command [mapping] takes [0] unnamed argument(s), but found [1]. > ***INFO*** Swallowed unknown token [{] for command [mapping]. > ***INFO*** Swallowed unknown token [id] for command [mapping]. > ***INFO*** Swallowed unknown token [}] for command [mapping]. > ... etc > [example] Customer.java $ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-33) Pathspec parser does not properly handle Regex character in input (revealed when using tab-completion)

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-33?page=com.atlassian.jira.plugin.s... ] Lincoln Baxter III updated FORGE-33: ------------------------------------ Fix Version/s: 1.0.5.Final (was: 1.0.4.Final) > Pathspec parser does not properly handle Regex character in input (revealed when using tab-completion) > ------------------------------------------------------------------------------------------------------ > > Key: FORGE-33 > URL: https://issues.jboss.org/browse/FORGE-33 > Project: Forge > Issue Type: Bug > Components: Shell > Affects Versions: 1.0.0.Beta2 > Environment: Ubuntu > Reporter: Lincoln Baxter III > Assignee: Mike Brock > Priority: Critical > Fix For: 1.0.5.Final > > > cd I(<TAB>" > results in: > [forge-distribution] dist $ set verbose on > [forge-distribution] dist $ cd ~/Desktop/ > [no project] Desktop $ cd I(<TAB>[INFO] ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] ------------------------------------------------------------------------ > [INFO] Total time: 17.077s > [INFO] Finished at: Tue Dec 14 18:56:28 EST 2010 > [INFO] Final Memory: 16M/218M > [INFO] ------------------------------------------------------------------------ > [ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.1.1:java (default-cli) on project forge-distribution: An exception occured while executing the Java class. null: InvocationTargetException: Unclosed group near index 6 > [ERROR] ^I(.*$ > [ERROR] ^ > [ERROR] -> [Help 1] > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.1.1:java (default-cli) on project forge-distribution: An exception occured while executing the Java class. null > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:203) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:140) > at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) > at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) > at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) > at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:314) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:151) > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:445) > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:168) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:132) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) > at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) > at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) > at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) > Caused by: org.apache.maven.plugin.MojoExecutionException: An exception occured while executing the Java class. null > at org.codehaus.mojo.exec.ExecJavaMojo.execute(ExecJavaMojo.java:338) > at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:107) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:195) > ... 19 more > Caused by: java.lang.reflect.InvocationTargetException > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.codehaus.mojo.exec.ExecJavaMojo$1.run(ExecJavaMojo.java:283) > at java.lang.Thread.run(Thread.java:619) > Caused by: java.util.regex.PatternSyntaxException: Unclosed group near index 6 > ^I(.*$ > ^ > at java.util.regex.Pattern.error(Pattern.java:1713) > at java.util.regex.Pattern.accept(Pattern.java:1571) > at java.util.regex.Pattern.group0(Pattern.java:2533) > at java.util.regex.Pattern.sequence(Pattern.java:1806) > at java.util.regex.Pattern.expr(Pattern.java:1752) > at java.util.regex.Pattern.compile(Pattern.java:1460) > at java.util.regex.Pattern.<init>(Pattern.java:1133) > at java.util.regex.Pattern.compile(Pattern.java:823) > at org.jboss.seam.forge.project.util.PathspecParser.resolve(PathspecParser.java:130) > at org.jboss.seam.forge.shell.completer.PluginCommandCompleter.getOptionCandidates(PluginCommandCompleter.java:337) > at org.jboss.seam.forge.shell.completer.PluginCommandCompleter.complete(PluginCommandCompleter.java:173) > at org.jboss.seam.forge.shell.completer.CommandCompleterAdaptor.complete(CommandCompleterAdaptor.java:49) > at jline.console.completer.AggregateCompleter$Completion.complete(AggregateCompleter.java:105) > at jline.console.completer.AggregateCompleter.complete(AggregateCompleter.java:66) > at jline.console.ConsoleReader.complete(ConsoleReader.java:1101) > at jline.console.ConsoleReader.readLine(ConsoleReader.java:898) > at jline.console.ConsoleReader.readLine(ConsoleReader.java:834) > at jline.console.ConsoleReader.readLine(ConsoleReader.java:822) > at org.jboss.seam.forge.shell.ShellImpl.readLine(ShellImpl.java:265) > at org.jboss.seam.forge.shell.ShellImpl.doShell(ShellImpl.java:246) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.jboss.weld.util.reflection.SecureReflections$13.work(SecureReflections.java:305) > at org.jboss.weld.util.reflection.SecureReflectionAccess.run(SecureReflectionAccess.java:54) > at org.jboss.weld.util.reflection.SecureReflectionAccess.runAsInvocation(SecureReflectionAccess.java:163) > at org.jboss.weld.util.reflection.SecureReflections.invoke(SecureReflections.java:299) > at org.jboss.weld.introspector.jlr.WeldMethodImpl.invokeOnInstance(WeldMethodImpl.java:198) > at org.jboss.weld.introspector.ForwardingWeldMethod.invokeOnInstance(ForwardingWeldMethod.java:59) > at org.jboss.weld.injection.MethodInjectionPoint.invokeOnInstanceWithSpecialValue(MethodInjectionPoint.java:200) > at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:270) > at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:253) > at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:222) > at org.jboss.weld.manager.BeanManagerImpl.notifyObservers(BeanManagerImpl.java:605) > at org.jboss.weld.manager.BeanManagerImpl.fireEvent(BeanManagerImpl.java:598) > at org.jboss.weld.manager.BeanManagerImpl.fireEvent(BeanManagerImpl.java:592) > at org.jboss.seam.forge.shell.Bootstrap.main(Bootstrap.java:56) > ... 6 more > [ERROR] > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please read the following articles: > [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException > lb3@quadshark ~/JBoss/forge/dist $ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-85) Shell cannot parse command values containing '!' exclaimation points

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-85?page=com.atlassian.jira.plugin.s... ] Lincoln Baxter III updated FORGE-85: ------------------------------------ Fix Version/s: 1.0.5.Final (was: 1.0.4.Final) > Shell cannot parse command values containing '!' exclaimation points > -------------------------------------------------------------------- > > Key: FORGE-85 > URL: https://issues.jboss.org/browse/FORGE-85 > Project: Forge > Issue Type: Bug > Components: Shell > Affects Versions: 1.0.0.Beta2 > Reporter: Lincoln Baxter III > Assignee: Mike Brock > Priority: Critical > Fix For: 1.0.5.Final > > Attachments: Forge-85.patch > > > {code} > [pfdemo] pfdemo $ echo sdfdf! > sdfdf ! > [pfdemo] pfdemo $ echo sdfdf!sdf > ***ERROR*** Exception encountered: !sdf: event not found (type "set VERBOSE true" to enable stack traces) > [pfdemo] pfdemo $ > [pfdemo] pfdemo $ echo 'asdf!asdf` > ***ERROR*** Exception encountered: !asdf`: event not found (type "set VERBOSE true" to enable stack traces) > [pfdemo] pfdemo $ > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-376) FSH parser cannot understand filenames with spaces

by Lincoln Baxter III (Created) (JIRA)

FSH parser cannot understand filenames with spaces -------------------------------------------------- Key: FORGE-376 URL: https://issues.jboss.org/browse/FORGE-376 Project: Forge Issue Type: Bug Components: Forge Scripting Language Affects Versions: 1.0.0.Beta3 Reporter: Lincoln Baxter III Assignee: Mike Brock Fix For: 1.0.0.Final {code} socialpm.png [no project] Desktop $ rm Screen Shot 2011-11-09 at 11.27.15 AM.png ? delete: Screen: are you sure? [Y/n] ***ERROR*** [rm] error deleting files. [no project] Desktop $ [no project] Desktop $ [no project] Desktop $ [no project] Desktop $ [no project] Desktop $ rm Screen\ Shot\ 2011-11-09\ at\ 11.27.15\ AM.png ? delete: Screen\: are you sure? [Y/n] ***ERROR*** [rm] error deleting files. [no project] Desktop $ ls BlueAngels/ Buffer/ forge-tools.png google-2-step-codes.png JBoss/ OriginsOfForge.odt P90x/ Recordings/ Screen Shot 2011-11-09 at 11.27.15 AM.png showcase/ socialpm.png [no project] Desktop $ rm -rf Screen Shot 2011-11-09 at 11.27.15 AM.png^C [no project] Desktop $ rm -rf Screen* Deleted /Users/lbaxter/Desktop/Screen Shot 2011-11-09 at 11.27.15 AM.png [no project] Desktop $ ls BlueAngels/ Buffer/ forge-tools.png JBoss/ OriginsOfForge.odt Recordings/ showcase/ socialpm.png [no project] Desktop $ {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

3
7
0 / 0

[JBoss JIRA] (FORGE-547) @Alias should be a CDI Qualifier

by Lincoln Baxter III (JIRA)

Lincoln Baxter III created FORGE-547: ---------------------------------------- Summary: @Alias should be a CDI Qualifier Key: FORGE-547 URL: https://issues.jboss.org/browse/FORGE-547 Project: Forge Issue Type: Enhancement Components: Plugin API Affects Versions: 1.0.2.Final Reporter: Lincoln Baxter III Fix For: 1.0.3.Final I've been working on the Facet construct internals quite a bit over the last few days, with the way Constraint lookups are performed; I realized that if you wrap a Facet with an Interceptor or Decorator, you can no longer inspect the constraints for that facet because you are in fact inspecting the Java Proxy object, not the Facet class itself. I believe this change is required to support such behavior. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
3
0 / 0

[JBoss JIRA] (FORGE-556) Add --debug option to forge

by George Gastaldi (JIRA)

George Gastaldi created FORGE-556: ------------------------------------- Summary: Add --debug option to forge Key: FORGE-556 URL: https://issues.jboss.org/browse/FORGE-556 Project: Forge Issue Type: Feature Request Components: Init Scripts Reporter: George Gastaldi In order to ease debugging, it should be possible to start forge with a --debug flag -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
4
0 / 0

[JBoss JIRA] (FORGE-422) creating a new option "evaluate"

by Jan Papousek (Created) (JIRA)

creating a new option "evaluate" -------------------------------- Key: FORGE-422 URL: https://issues.jboss.org/browse/FORGE-422 Project: Forge Issue Type: Feature Request Affects Versions: 1.0.0.Beta5 Reporter: Jan Papousek I would be nice to add an option (*--evaluate* or *-e* for short) for evaluating commands without going into the forge console. Example: {code} forge -e /path/to/script.fsh {code} It's hard to write bash scripts using forge without this option. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

5
16
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues April 2012