May 2012 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-578) Faces setup fails when project is created with --type war

by George Gastaldi (JIRA)

George Gastaldi created FORGE-578: ------------------------------------- Summary: Faces setup fails when project is created with --type war Key: FORGE-578 URL: https://issues.jboss.org/browse/FORGE-578 Project: Forge Issue Type: Bug Affects Versions: 1.0.5.Final Reporter: George Gastaldi If you run the following commands, you´ll get an error: {code} new-project --named testme --type war faces setup {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

1
4
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.6.Final (was: 1.0.5.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.6.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, 1 month

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.6.Final (was: 1.0.5.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.6.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, 1 month

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.6.Final (was: 1.0.5.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 > Labels: HackNight > Fix For: 1.0.6.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, 1 month

1
0
0 / 0

[JBoss JIRA] (FORGE-579) Create a plugin that can generate an RPM spec from a Maven project

by Dan Allen (JIRA)

[ https://issues.jboss.org/browse/FORGE-579?page=com.atlassian.jira.plugin.... ] Dan Allen deleted FORGE-579: ---------------------------- > Create a plugin that can generate an RPM spec from a Maven project > ------------------------------------------------------------------ > > Key: FORGE-579 > URL: https://issues.jboss.org/browse/FORGE-579 > Project: Forge > Issue Type: Story > Reporter: Dan Allen > Priority: Minor > > All, or nearly all, the information in an RPM spec for a Java package can be derived from the pom.xml files or the build output of a Maven project. Therefore, a Forge plugin could generate a stub RPM spec file to help accelerate the process of packaging a Maven-based application or library for RPM-based distributions (specifically Fedora). > This plugin could also be used to aid in the task of packaging Forge for Fedora. -- 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

1
0
0 / 0

[JBoss JIRA] (FORGE-579) Create a plugin that can generate an RPM spec from a Maven project

by Dan Allen (JIRA)

Dan Allen created FORGE-579: ------------------------------- Summary: Create a plugin that can generate an RPM spec from a Maven project Key: FORGE-579 URL: https://issues.jboss.org/browse/FORGE-579 Project: Forge Issue Type: Story Reporter: Dan Allen Priority: Minor All, or nearly all, the information in an RPM spec for a Java package can be derived from the pom.xml files or the build output of a Maven project. Therefore, a Forge plugin could generate a stub RPM spec file to help accelerate the process of packaging a Maven-based application or library for RPM-based distributions (specifically Fedora). This plugin could also be used to aid in the task of packaging Forge for Fedora. -- 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

1
0
0 / 0

[JBoss JIRA] (FORGE-320) Git-powered "Undo" functionality in Forge

by Jevgeni Zelenkov (JIRA)

[ https://issues.jboss.org/browse/FORGE-320?page=com.atlassian.jira.plugin.... ] Jevgeni Zelenkov reassigned FORGE-320: -------------------------------------- Assignee: Jevgeni Zelenkov > Git-powered "Undo" functionality in Forge > ----------------------------------------- > > Key: FORGE-320 > URL: https://issues.jboss.org/browse/FORGE-320 > Project: Forge > Issue Type: Feature Request > Components: Brainstorming > Environment: All > Reporter: Ian Hands > Assignee: Jevgeni Zelenkov > Priority: Minor > > Forge should support undo/redo of changes on the file system. Use of git would rock here, particularly cases where Forge is introduced to an existing project, and determining what actually changed during a plugin execution could be nasty. > Care should be taken to integrate with projects that are already using git as a version control mechanism. > For example: > {code}I see you are already using git, what branch should Forge use when modifying files? > 1 - org.jboss.forge.history > 2 - define your own?*{code} > After every successful command execution, changes should be committed to the history branch. If an undo is requested, users could be presented with a list of revisions, or simply pop the latest revision off the stack. If a command exits in failure state, the user should be prompted to either "Undo" or "Abort," in which case, if "Undo" is selected, changes made during the failed command execution should be reverted to the previous state - "Abort" simply does nothing. > {code}***ERROR*** Could not complete action [blah]... > ? Undo changes from previous command? [Y/n] {code} > Scenarios: > * Master/current branch is ahead of history branch > * Master/current branch is behind history branch > * How to handle running in detached state? > * How to handle rebasing of a branch to avoid merge commits? -- 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

1
0
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-333) Add proper Facet support for Git

by Lincoln Baxter III (JIRA)

Add proper Facet support for Git -------------------------------- Key: SEAMFORGE-333 URL: https://issues.jboss.org/browse/SEAMFORGE-333 Project: Seam Forge Issue Type: Feature Request Components: Builtin Plugins Reporter: Lincoln Baxter III Fix For: Future -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

2
3
0 / 0

[JBoss JIRA] (FORGE-574) Could not find artifact org.metawidget.forge:metawidget-forge-scaffold:jar:1.0.0-SNAPSHOT in JBOSS_NEXUS (http://repository.jboss.org/nexus/content/groups/public) -> [Help 1]

by Laureano Ruiz (JIRA)

Laureano Ruiz created FORGE-574: ----------------------------------- Summary: Could not find artifact org.metawidget.forge:metawidget-forge-scaffold:jar:1.0.0-SNAPSHOT in JBOSS_NEXUS (http://repository.jboss.org/nexus/content/groups/public) -> [Help 1] Key: FORGE-574 URL: https://issues.jboss.org/browse/FORGE-574 Project: Forge Issue Type: Bug Components: Forge Build Affects Versions: 1.0.0.Beta3 Environment: Apache Maven 3.0.4 (r1232337; 2012-01-17 02:44:56-0600) Maven home: C:\Program Files\Apache Software Foundation\apache-maven-3.0.4 Java version: 1.6.0_20, vendor: Sun Microsystems Inc. Java home: C:\Program Files\Java\jdk1.6.0_20\jre Default locale: en_US, platform encoding: Cp1252 OS name: "windows xp", version: "5.1", arch: "x86", family: "windows" Reporter: Laureano Ruiz Cannot complete the steps in "Generating a basic Java EE web-application" (https://docs.jboss.org/author/display/FORGE/Generating+a+basic+Java+EE+we...) When I get to the build or the mvn clean package, I get the following Maven error: [ERROR] Failed to execute goal on project exampleLR: Could not resolve dependencies for project com.lr.example:exampleLR:war:1.0.0-SNAPSHOT: Could not find artifact org.metawidget.forge:metawidget-forge-scaffold:jar:1.0.0-SNAPSHOT in JBOSS_NEXUS (http://repository.jboss.org/nexus/content/groups/public) -> [Help 1] Looks like the Jar file is not in that location or in Nexus for that version. -- 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
3
0 / 0

[JBoss JIRA] (FORGE-566) Forge fails to resolve BOM

by Pete Muir (JIRA)

Pete Muir created FORGE-566: ------------------------------- Summary: Forge fails to resolve BOM Key: FORGE-566 URL: https://issues.jboss.org/browse/FORGE-566 Project: Forge Issue Type: Bug Reporter: Pete Muir {code} ticket-monster] ticket-monster $ scaffold from-entity org.jboss.jdf.example.ticketmonster.model.* --targetDir admin; ***INFO*** Skipped non-@Entity Java resource [org.jboss.jdf.example.ticketmonster.model.Address] ***INFO*** Skipped non-@Entity Java resource [org.jboss.jdf.example.ticketmonster.model.MediaType] ***INFO*** Skipped non-@Entity Java resource [org.jboss.jdf.example.ticketmonster.model.Seat] ***INFO*** Skipped non-@Entity Java resource [org.jboss.jdf.example.ticketmonster.model.SeatAllocationException] ***INFO*** Using currently installed scaffold [faces] Warning: The encoding 'UTF-8' is not supported by the Java runtime. ***ERROR*** [scaffold from-entity] org.apache.maven.project.ProjectBuildingException: 1 problem was encountered while building the effective model for org.jboss.jdf.examples:ticket-monster:1.0-SNAPSHOT [ERROR] Non-resolvable import POM: Could not find artifact org.richfaces:richfaces-bom:pom:4.0.0.Final @ line 47, column 19 for project org.jboss.jdf.examples:ticket-monster:1.0-SNAPSHOT at /Users/pmuir/workspace/ticket-monster/pom.xml {code} However the BOM is resolved fine when we run a build -- 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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues May 2012