[JBoss JIRA] (FORGE-866) Forge cannot handle 'p2' repository layout in settings.xml
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-866?page=com.atlassian.jira.plugin.... ]
George Gastaldi closed FORGE-866.
---------------------------------
Fix Version/s: 2.0.0.Alpha4
Resolution: Done
Fixed
> Forge cannot handle 'p2' repository layout in settings.xml
> ----------------------------------------------------------
>
> Key: FORGE-866
> URL: https://issues.jboss.org/browse/FORGE-866
> Project: Forge
> Issue Type: Bug
> Affects Versions: 1.2.2.Final
> Reporter: Pavol Srna
> Assignee: George Gastaldi
> Priority: Critical
> Fix For: 1.2.4.Final, 2.0.0.Alpha4
>
>
> {code}
> java.lang.NullPointerException
> at org.apache.maven.RepositoryUtils.getLayout(RepositoryUtils.java:214)
> at org.apache.maven.RepositoryUtils.toRepo(RepositoryUtils.java:200)
> at org.apache.maven.RepositoryUtils.toRepos(RepositoryUtils.java:190)
> at org.apache.maven.project.DefaultProjectBuilder$InternalConfig.<init>(DefaultProjectBuilder.java:662)
> at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:102)
> at org.jboss.forge.maven.facets.MavenCoreFacetImpl.getPartialProjectBuildingResult(MavenCoreFacetImpl.java:86)
> at org.jboss.forge.maven.facets.MavenCoreFacetImpl.resolveProperties(MavenCoreFacetImpl.java:304)
> at org.jboss.forge.maven.facets.MavenDependencyFacet.resolveProperties(MavenDependencyFacet.java:393)
> at org.jboss.forge.maven.facets.MavenDependencyFacet.hasEffectiveDependency(MavenDependencyFacet.java:171)
> at org.jboss.forge.spec.javaee.BaseJavaEEFacet.isInstalled(BaseJavaEEFacet.java:64)
> at org.jboss.forge.project.BaseProject.registerFacet(BaseProject.java:153)
> at org.jboss.forge.project.services.ProjectFactory.registerSingleFacet(ProjectFactory.java:208)
> at org.jboss.forge.project.services.ProjectFactory.registerSingleFacet(ProjectFactory.java:186)
> at org.jboss.forge.project.services.ProjectFactory.registerFacets(ProjectFactory.java:178)
> at org.jboss.forge.project.services.ProjectFactory.createProject(ProjectFactory.java:146)
> at org.jboss.forge.shell.plugins.builtin.NewProjectPlugin.create(NewProjectPlugin.java:205)
> 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.forge.shell.command.Execution.perform(Execution.java:134)
> at org.jboss.forge.shell.command.fshparser.FSHRuntime.run(FSHRuntime.java:109)
> at org.jboss.forge.shell.command.fshparser.FSHRuntime.run(FSHRuntime.java:47)
> at org.jboss.forge.shell.ShellImpl$ExecutorThread.run(ShellImpl.java:789)
> at org.jboss.forge.shell.ShellImpl.execute(ShellImpl.java:812)
> at org.jboss.forge.shell.ShellImpl.doShell(ShellImpl.java:602)
> 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.bean.proxy.AbstractBeanInstance.invoke(AbstractBeanInstance.java:48)
> at org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:125)
> at org.jboss.forge.shell.ShellImpl$Proxy$_$$_WeldClientProxy.doShell(ShellImpl$Proxy$_$$_WeldClientProxy.java)
> 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:188)
> at org.jboss.weld.introspector.ForwardingWeldMethod.invokeOnInstance(ForwardingWeldMethod.java:59)
> at org.jboss.weld.injection.MethodInjectionPoint.invokeOnInstanceWithSpecialValue(MethodInjectionPoint.java:198)
> at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:282)
> at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:265)
> at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:234)
> at org.jboss.weld.manager.BeanManagerImpl.notifyObservers(BeanManagerImpl.java:635)
> at org.jboss.weld.manager.BeanManagerImpl.fireEvent(BeanManagerImpl.java:622)
> at org.jboss.weld.manager.BeanManagerImpl.fireEvent(BeanManagerImpl.java:616)
> at org.jboss.forge.shell.Bootstrap$1.run(Bootstrap.java:172)
> at java.lang.Thread.run(Thread.java:662)
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 9 months
[JBoss JIRA] (FORGE-866) Forge cannot handle 'p2' repository layout in settings.xml
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-866?page=com.atlassian.jira.plugin.... ]
George Gastaldi reassigned FORGE-866:
-------------------------------------
Assignee: George Gastaldi
> Forge cannot handle 'p2' repository layout in settings.xml
> ----------------------------------------------------------
>
> Key: FORGE-866
> URL: https://issues.jboss.org/browse/FORGE-866
> Project: Forge
> Issue Type: Bug
> Affects Versions: 1.2.2.Final
> Reporter: Pavol Srna
> Assignee: George Gastaldi
> Priority: Critical
> Fix For: 1.2.4.Final
>
>
> {code}
> java.lang.NullPointerException
> at org.apache.maven.RepositoryUtils.getLayout(RepositoryUtils.java:214)
> at org.apache.maven.RepositoryUtils.toRepo(RepositoryUtils.java:200)
> at org.apache.maven.RepositoryUtils.toRepos(RepositoryUtils.java:190)
> at org.apache.maven.project.DefaultProjectBuilder$InternalConfig.<init>(DefaultProjectBuilder.java:662)
> at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:102)
> at org.jboss.forge.maven.facets.MavenCoreFacetImpl.getPartialProjectBuildingResult(MavenCoreFacetImpl.java:86)
> at org.jboss.forge.maven.facets.MavenCoreFacetImpl.resolveProperties(MavenCoreFacetImpl.java:304)
> at org.jboss.forge.maven.facets.MavenDependencyFacet.resolveProperties(MavenDependencyFacet.java:393)
> at org.jboss.forge.maven.facets.MavenDependencyFacet.hasEffectiveDependency(MavenDependencyFacet.java:171)
> at org.jboss.forge.spec.javaee.BaseJavaEEFacet.isInstalled(BaseJavaEEFacet.java:64)
> at org.jboss.forge.project.BaseProject.registerFacet(BaseProject.java:153)
> at org.jboss.forge.project.services.ProjectFactory.registerSingleFacet(ProjectFactory.java:208)
> at org.jboss.forge.project.services.ProjectFactory.registerSingleFacet(ProjectFactory.java:186)
> at org.jboss.forge.project.services.ProjectFactory.registerFacets(ProjectFactory.java:178)
> at org.jboss.forge.project.services.ProjectFactory.createProject(ProjectFactory.java:146)
> at org.jboss.forge.shell.plugins.builtin.NewProjectPlugin.create(NewProjectPlugin.java:205)
> 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.forge.shell.command.Execution.perform(Execution.java:134)
> at org.jboss.forge.shell.command.fshparser.FSHRuntime.run(FSHRuntime.java:109)
> at org.jboss.forge.shell.command.fshparser.FSHRuntime.run(FSHRuntime.java:47)
> at org.jboss.forge.shell.ShellImpl$ExecutorThread.run(ShellImpl.java:789)
> at org.jboss.forge.shell.ShellImpl.execute(ShellImpl.java:812)
> at org.jboss.forge.shell.ShellImpl.doShell(ShellImpl.java:602)
> 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.bean.proxy.AbstractBeanInstance.invoke(AbstractBeanInstance.java:48)
> at org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:125)
> at org.jboss.forge.shell.ShellImpl$Proxy$_$$_WeldClientProxy.doShell(ShellImpl$Proxy$_$$_WeldClientProxy.java)
> 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:188)
> at org.jboss.weld.introspector.ForwardingWeldMethod.invokeOnInstance(ForwardingWeldMethod.java:59)
> at org.jboss.weld.injection.MethodInjectionPoint.invokeOnInstanceWithSpecialValue(MethodInjectionPoint.java:198)
> at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:282)
> at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:265)
> at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:234)
> at org.jboss.weld.manager.BeanManagerImpl.notifyObservers(BeanManagerImpl.java:635)
> at org.jboss.weld.manager.BeanManagerImpl.fireEvent(BeanManagerImpl.java:622)
> at org.jboss.weld.manager.BeanManagerImpl.fireEvent(BeanManagerImpl.java:616)
> at org.jboss.forge.shell.Bootstrap$1.run(Bootstrap.java:172)
> at java.lang.Thread.run(Thread.java:662)
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 9 months
[JBoss JIRA] (FORGE-866) Forge cannot handle 'p2' repository layout in settings.xml
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-866?page=com.atlassian.jira.plugin.... ]
Work on FORGE-866 started by George Gastaldi.
> Forge cannot handle 'p2' repository layout in settings.xml
> ----------------------------------------------------------
>
> Key: FORGE-866
> URL: https://issues.jboss.org/browse/FORGE-866
> Project: Forge
> Issue Type: Bug
> Affects Versions: 1.2.2.Final
> Reporter: Pavol Srna
> Assignee: George Gastaldi
> Priority: Critical
> Fix For: 1.2.4.Final
>
>
> {code}
> java.lang.NullPointerException
> at org.apache.maven.RepositoryUtils.getLayout(RepositoryUtils.java:214)
> at org.apache.maven.RepositoryUtils.toRepo(RepositoryUtils.java:200)
> at org.apache.maven.RepositoryUtils.toRepos(RepositoryUtils.java:190)
> at org.apache.maven.project.DefaultProjectBuilder$InternalConfig.<init>(DefaultProjectBuilder.java:662)
> at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:102)
> at org.jboss.forge.maven.facets.MavenCoreFacetImpl.getPartialProjectBuildingResult(MavenCoreFacetImpl.java:86)
> at org.jboss.forge.maven.facets.MavenCoreFacetImpl.resolveProperties(MavenCoreFacetImpl.java:304)
> at org.jboss.forge.maven.facets.MavenDependencyFacet.resolveProperties(MavenDependencyFacet.java:393)
> at org.jboss.forge.maven.facets.MavenDependencyFacet.hasEffectiveDependency(MavenDependencyFacet.java:171)
> at org.jboss.forge.spec.javaee.BaseJavaEEFacet.isInstalled(BaseJavaEEFacet.java:64)
> at org.jboss.forge.project.BaseProject.registerFacet(BaseProject.java:153)
> at org.jboss.forge.project.services.ProjectFactory.registerSingleFacet(ProjectFactory.java:208)
> at org.jboss.forge.project.services.ProjectFactory.registerSingleFacet(ProjectFactory.java:186)
> at org.jboss.forge.project.services.ProjectFactory.registerFacets(ProjectFactory.java:178)
> at org.jboss.forge.project.services.ProjectFactory.createProject(ProjectFactory.java:146)
> at org.jboss.forge.shell.plugins.builtin.NewProjectPlugin.create(NewProjectPlugin.java:205)
> 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.forge.shell.command.Execution.perform(Execution.java:134)
> at org.jboss.forge.shell.command.fshparser.FSHRuntime.run(FSHRuntime.java:109)
> at org.jboss.forge.shell.command.fshparser.FSHRuntime.run(FSHRuntime.java:47)
> at org.jboss.forge.shell.ShellImpl$ExecutorThread.run(ShellImpl.java:789)
> at org.jboss.forge.shell.ShellImpl.execute(ShellImpl.java:812)
> at org.jboss.forge.shell.ShellImpl.doShell(ShellImpl.java:602)
> 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.bean.proxy.AbstractBeanInstance.invoke(AbstractBeanInstance.java:48)
> at org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:125)
> at org.jboss.forge.shell.ShellImpl$Proxy$_$$_WeldClientProxy.doShell(ShellImpl$Proxy$_$$_WeldClientProxy.java)
> 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:188)
> at org.jboss.weld.introspector.ForwardingWeldMethod.invokeOnInstance(ForwardingWeldMethod.java:59)
> at org.jboss.weld.injection.MethodInjectionPoint.invokeOnInstanceWithSpecialValue(MethodInjectionPoint.java:198)
> at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:282)
> at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:265)
> at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:234)
> at org.jboss.weld.manager.BeanManagerImpl.notifyObservers(BeanManagerImpl.java:635)
> at org.jboss.weld.manager.BeanManagerImpl.fireEvent(BeanManagerImpl.java:622)
> at org.jboss.weld.manager.BeanManagerImpl.fireEvent(BeanManagerImpl.java:616)
> at org.jboss.forge.shell.Bootstrap$1.run(Bootstrap.java:172)
> at java.lang.Thread.run(Thread.java:662)
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 9 months
[JBoss JIRA] (FORGE-875) the `scaffold setup --scaffoldType faces; ` command. failed to create beans.xml
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-875?page=com.atlassian.jira.plugin.... ]
George Gastaldi reassigned FORGE-875:
-------------------------------------
Assignee: (was: George Gastaldi)
> the `scaffold setup --scaffoldType faces;` command. failed to create beans.xml
> ------------------------------------------------------------------------------
>
> Key: FORGE-875
> URL: https://issues.jboss.org/browse/FORGE-875
> Project: Forge
> Issue Type: Bug
> Affects Versions: 1.2.2.Final
> Environment: Mac: OS X 10.8.3, 2.66 GHz Intel Core i7, 4GG 1067 MHz DDR3
> Running Forge Console in JBoss Developers Studio version 6.1.0.GA, Deploying to JBoss EAP 6.0.1
> Reporter: Randy Thomas
> Priority: Blocker
> Labels: forge
>
> I generated a sample project using the generate.fsh script. I deployed the war file to EAP 6 and everything seemed to be working fine.
> The welcome page comes up for the app with no problems. However, an error is generated upon the attempt to add data to the database.
> I was able to resolve the problem by adding the following lines to the script:
> @/* Add beans.xml for CDI */;
> touch src/main/webapp/WEB-INF/beans.xml
> Lincoln indicated that this should have already been done by the
> `scaffold setup --scaffoldType faces;` command.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 9 months
[JBoss JIRA] (FORGE-875) the `scaffold setup --scaffoldType faces; ` command. failed to create beans.xml
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-875?page=com.atlassian.jira.plugin.... ]
George Gastaldi reassigned FORGE-875:
-------------------------------------
Assignee: George Gastaldi
> the `scaffold setup --scaffoldType faces;` command. failed to create beans.xml
> ------------------------------------------------------------------------------
>
> Key: FORGE-875
> URL: https://issues.jboss.org/browse/FORGE-875
> Project: Forge
> Issue Type: Bug
> Affects Versions: 1.2.2.Final
> Environment: Mac: OS X 10.8.3, 2.66 GHz Intel Core i7, 4GG 1067 MHz DDR3
> Running Forge Console in JBoss Developers Studio version 6.1.0.GA, Deploying to JBoss EAP 6.0.1
> Reporter: Randy Thomas
> Assignee: George Gastaldi
> Priority: Blocker
> Labels: forge
>
> I generated a sample project using the generate.fsh script. I deployed the war file to EAP 6 and everything seemed to be working fine.
> The welcome page comes up for the app with no problems. However, an error is generated upon the attempt to add data to the database.
> I was able to resolve the problem by adding the following lines to the script:
> @/* Add beans.xml for CDI */;
> touch src/main/webapp/WEB-INF/beans.xml
> Lincoln indicated that this should have already been done by the
> `scaffold setup --scaffoldType faces;` command.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 9 months
[JBoss JIRA] (FORGE-875) the `scaffold setup --scaffoldType faces; ` command. failed to create beans.xml
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-875?page=com.atlassian.jira.plugin.... ]
George Gastaldi updated FORGE-875:
----------------------------------
Issue Type: Bug (was: Story)
Workflow: GIT Pull Request workflow (was: jira)
Workaround Description: Added "beans setup" to generate.fsh file
> the `scaffold setup --scaffoldType faces;` command. failed to create beans.xml
> ------------------------------------------------------------------------------
>
> Key: FORGE-875
> URL: https://issues.jboss.org/browse/FORGE-875
> Project: Forge
> Issue Type: Bug
> Affects Versions: 1.2.2.Final
> Environment: Mac: OS X 10.8.3, 2.66 GHz Intel Core i7, 4GG 1067 MHz DDR3
> Running Forge Console in JBoss Developers Studio version 6.1.0.GA, Deploying to JBoss EAP 6.0.1
> Reporter: Randy Thomas
> Assignee: George Gastaldi
> Priority: Blocker
> Labels: forge
>
> I generated a sample project using the generate.fsh script. I deployed the war file to EAP 6 and everything seemed to be working fine.
> The welcome page comes up for the app with no problems. However, an error is generated upon the attempt to add data to the database.
> I was able to resolve the problem by adding the following lines to the script:
> @/* Add beans.xml for CDI */;
> touch src/main/webapp/WEB-INF/beans.xml
> Lincoln indicated that this should have already been done by the
> `scaffold setup --scaffoldType faces;` command.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 9 months
[JBoss JIRA] (FORGE-875) the `scaffold setup --scaffoldType faces; ` command. failed to create beans.xml
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-875?page=com.atlassian.jira.plugin.... ]
George Gastaldi reopened FORGE-875:
-----------------------------------
Reopening this issue, as it seems to be a bug in Forge
> the `scaffold setup --scaffoldType faces;` command. failed to create beans.xml
> ------------------------------------------------------------------------------
>
> Key: FORGE-875
> URL: https://issues.jboss.org/browse/FORGE-875
> Project: Forge
> Issue Type: Story
> Affects Versions: 1.2.2.Final
> Environment: Mac: OS X 10.8.3, 2.66 GHz Intel Core i7, 4GG 1067 MHz DDR3
> Running Forge Console in JBoss Developers Studio version 6.1.0.GA, Deploying to JBoss EAP 6.0.1
> Reporter: Randy Thomas
> Assignee: George Gastaldi
> Priority: Blocker
> Labels: forge
>
> I generated a sample project using the generate.fsh script. I deployed the war file to EAP 6 and everything seemed to be working fine.
> The welcome page comes up for the app with no problems. However, an error is generated upon the attempt to add data to the database.
> I was able to resolve the problem by adding the following lines to the script:
> @/* Add beans.xml for CDI */;
> touch src/main/webapp/WEB-INF/beans.xml
> Lincoln indicated that this should have already been done by the
> `scaffold setup --scaffoldType faces;` command.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 9 months
[JBoss JIRA] (FORGE-875) the `scaffold setup --scaffoldType faces; ` command. failed to create beans.xml
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-875?page=com.atlassian.jira.plugin.... ]
George Gastaldi closed FORGE-875.
---------------------------------
Assignee: George Gastaldi
Resolution: Done
Fixed in JDF Quickstarts (added 'beans setup' to script)
> the `scaffold setup --scaffoldType faces;` command. failed to create beans.xml
> ------------------------------------------------------------------------------
>
> Key: FORGE-875
> URL: https://issues.jboss.org/browse/FORGE-875
> Project: Forge
> Issue Type: Story
> Affects Versions: 1.2.2.Final
> Environment: Mac: OS X 10.8.3, 2.66 GHz Intel Core i7, 4GG 1067 MHz DDR3
> Running Forge Console in JBoss Developers Studio version 6.1.0.GA, Deploying to JBoss EAP 6.0.1
> Reporter: Randy Thomas
> Assignee: George Gastaldi
> Priority: Blocker
> Labels: forge
>
> I generated a sample project using the generate.fsh script. I deployed the war file to EAP 6 and everything seemed to be working fine.
> The welcome page comes up for the app with no problems. However, an error is generated upon the attempt to add data to the database.
> I was able to resolve the problem by adding the following lines to the script:
> @/* Add beans.xml for CDI */;
> touch src/main/webapp/WEB-INF/beans.xml
> Lincoln indicated that this should have already been done by the
> `scaffold setup --scaffoldType faces;` command.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 9 months
[JBoss JIRA] (FORGE-875) the `scaffold setup --scaffoldType faces; ` command. failed to create beans.xml
by Rafael Benevides (JIRA)
[ https://issues.jboss.org/browse/FORGE-875?page=com.atlassian.jira.plugin.... ]
Rafael Benevides commented on FORGE-875:
----------------------------------------
PR merged
> the `scaffold setup --scaffoldType faces;` command. failed to create beans.xml
> ------------------------------------------------------------------------------
>
> Key: FORGE-875
> URL: https://issues.jboss.org/browse/FORGE-875
> Project: Forge
> Issue Type: Story
> Affects Versions: 1.2.2.Final
> Environment: Mac: OS X 10.8.3, 2.66 GHz Intel Core i7, 4GG 1067 MHz DDR3
> Running Forge Console in JBoss Developers Studio version 6.1.0.GA, Deploying to JBoss EAP 6.0.1
> Reporter: Randy Thomas
> Priority: Blocker
> Labels: forge
>
> I generated a sample project using the generate.fsh script. I deployed the war file to EAP 6 and everything seemed to be working fine.
> The welcome page comes up for the app with no problems. However, an error is generated upon the attempt to add data to the database.
> I was able to resolve the problem by adding the following lines to the script:
> @/* Add beans.xml for CDI */;
> touch src/main/webapp/WEB-INF/beans.xml
> Lincoln indicated that this should have already been done by the
> `scaffold setup --scaffoldType faces;` command.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 9 months