November 2013 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-1339) Mandatory attributes in CLI

by Antonio Goncalves (JIRA)

Antonio Goncalves created FORGE-1339: ---------------------------------------- Summary: Mandatory attributes in CLI Key: FORGE-1339 URL: https://issues.jboss.org/browse/FORGE-1339 Project: Forge Issue Type: Sub-task Reporter: Antonio Goncalves For the command {{jpa-new-entity}}, when you hit TAB, both {{named}} and {{idStrategy}} are in green (while {{targetPackage}} is in black). I might be wrong, but green shows to me that both {{named}} and {{idStrategy}} are mandatory. Which is not the case : {{named}} IS mandatory but {{idStrategy}} is not -- 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

1
0
0 / 0

[JBoss JIRA] (FORGE-1338) Make JDK 7 the minimum runtime requirement

by George Gastaldi (JIRA)

George Gastaldi created FORGE-1338: -------------------------------------- Summary: Make JDK 7 the minimum runtime requirement Key: FORGE-1338 URL: https://issues.jboss.org/browse/FORGE-1338 Project: Forge Issue Type: Component Upgrade Components: Forge Build Affects Versions: 2.0.0.Beta3 Reporter: George Gastaldi Fix For: 2.x Future This issue should be used to track changes in the pom.xml to support JDK 7 as the minimum requirement. It should be solved when the the JBT and JBDS Team uses JDK7 as their minimum runtime. -- 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

1
0
0 / 0

[JBoss JIRA] (FORGE-1334) Addon installation "forge -i core" takes forever and repeatedly downloads metadata files

by George Gastaldi (JIRA)

11 years

1
0
0 / 0

[JBoss JIRA] (FORGE-1321) Failure to install addons when using secure repositories

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1321?page=com.atlassian.jira.plugin... ] George Gastaldi commented on FORGE-1321: ---------------------------------------- After this change, if the repository does not require any authentication, but a <server> entry is specified in the settings.xml (eg: jboss-public-repository), it will fail with an unauthorized exception. Please remove any <server> from the settings.xml that doesn't require authentication. > Failure to install addons when using secure repositories > -------------------------------------------------------- > > Key: FORGE-1321 > URL: https://issues.jboss.org/browse/FORGE-1321 > Project: Forge > Issue Type: Bug > Components: Build Tools - Maven > Affects Versions: 2.0.0.Beta3 > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > Fix For: 2.0.0.Beta4 > > > After FORGE-1307, Forge seems to be able to access secure repositories, but fails to install the addon: > {noformat} > forge-distribution-2.0.0.Beta2$ ./bin/forge --install shell > Using Forge at forge-distribution-2.0.0.Beta2 > Warning: JAVA_HOME environment variable is not set. > Downloading: http://xxxxxx/artifactory/repo/org/jboss/forge/addon/shell/maven-metadata... > Downloading: http://xxxxxx/artifactory/repo/org/jboss/forge/addon/shell/maven-metadata... > java.lang.IllegalArgumentException: No Artifact version found for org.jboss.forge.addon:shell > at org.jboss.forge.bootstrap.Bootstrap.install(Bootstrap.java:199) > at org.jboss.forge.bootstrap.Bootstrap.<init>(Bootstrap.java:144) > at org.jboss.forge.bootstrap.Bootstrap.main(Bootstrap.java:88) > > Forge version [2.0.0.Beta1] > {noformat} > The Artifactory repository used this feature: http://www.jfrog.com/confluence/display/RTF/Centrally+Secure+Passwords > Additional info: > {noformat} > <dbeer> think I have found part of issue I have removed security constraint briefly from our server and is now downloading a load of forge addon snapshots, will investigate the security further tomorrow > {noformat} -- 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

1
0
0 / 0

[JBoss JIRA] (FORGE-1335) Creating new project, JVM IBM 1.7

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1335?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-1335: ----------------------------------- Fix Version/s: 2.x Future > Creating new project, JVM IBM 1.7 > --------------------------------- > > Key: FORGE-1335 > URL: https://issues.jboss.org/browse/FORGE-1335 > Project: Forge > Issue Type: Bug > Affects Versions: 1.4.3.Final > Environment: JVM: IBM J9 VM (build 2.6, JRE 1.7.0 Linux amd64-64 Compressed References 20130205_137358 (JIT enabled, AOT enabled) > OS: Ubuntu 13.04 64 bit > Reporter: Martin Basovnik > Fix For: 2.x Future > > > Problem with creating of new project on JVM ibm17. > LOG: > {noformat} > [no project] test-forge $ new-project --named IBM > ? Use [/home/mbasovni/development/test-forge/IBM] as project directory? [Y/n] > Wrote /home/mbasovni/development/test-forge/IBM > Wrote /home/mbasovni/development/test-forge/IBM/pom.xml > Wrote /home/mbasovni/development/test-forge/IBM/src/main/java > Wrote /home/mbasovni/development/test-forge/IBM/src/test/java > Wrote /home/mbasovni/development/test-forge/IBM/src/main/resources > Wrote /home/mbasovni/development/test-forge/IBM/src/test/resources > ***ERROR*** Exception encountered: null (type "set VERBOSE true" to enable stack traces) > {noformat} > When I set: {{set VERBOSE true}} > LOG: > {noformat} > [no project] test-forge $ set VERBOSE true > [no project] test-forge $ new-project --named IBM2 > ? Use [/home/mbasovni/development/test-forge/IBM2] as project directory? [Y/n] > Wrote /home/mbasovni/development/test-forge/IBM2 > Wrote /home/mbasovni/development/test-forge/IBM2/pom.xml > Wrote /home/mbasovni/development/test-forge/IBM2/src/main/java > Wrote /home/mbasovni/development/test-forge/IBM2/src/test/java > Wrote /home/mbasovni/development/test-forge/IBM2/src/main/resources > Wrote /home/mbasovni/development/test-forge/IBM2/src/test/resources > ***ERROR*** Exception encountered: (type "set VERBOSE false" to disable stack traces) > java.util.NoSuchElementException > at org.sonatype.guice.bean.locators.LocatedBeans$Itr.next(LocatedBeans.java:184) > at org.sonatype.guice.bean.locators.LocatedBeans$Itr.next(LocatedBeans.java:124) > at org.sonatype.guice.plexus.locators.DefaultPlexusBeans$Itr.next(DefaultPlexusBeans.java:64) > at org.sonatype.guice.plexus.locators.DefaultPlexusBeans$Itr.next(DefaultPlexusBeans.java:52) > at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:243) > at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:235) > at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:229) > at org.jboss.forge.maven.facets.MavenContainer.lookup(MavenContainer.java:214) > at org.jboss.forge.maven.facets.MavenContainer.getBuildingRequest(MavenContainer.java:86) > at org.jboss.forge.maven.facets.MavenContainer.getRequest(MavenContainer.java:68) > at org.jboss.forge.maven.facets.MavenContainer$Proxy$_$$_WeldClientProxy.getRequest(MavenContainer$Proxy$_$$_WeldClientProxy.java) > at org.jboss.forge.maven.facets.MavenCoreFacetImpl.getPartialProjectBuildingResult(MavenCoreFacetImpl.java:90) > at org.jboss.forge.maven.facets.MavenCoreFacetImpl.resolveProperties(MavenCoreFacetImpl.java:338) > at org.jboss.forge.maven.facets.MavenDependencyFacet.resolveProperties(MavenDependencyFacet.java:394) > at org.jboss.forge.maven.facets.MavenDependencyFacet.hasEffectiveDependency(MavenDependencyFacet.java:172) > at org.jboss.forge.shell.project.DependencyInstallerImpl.isInstalled(DependencyInstallerImpl.java:170) > at org.jboss.forge.git.GitAPIFacet.isInstalled(GitAPIFacet.java:42) > 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:88) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55) > at java.lang.reflect.Method.invoke(Method.java:613) > at org.jboss.forge.shell.command.Execution.perform(Execution.java:160) > 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:796) > at org.jboss.forge.shell.ShellImpl.execute(ShellImpl.java:819) > at org.jboss.forge.shell.ShellImpl.doShell(ShellImpl.java:609) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:88) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55) > at java.lang.reflect.Method.invoke(Method.java:613) > 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:88) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55) > at java.lang.reflect.Method.invoke(Method.java:613) > 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:186) > at java.lang.Thread.run(Thread.java:780) > {noformat} -- 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

1
0
0 / 0

[JBoss JIRA] (FORGE-989) Support rollback of installed addons

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-989?page=com.atlassian.jira.plugin.... ] George Gastaldi reassigned FORGE-989: ------------------------------------- Assignee: (was: George Gastaldi) > Support rollback of installed addons > ------------------------------------- > > Key: FORGE-989 > URL: https://issues.jboss.org/browse/FORGE-989 > Project: Forge > Issue Type: Feature Request > Components: Addon Manager > Affects Versions: 2.0.0.Alpha6 > Reporter: George Gastaldi > Priority: Critical > Fix For: 2.x Future > > > After an installation is performed, it should be possible to revert the repository to a previous state. > It should be possible to log every install/remove request for each addon and group them by transaction savepoints. > Eg: > - Install Addon A which depends on B,C,D ( C and D already installed) > Log: > Transaction #1 > Addon A: INSTALLED > Addon B: INSTALLED > - Install Addon E which depends on A > Log: > Transaction #2 > Addon E: INSTALLED > Rollback of each transaction should have the following behavior: > - Rollback of Transaction #2 should remove Addon E. > - Rollback of Transaction #1 should remove A, B. -- 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

1
0
0 / 0

[JBoss JIRA] (FORGE-957) Create "Stacks" addon, that allows providing stack implementations to supply default values in dialogs

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-957?page=com.atlassian.jira.plugin.... ] George Gastaldi reassigned FORGE-957: ------------------------------------- Assignee: (was: George Gastaldi) > Create "Stacks" addon, that allows providing stack implementations to supply default values in dialogs > ------------------------------------------------------------------------------------------------------ > > Key: FORGE-957 > URL: https://issues.jboss.org/browse/FORGE-957 > Project: Forge > Issue Type: Feature Request > Components: Blessed Plugins > Affects Versions: 2.0.0.Alpha5 > Reporter: Lincoln Baxter III > Priority: Critical > Fix For: 2.0.0.Final > > > This will allow things like, detecting that the user is on Wildfly AS, and subsequently selecting appropriate versions of specifications, libraries, and other setup configurations. -- 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

1
0
0 / 0

[JBoss JIRA] (FORGEPLUGINS-153) Arquillian plugin - setup, missing hint of container name

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGEPLUGINS-153?page=com.atlassian.jira.... ] George Gastaldi moved FORGE-1336 to FORGEPLUGINS-153: ----------------------------------------------------- Project: Forge Plugins (was: Forge) Key: FORGEPLUGINS-153 (was: FORGE-1336) Affects Version/s: (was: 1.4.3.Final) Component/s: Arquillian Plugin (was: Builtin Plugins) > Arquillian plugin - setup, missing hint of container name > --------------------------------------------------------- > > Key: FORGEPLUGINS-153 > URL: https://issues.jboss.org/browse/FORGEPLUGINS-153 > Project: Forge Plugins > Issue Type: Bug > Components: Arquillian Plugin > Environment: JVM: Oracle 1.7.0_25 > OS: Ubuntu 13.04 64bit > Arquillian plugin: 1.0.6.Final > <plugin api-version="1.0.6.Final" name="org.arquillian.forge.arquillian-plugin" slot="1.0.0-SNAPSHOT-270daa6b-2354-40b1-8422-cd487588a50e"/> > Reporter: Martin Basovnik > > Setting up of arquillian plugin is failing. There is no option of supported containers after key {{TAB}} is pressed for {{--containerName}}, but according to instructions [here|http://forge.jboss.org/docs/important_plugins/arquillian-testing.html], there should be. File [containers.json|https://github.com/forge/plugin-arquillian/blob/1.0.6.Fin...] exists but obviously is not used properly. When bad container name is typed, following exception is thrown: > {noformat} > ***ERROR*** Exception encountered: (type "set VERBOSE false" to disable stack traces) > java.lang.RuntimeException: Container not recognized > at org.jboss.forge.arquillian.ArquillianPlugin.installContainer(ArquillianPlugin.java:156) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.forge.shell.command.Execution.perform(Execution.java:160) > 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:796) > at org.jboss.forge.shell.ShellImpl.execute(ShellImpl.java:819) > at org.jboss.forge.shell.ShellImpl.doShell(ShellImpl.java:609) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > 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:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > 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:186) > at java.lang.Thread.run(Thread.java:724) > {noformat} -- 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

1
0
0 / 0

[JBoss JIRA] (FORGEPLUGINS-154) Switchyad plugin - bean-service creation

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGEPLUGINS-154?page=com.atlassian.jira.... ] George Gastaldi moved FORGE-1337 to FORGEPLUGINS-154: ----------------------------------------------------- Project: Forge Plugins (was: Forge) Key: FORGEPLUGINS-154 (was: FORGE-1337) Affects Version/s: (was: 1.4.3.Final) Component/s: Switchyard Plugin (was: Builtin Plugins) > Switchyad plugin - bean-service creation > ---------------------------------------- > > Key: FORGEPLUGINS-154 > URL: https://issues.jboss.org/browse/FORGEPLUGINS-154 > Project: Forge Plugins > Issue Type: Bug > Components: Switchyard Plugin > Environment: Switchyard plugin: 1.2.2.Final > Java: Oracle 1.7.0_25 > Reporter: Martin Basovnik > Labels: switchyard > > {noformat} > $ bean-service create --serviceName Test > {noformat} > Classes {{Test.java}} and {{TestBean.java}} are properly created, but configuration file {{switchyard.xml}} is not updated. -- 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

1
0
0 / 0

[JBoss JIRA] (FORGE-1337) Switchyad plugin - bean-service creation

by Martin Basovnik (JIRA)

[ https://issues.jboss.org/browse/FORGE-1337?page=com.atlassian.jira.plugin... ] Martin Basovnik updated FORGE-1337: ----------------------------------- Environment: Switchyard plugin: 1.2.2.Final Java: Oracle 1.7.0_25 > Switchyad plugin - bean-service creation > ---------------------------------------- > > Key: FORGE-1337 > URL: https://issues.jboss.org/browse/FORGE-1337 > Project: Forge > Issue Type: Bug > Components: Builtin Plugins > Affects Versions: 1.4.3.Final > Environment: Switchyard plugin: 1.2.2.Final > Java: Oracle 1.7.0_25 > Reporter: Martin Basovnik > Labels: switchyard > > {noformat} > $ bean-service create --serviceName Test > {noformat} > Classes {{Test.java}} and {{TestBean.java}} are properly created, but configuration file {{switchyard.xml}} is not updated. -- 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

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues November 2013