March 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.1.CR1 (was: 1.0.0.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.1.CR1 > > > 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-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.1.CR1 (was: 1.0.0.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.1.CR1 > > > {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, 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.1.CR1 (was: 1.0.0.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.1.CR1 > > > {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-213) Java EE6 Full Project (follows the EE6 full profile)

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-213?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III updated FORGE-213: ------------------------------------- Fix Version/s: 1.0.1.CR1 (was: 1.0.0.Final) > Java EE6 Full Project (follows the EE6 full profile) > ---------------------------------------------------- > > Key: FORGE-213 > URL: https://issues.jboss.org/browse/FORGE-213 > Project: Forge > Issue Type: Feature Request > Reporter: Burr Sutter > Fix For: 1.0.1.CR1 > > > * Java EE6 Full (follows the EE6 full profile) > HTML > JavaScript > Servlet 3.0 > JSP 2.2 > JSTL 1.2 > JTA 1.1 > JSF 2.0 > - easy to add RichFaces4 > CDI 1.0 > JPA 2.0 > Bean Validation 1.0 > + > EJB 3.1 > JAX-RS 1.1 > JAX-WS 2.2 > JMS 1.1 > Maven -- 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-305) Forge should inform users when they are attempting to run on an unsupported JRE version

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-305?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III updated FORGE-305: ------------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/forge/core/pull/121 > Forge should inform users when they are attempting to run on an unsupported JRE version > --------------------------------------------------------------------------------------- > > Key: FORGE-305 > URL: https://issues.jboss.org/browse/FORGE-305 > Project: Forge > Issue Type: Feature Request > Components: Init Scripts > Affects Versions: 1.0.0.Alpha1 > Reporter: Lincoln Baxter III > Assignee: Lincoln Baxter III > Fix For: 1.0.0.Alpha3 > > > *nix: > #------------------------- > JAVAVER=`$JAVACMD -version 2>&1` > case $JAVAVER in > *1.[6-9]*) ;; > *1.[1-5]*) > echo " Error: a Java 1.6 or higher JRE is required to run Forge; found [$JAVACMD -version == $JAVAVER]." > exit 1 > ;; > esac > *windoze > #----------------------- > ???? -- 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-483) Provide an Option to NOT Include All Dependencies in a Separate Module

by Koen Aers (JIRA)

Koen Aers created FORGE-483: ------------------------------- Summary: Provide an Option to NOT Include All Dependencies in a Separate Module Key: FORGE-483 URL: https://issues.jboss.org/browse/FORGE-483 Project: Forge Issue Type: Feature Request Components: Shell Reporter: Koen Aers Currently the built-in forge plugin bundles all the dependencies of the plugin in a separate module. This is cool but because of this I run into a problem loading JDBC drivers while trying to fix the Hibernate Tools Forge plugin. This problem can be avoided when those dependencies are put as a <resource-root> in the <resources> section of the module.xml of the plugin. I'm not sure if there are any drawbacks of doing so though. -- 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

2
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues March 2012