April 2012 - forge-issues - Jboss List Archives

[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.3.Final (was: 1.0.2.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.3.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, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-43) Tab completion fails to properly escape spaces in filenames

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-43?page=com.atlassian.jira.plugin.s... ] Lincoln Baxter III updated FORGE-43: ------------------------------------ Fix Version/s: 1.0.3.Final (was: 1.0.2.Final) > Tab completion fails to properly escape spaces in filenames > ----------------------------------------------------------- > > Key: FORGE-43 > URL: https://issues.jboss.org/browse/FORGE-43 > Project: Forge > Issue Type: Bug > Components: Resources API, Shell > Affects Versions: 1.0.0.Beta2 > Reporter: Lincoln Baxter III > Assignee: Mike Brock > Priority: Critical > Fix For: 1.0.3.Final > > > {code}[no project] Desktop $ > [no project] Desktop $ rm Screen shot 2011-07-05 at 1.05.51 PM.png > ? delete: Screen: are you sure? [Y/n] > ***ERROR*** [rm] error deleting files. > [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, 8 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.3.Final (was: 1.0.2.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.3.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, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-275) delete associated methods when deleting a field

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-275?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III commented on FORGE-275: ------------------------------------------ Hi Shameera, First, please read and follow the contributor guide for submitting changes: https://docs.jboss.org/author/display/FORGE/Contribute+or+Get+Involved Second, your approach is fairly good, but this should probably be abstracted from the RmPlugin. I think that the work for deleting relevant fields or methods should probably take place in the JavaResource itself. Possibly even prompting for user input there as well. The RmPlugin, however, should stay generic, and not know what type of resources it is operating on. ~Lincoln > delete associated methods when deleting a field > ----------------------------------------------- > > Key: FORGE-275 > URL: https://issues.jboss.org/browse/FORGE-275 > Project: Forge > Issue Type: Feature Request > Components: Brainstorming, Builtin Plugins > Affects Versions: 1.0.0.Alpha2, 1.0.0.Alpha3 > Reporter: Rodney Russ > Priority: Minor > Attachments: Forge-275.patch > > > When removing a field, it would make sense to remove the associated methods. For example: > cd Person.java > rm firstName > *delete associated methods setFirstName() and getFirstName() (Y/n)? -- 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, 8 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 commented on FORGE-85: ----------------------------------------- There must be a better way to resolve this, that would work for all plugins :) > 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.2.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, 8 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 commented on FORGE-85: ----------------------------------------- Shameera, it's fantastic that you found the root cause! However, I don't think that testing for an individual plugin is the solution here. For instance, using your patch, this would still fail when using an '!' in any other command. > 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.2.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, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-275) delete associated methods when deleting a field

by Shameera Rathanayaka (JIRA)

[ https://issues.jboss.org/browse/FORGE-275?page=com.atlassian.jira.plugin.... ] Shameera Rathanayaka updated FORGE-275: --------------------------------------- Attachment: Forge-275.patch Hi devs , I have attached patch for this. Here i have remove associated getters and setters as the way Rodney suggest and also update the toString method also. Please give me a little feedback on this patch, whether i have done it correct way or not. Because of this modification rm test will fail, i'll fix it ASA and provide a patch if this patch is ok. Thanks, Shameera. > delete associated methods when deleting a field > ----------------------------------------------- > > Key: FORGE-275 > URL: https://issues.jboss.org/browse/FORGE-275 > Project: Forge > Issue Type: Feature Request > Components: Brainstorming, Builtin Plugins > Affects Versions: 1.0.0.Alpha2, 1.0.0.Alpha3 > Reporter: Rodney Russ > Priority: Minor > Attachments: Forge-275.patch > > > When removing a field, it would make sense to remove the associated methods. For example: > cd Person.java > rm firstName > *delete associated methods setFirstName() and getFirstName() (Y/n)? -- 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, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues April 2012