August 2017 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-2733) bug in either forge REST API or in obsidian front end

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2733?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-2733. ---------------------------------- Resolution: Out of Date > bug in either forge REST API or in obsidian front end > ----------------------------------------------------- > > Key: FORGE-2733 > URL: https://issues.jboss.org/browse/FORGE-2733 > Project: Forge > Issue Type: Bug > Reporter: James Strachan > > I managed to get this exception just now: > {code} > 2017-02-28 10:01:27,355 ERROR [io.undertow.request] (default task-20) UT005023: Exception handling request to /forge/commands/obsidian-new-quickstart/validate: org.jboss.resteasy.spi.UnhandledException: java.lang.IndexOutOfBoundsException: Index: 4, Size: 4 > at org.jboss.resteasy.core.ExceptionHandler.handleApplicationException(ExceptionHandler.java:77) > at org.jboss.resteasy.core.ExceptionHandler.handleException(ExceptionHandler.java:220) > at org.jboss.resteasy.core.SynchronousDispatcher.writeException(SynchronousDispatcher.java:175) > at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:418) > at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:209) > at org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:221) > at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:56) > at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:51) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) > at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:85) > at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:62) > at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) > at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at org.wildfly.swarm.generated.FaviconErrorHandler.handleRequest(FaviconErrorHandler.java:62) > at io.undertow.server.handlers.PathHandler.handleRequest(PathHandler.java:94) > at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:131) > at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:57) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46) > at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64) > at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:60) > at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:77) > at io.undertow.security.handlers.NotificationReceiverHandler.handleRequest(NotificationReceiverHandler.java:50) > at io.undertow.security.handlers.AbstractSecurityContextAssociationHandler.handleRequest(AbstractSecurityContextAssociationHandler.java:43) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:292) > at io.undertow.servlet.handlers.ServletInitialHandler.access$100(ServletInitialHandler.java:81) > at io.undertow.servlet.handlers.ServletInitialHandler$2.call(ServletInitialHandler.java:138) > at io.undertow.servlet.handlers.ServletInitialHandler$2.call(ServletInitialHandler.java:135) > at io.undertow.servlet.core.ServletRequestContextThreadSetupAction$1.call(ServletRequestContextThreadSetupAction.java:48) > at io.undertow.servlet.core.ContextClassLoaderSetupAction$1.call(ContextClassLoaderSetupAction.java:43) > at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44) > at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44) > at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44) > at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44) > at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:272) > at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:81) > at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:104) > at io.undertow.server.Connectors.executeRootHandler(Connectors.java:202) > at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:805) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.lang.IndexOutOfBoundsException: Index: 4, Size: 4 > at java.util.ArrayList.rangeCheck(ArrayList.java:653) > at java.util.ArrayList.get(ArrayList.java:429) > at org.jboss.forge.addon.ui.impl.controller.WizardCommandControllerImpl.getCurrentEntry(WizardCommandControllerImpl.java:493) > at org.jboss.forge.addon.ui.impl.controller.WizardCommandControllerImpl.getCurrentController(WizardCommandControllerImpl.java:504) > at org.jboss.forge.addon.ui.impl.controller.WizardCommandControllerImpl.isInitialized(WizardCommandControllerImpl.java:127) > at org.jboss.forge.addon.ui.impl.controller.AbstractCommandController.assertInitialized(AbstractCommandController.java:55) > at org.jboss.forge.addon.ui.impl.controller.WizardCommandControllerImpl.canMoveToNextStep(WizardCommandControllerImpl.java:298) > at org.jboss.forge.addon.ui.impl.controller.NoUIWizardControllerDecorator.canMoveToNextStep(NoUIWizardControllerDecorator.java:52) > at sun.reflect.GeneratedMethodAccessor280.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback$2.call(ClassLoaderAdapterCallback.java:124) > at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42) > at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.invoke(ClassLoaderAdapterCallback.java:97) > at org.jboss.forge.addon.ui.controller.CommandController_$$_javassist_6eedec42-b625-4979-a432-d20d894e7b45.canMoveToNextStep(CommandController_$$_javassist_6eedec42-b625-4979-a432-d20d894e7b45.java) > at org.jboss.forge.service.util.UICommandHelper.describeCurrentState(UICommandHelper.java:83) > at org.obsidiantoaster.generator.rest.ObsidianResource.validateCommand(ObsidianResource.java:192) > at org.obsidiantoaster.generator.rest.ObsidianResource$Proxy$_$$_WeldClientProxy.validateCommand(Unknown Source) > at sun.reflect.GeneratedMethodAccessor546.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:139) > at org.jboss.resteasy.core.ResourceMethodInvoker.invokeOnTarget(ResourceMethodInvoker.java:295) > at org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:249) > at org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:236) > at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:402) > {code} > as I clicked on the last page of a 4 page wizard. Not sure if its a front end bug or not. The last posted form data was: > {code} > stepIndex:3 > type:Creates a new Spring Boot Tomcat - Rest & Config Map > named:demo26 > topLevelPackage:com.example > version:1.0.0-SNAPSHOT > pipeline:CanaryRelease > gitOrganisation:jstrachan > gitRepository:demo26 > gitRepoDescription:undefined > kubernetesSpace:team > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1599) Introduce a cache addon

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1599?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1599. ---------------------------------- Fix Version/s: (was: 3.x Future) Assignee: George Gastaldi (was: Adam Wyłuda) Resolution: Done Created Cache addon separated from forge/core > Introduce a cache addon > ----------------------- > > Key: FORGE-1599 > URL: https://issues.jboss.org/browse/FORGE-1599 > Project: Forge > Issue Type: Feature Request > Components: Blessed Plugins > Reporter: George Gastaldi > Assignee: George Gastaldi > > This would allow other addons to cache state. It should allow individual configurations of each cache. > There should also have a CacheFactory, to allow creation of caches on-demand. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-852) RSS based news mechanism

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-852?page=com.atlassian.jira.plugin.... ] George Gastaldi commented on FORGE-852: --------------------------------------- Atom URL: http://forge.jboss.org/atom.xml > RSS based news mechanism > ------------------------ > > Key: FORGE-852 > URL: https://issues.jboss.org/browse/FORGE-852 > Project: Forge > Issue Type: Feature Request > Components: Builtin Plugins, Usability > Affects Versions: 1.2.2.Final > Reporter: Michal Matloka > Fix For: 3.x Future > > > On Forge startup user could see a message e.g. taken from Forge RSS. This could help in such situations like this: http://forge.jboss.org/news/2013/04/08/forge-update.html > Possible workflow: > run forge -> request to rss/sth -> retrieved important messages -> show to user in e.g. console > Console is a starting point. It possibly could be developed into a more generic mechanism which could be used under different interfaces. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2760) cdi-setup and scaffold fail

by George Labuschagne (JIRA)

[ https://issues.jboss.org/browse/FORGE-2760?page=com.atlassian.jira.plugin... ] George Labuschagne deleted FORGE-2760: -------------------------------------- > cdi-setup and scaffold fail > --------------------------- > > Key: FORGE-2760 > URL: https://issues.jboss.org/browse/FORGE-2760 > Project: Forge > Issue Type: Bug > Environment: CentOS 7.3 > Forge 3.7.2 > Java OpenJDK Runtime Environment (build 1.8.0_141-b16) > Apache Maven 3.5.0 > Reporter: George Labuschagne > > Attempting to run 'cdi-setup' or 'scaffold-setup --provider Faces' results in the following error message: > ***ERROR*** Could not install CDI. > Where last line of log file reads: > 19:56:22,799 SEVERE [org.jboss.forge.addon.shell.aesh.CommandAdapter] (AeshProcess: 1) Could not install CDI. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2760) cdi-setup and scaffold fail

by George Labuschagne (JIRA)

[ https://issues.jboss.org/browse/FORGE-2760?page=com.atlassian.jira.plugin... ] George Labuschagne updated FORGE-2760: -------------------------------------- Attachment: pom.xml > cdi-setup and scaffold fail > --------------------------- > > Key: FORGE-2760 > URL: https://issues.jboss.org/browse/FORGE-2760 > Project: Forge > Issue Type: Bug > Components: Furnace CDI, Scaffold > Affects Versions: 3.7.2.Final > Environment: CentOS 7.3 > Forge 3.7.2 > Java OpenJDK Runtime Environment (build 1.8.0_141-b16) > Apache Maven 3.5.0 > Reporter: George Labuschagne > Attachments: forge.log, pom.xml, pom.xml, src.tar.gz > > > Attempting to run 'cdi-setup' or 'scaffold-setup --provider Faces' results in the following error message: > ***ERROR*** Could not install CDI. > Where last line of log file reads: > 19:56:22,799 SEVERE [org.jboss.forge.addon.shell.aesh.CommandAdapter] (AeshProcess: 1) Could not install CDI. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2760) cdi-setup and scaffold fail

by George Labuschagne (JIRA)

[ https://issues.jboss.org/browse/FORGE-2760?page=com.atlassian.jira.plugin... ] George Labuschagne commented on FORGE-2760: ------------------------------------------- Resolved the issue, the bug was between the keyboard and the chair. I uploaded a new POM file that does not encounter this issue. > cdi-setup and scaffold fail > --------------------------- > > Key: FORGE-2760 > URL: https://issues.jboss.org/browse/FORGE-2760 > Project: Forge > Issue Type: Bug > Components: Furnace CDI, Scaffold > Affects Versions: 3.7.2.Final > Environment: CentOS 7.3 > Forge 3.7.2 > Java OpenJDK Runtime Environment (build 1.8.0_141-b16) > Apache Maven 3.5.0 > Reporter: George Labuschagne > Attachments: forge.log, pom.xml, src.tar.gz > > > Attempting to run 'cdi-setup' or 'scaffold-setup --provider Faces' results in the following error message: > ***ERROR*** Could not install CDI. > Where last line of log file reads: > 19:56:22,799 SEVERE [org.jboss.forge.addon.shell.aesh.CommandAdapter] (AeshProcess: 1) Could not install CDI. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2760) cdi-setup and scaffold fail

by George Labuschagne (JIRA)

[ https://issues.jboss.org/browse/FORGE-2760?page=com.atlassian.jira.plugin... ] George Labuschagne edited comment on FORGE-2760 at 8/19/17 8:28 AM: -------------------------------------------------------------------- Hi George, indeed! :) I have the latest Forge extracted such that the bin is located at: ~/opt/forge/bin {code:bash} [georgel@devbox ~]$ which forge ~/opt/forge/bin/forge {code} The project is located at: {code:bash} [georgel@devbox edsnext]$ pwd /home/georgel/coding/edsnext [georgel@devbox edsnext]$ ls edsnext.iml pom.xml src target [georgel@devbox edsnext]$ {code} I uploaded now a copy of the src directory as well (it is tiny at the moment). When logging in to forge and then running either run 'cdi-setup' or 'scaffold-setup --provider Faces' I get the error as below: {code:bash} [georgel@devbox edsnext]$ forge Using Forge at /home/georgel/opt/forge _____ | ___|__ _ __ __ _ ___ | |_ / _ \| `__/ _` |/ _ \ \\ | _| (_) | | | (_| | __/ // |_| \___/|_| \__, |\___| |__/ JBoss Forge, version [ 3.7.2.Final ] - JBoss, by Red Hat, Inc. [ http://forge.jboss.org ] Hit '<TAB>' for a list of available commands and 'man [cmd]' for help on a specific command. To quit the shell, type 'exit'. [edsnext]$ cdi-setup ***ERROR*** Could not install CDI. [edsnext]$ scaffold-setup --provider Faces ***ERROR*** Could not install CDI. ***SUCCESS*** Scaffold was setup successfully. [edsnext]$ {code} Please let me know if you require any other info and thanks for looking into this; it is most appreciated. was (Author: george.labuschagne): Hi George, indeed! :) I have the latest Forge extracted such that the bin is located at: ~/opt/forge/bin {code:bash} [georgel@devbox ~]$ which forge ~/opt/forge/bin/forge {code} The project is located at: {code:bash} [georgel@devbox edsnext]$ pwd /home/georgel/coding/edsnext [georgel@devbox edsnext]$ ls edsnext.iml pom.xml src target [georgel@devbox edsnext]$ {code} I uploaded now a copy of the src directory as well (it is tiny at the moment). When logging in to forge and then running either run 'cdi-setup' or 'scaffold-setup --provider Faces' I get the error as below: {code:bash} [georgel@devbox edsnext]$ forge Using Forge at /home/georgel/opt/forge _____ | ___|__ _ __ __ _ ___ | |_ / _ \| `__/ _` |/ _ \ \\ | _| (_) | | | (_| | __/ // |_| \___/|_| \__, |\___| |__/ JBoss Forge, version [ 3.7.2.Final ] - JBoss, by Red Hat, Inc. [ http://forge.jboss.org ] Hit '<TAB>' for a list of available commands and 'man [cmd]' for help on a specific command. To quit the shell, type 'exit'. [edsnext]$ cdi-setup ***ERROR*** Could not install CDI. [edsnext]$ scaffold-setup --provider Faces ***ERROR*** Could not install CDI. ***SUCCESS*** Scaffold was setup successfully. [edsnext]$ {code} > cdi-setup and scaffold fail > --------------------------- > > Key: FORGE-2760 > URL: https://issues.jboss.org/browse/FORGE-2760 > Project: Forge > Issue Type: Bug > Components: Furnace CDI, Scaffold > Affects Versions: 3.7.2.Final > Environment: CentOS 7.3 > Forge 3.7.2 > Java OpenJDK Runtime Environment (build 1.8.0_141-b16) > Apache Maven 3.5.0 > Reporter: George Labuschagne > Attachments: forge.log, pom.xml, src.tar.gz > > > Attempting to run 'cdi-setup' or 'scaffold-setup --provider Faces' results in the following error message: > ***ERROR*** Could not install CDI. > Where last line of log file reads: > 19:56:22,799 SEVERE [org.jboss.forge.addon.shell.aesh.CommandAdapter] (AeshProcess: 1) Could not install CDI. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2760) cdi-setup and scaffold fail

by George Labuschagne (JIRA)

[ https://issues.jboss.org/browse/FORGE-2760?page=com.atlassian.jira.plugin... ] George Labuschagne edited comment on FORGE-2760 at 8/19/17 8:27 AM: -------------------------------------------------------------------- Hi George, indeed! :) I have the latest Forge extracted such that the bin is located at: ~/opt/forge/bin {code:bash} [georgel@devbox ~]$ which forge ~/opt/forge/bin/forge {code} The project is located at: {code:bash} [georgel@devbox edsnext]$ pwd /home/georgel/coding/edsnext [georgel@devbox edsnext]$ ls edsnext.iml pom.xml src target [georgel@devbox edsnext]$ {code} I uploaded now a copy of the src directory as well (it is tiny at the moment). When logging in to forge and then running either run 'cdi-setup' or 'scaffold-setup --provider Faces' I get the error as below: {code:bash} [georgel@devbox edsnext]$ forge Using Forge at /home/georgel/opt/forge _____ | ___|__ _ __ __ _ ___ | |_ / _ \| `__/ _` |/ _ \ \\ | _| (_) | | | (_| | __/ // |_| \___/|_| \__, |\___| |__/ JBoss Forge, version [ 3.7.2.Final ] - JBoss, by Red Hat, Inc. [ http://forge.jboss.org ] Hit '<TAB>' for a list of available commands and 'man [cmd]' for help on a specific command. To quit the shell, type 'exit'. [edsnext]$ cdi-setup ***ERROR*** Could not install CDI. [edsnext]$ scaffold-setup --provider Faces ***ERROR*** Could not install CDI. ***SUCCESS*** Scaffold was setup successfully. [edsnext]$ {code} was (Author: george.labuschagne): Hi George, indeed! :) I have the latest Forge extracted such that the bin is located at: ~/opt/forge/bin {code:bash} [georgel@devbox ~]$ which forge ~/opt/forge/bin/forge {code} The project is located at: {code:bash} [georgel@devbox edsnext]$ ls edsnext.iml pom.xml src target {code} I uploaded now a copy of the src directory as well (it is tiny at the moment). When logging in to forge and then running either run 'cdi-setup' or 'scaffold-setup --provider Faces' I get the error as below: {code:bash} [georgel@devbox edsnext]$ forge Using Forge at /home/georgel/opt/forge _____ | ___|__ _ __ __ _ ___ | |_ / _ \| `__/ _` |/ _ \ \\ | _| (_) | | | (_| | __/ // |_| \___/|_| \__, |\___| |__/ JBoss Forge, version [ 3.7.2.Final ] - JBoss, by Red Hat, Inc. [ http://forge.jboss.org ] Hit '<TAB>' for a list of available commands and 'man [cmd]' for help on a specific command. To quit the shell, type 'exit'. [edsnext]$ cdi-setup ***ERROR*** Could not install CDI. [edsnext]$ scaffold-setup --provider Faces ***ERROR*** Could not install CDI. ***SUCCESS*** Scaffold was setup successfully. [edsnext]$ {code} > cdi-setup and scaffold fail > --------------------------- > > Key: FORGE-2760 > URL: https://issues.jboss.org/browse/FORGE-2760 > Project: Forge > Issue Type: Bug > Components: Furnace CDI, Scaffold > Affects Versions: 3.7.2.Final > Environment: CentOS 7.3 > Forge 3.7.2 > Java OpenJDK Runtime Environment (build 1.8.0_141-b16) > Apache Maven 3.5.0 > Reporter: George Labuschagne > Attachments: forge.log, pom.xml, src.tar.gz > > > Attempting to run 'cdi-setup' or 'scaffold-setup --provider Faces' results in the following error message: > ***ERROR*** Could not install CDI. > Where last line of log file reads: > 19:56:22,799 SEVERE [org.jboss.forge.addon.shell.aesh.CommandAdapter] (AeshProcess: 1) Could not install CDI. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2760) cdi-setup and scaffold fail

by George Labuschagne (JIRA)

[ https://issues.jboss.org/browse/FORGE-2760?page=com.atlassian.jira.plugin... ] George Labuschagne edited comment on FORGE-2760 at 8/19/17 8:25 AM: -------------------------------------------------------------------- Hi George, indeed! :) I have the latest Forge extracted such that the bin is located at: ~/opt/forge/bin {code:bash} [georgel@devbox ~]$ which forge ~/opt/forge/bin/forge {code} The project is located at: {code:bash} [georgel@devbox edsnext]$ ls edsnext.iml pom.xml src target {code} I uploaded now a copy of the src directory as well (it is tiny at the moment). When logging in to forge and then running either run 'cdi-setup' or 'scaffold-setup --provider Faces' I get the error as below: {code:bash} [georgel@devbox edsnext]$ forge Using Forge at /home/georgel/opt/forge _____ | ___|__ _ __ __ _ ___ | |_ / _ \| `__/ _` |/ _ \ \\ | _| (_) | | | (_| | __/ // |_| \___/|_| \__, |\___| |__/ JBoss Forge, version [ 3.7.2.Final ] - JBoss, by Red Hat, Inc. [ http://forge.jboss.org ] Hit '<TAB>' for a list of available commands and 'man [cmd]' for help on a specific command. To quit the shell, type 'exit'. [edsnext]$ cdi-setup ***ERROR*** Could not install CDI. [edsnext]$ scaffold-setup --provider Faces ***ERROR*** Could not install CDI. ***SUCCESS*** Scaffold was setup successfully. [edsnext]$ {code} was (Author: george.labuschagne): Hi George, indeed! :) I have the latest Forge extracted such that the bin is located at: ~/opt/forge/bin {code:bash} [georgel@devbox ~]$ which forge ~/opt/forge/bin/forge {code} The project is located at: {code:bash} [georgel@devbox edsnext]$ ls edsnext.iml pom.xml src target {code} I uploaded now a copy of the src directory as well (it is tiny at the moment). > cdi-setup and scaffold fail > --------------------------- > > Key: FORGE-2760 > URL: https://issues.jboss.org/browse/FORGE-2760 > Project: Forge > Issue Type: Bug > Components: Furnace CDI, Scaffold > Affects Versions: 3.7.2.Final > Environment: CentOS 7.3 > Forge 3.7.2 > Java OpenJDK Runtime Environment (build 1.8.0_141-b16) > Apache Maven 3.5.0 > Reporter: George Labuschagne > Attachments: forge.log, pom.xml, src.tar.gz > > > Attempting to run 'cdi-setup' or 'scaffold-setup --provider Faces' results in the following error message: > ***ERROR*** Could not install CDI. > Where last line of log file reads: > 19:56:22,799 SEVERE [org.jboss.forge.addon.shell.aesh.CommandAdapter] (AeshProcess: 1) Could not install CDI. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2760) cdi-setup and scaffold fail

by George Labuschagne (JIRA)

[ https://issues.jboss.org/browse/FORGE-2760?page=com.atlassian.jira.plugin... ] George Labuschagne updated FORGE-2760: -------------------------------------- Attachment: src.tar.gz > cdi-setup and scaffold fail > --------------------------- > > Key: FORGE-2760 > URL: https://issues.jboss.org/browse/FORGE-2760 > Project: Forge > Issue Type: Bug > Components: Furnace CDI, Scaffold > Affects Versions: 3.7.2.Final > Environment: CentOS 7.3 > Forge 3.7.2 > Java OpenJDK Runtime Environment (build 1.8.0_141-b16) > Apache Maven 3.5.0 > Reporter: George Labuschagne > Attachments: forge.log, pom.xml, src.tar.gz > > > Attempting to run 'cdi-setup' or 'scaffold-setup --provider Faces' results in the following error message: > ***ERROR*** Could not install CDI. > Where last line of log file reads: > 19:56:22,799 SEVERE [org.jboss.forge.addon.shell.aesh.CommandAdapter] (AeshProcess: 1) Could not install CDI. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues August 2017