March 2012 - forge-issues - Jboss List Archives

by Pete Muir (JIRA)

Pete Muir created FORGE-509: ------------------------------- Summary: Add eap plugin Key: FORGE-509 URL: https://issues.jboss.org/browse/FORGE-509 Project: Forge Issue Type: Feature Request Reporter: Pete Muir Essentially a clone of the as7 plugin with the --version option described in FORGE-508 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-507) Tidy up Forge's list-commands output

by Burr Sutter (JIRA)

Burr Sutter created FORGE-507: --------------------------------- Summary: Tidy up Forge's list-commands output Key: FORGE-507 URL: https://issues.jboss.org/browse/FORGE-507 Project: Forge Issue Type: Enhancement Reporter: Burr Sutter Attachments: Screen Shot 2012-03-14 at 8.55.57 AM.png The use of "list-commands" produces a less than ideal formatting - see screenshot from JBDS5 Beta1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
1
0 / 0

[JBoss JIRA] (FORGE-499) ISE thrown when forge git-plugin not used in a project

by Pete Muir (JIRA)

Pete Muir created FORGE-499: ------------------------------- Summary: ISE thrown when forge git-plugin not used in a project Key: FORGE-499 URL: https://issues.jboss.org/browse/FORGE-499 Project: Forge Issue Type: Bug Affects Versions: 1.0.0.Final Reporter: Pete Muir If I run {code} forge git-plugin git://github.com/forge/scaffold-aerogear.git {code} outside of a project, I get an ISE, if I run it in a project, it works. {code} [no project] workspace-jbds $ forge git-plugin git://github.com/forge/scaffold-aerogear.git ***ERROR*** [forge git-plugin] null org.jboss.forge.shell.exceptions.CommandExecutionException at org.jboss.forge.shell.command.Execution.perform(Execution.java:153) at org.jboss.forge.shell.command.fshparser.FSHRuntime.run(FSHRuntime.java:125) at org.jboss.forge.shell.command.fshparser.FSHRuntime.run(FSHRuntime.java:63) at org.jboss.forge.shell.ShellImpl$ExecutorThread.run(ShellImpl.java:829) at org.jboss.forge.shell.ShellImpl.execute(ShellImpl.java:852) at org.jboss.forge.shell.ShellImpl.doShell(ShellImpl.java:642) 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:120) at java.lang.Thread.run(Thread.java:680) 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.jboss.forge.shell.command.Execution.perform(Execution.java:149) ... 31 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.jboss.solder.unwraps.UnwrapsInvocationHandler.invoke(UnwrapsInvocationHandler.java:82) at org.javassist.tmp.java.lang.Object_$$_javassist_0.getScopedConfiguration(Object_$$_javassist_0.java) at org.jboss.forge.shell.plugins.builtin.ForgePlugin.getProxySettings(ForgePlugin.java:190) at org.jboss.forge.shell.plugins.builtin.ForgePlugin.prepareProxyForJGit(ForgePlugin.java:472) at org.jboss.forge.shell.plugins.builtin.ForgePlugin.installFromGit(ForgePlugin.java:405) ... 36 more Caused by: java.lang.IllegalStateException at org.jboss.forge.shell.env.ScopedConfigurationAdapter.getScopedConfiguration(ScopedConfigurationAdapter.java:74) at org.jboss.forge.shell.env.ConfigurationAdapter.getScopedConfiguration(ConfigurationAdapter.java:59) ... 45 more {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

2
1
0 / 0

[JBoss JIRA] (FORGE-484) Document and Refine the <dependencies-as-resource-root/> Functionality

by Koen Aers (JIRA)

Koen Aers created FORGE-484: ------------------------------- Summary: Document and Refine the <dependencies-as-resource-root/> Functionality Key: FORGE-484 URL: https://issues.jboss.org/browse/FORGE-484 Project: Forge Issue Type: Feature Request Components: Shell Reporter: Koen Aers Assignee: Koen Aers Fix For: 2.0.0.Alpha1 FORGE-483 introduced the <dependencies-as-resource-root/> xml tag in the forge.xml file. This option makes sure that forge plugin dependencies will be deployed as root resources in the plugin module and not in the dependencies module. This can be refined to include/exclude only particular dependencies. It also needs to be properly documented. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

2
2
0 / 0

[JBoss JIRA] (FORGE-496) --scaffoldType faces redundant

by Burr Sutter (JIRA)

Burr Sutter created FORGE-496: --------------------------------- Summary: --scaffoldType faces redundant Key: FORGE-496 URL: https://issues.jboss.org/browse/FORGE-496 Project: Forge Issue Type: Enhancement Components: Scaffold Reporter: Burr Sutter scaffold setup --scaffoldType faces scaffold from-entity ~.model.* --scaffoldType faces --overwrite consider the above forge commands - the first line establishes that I want "faces" and the 2nd line requires "--scaffoldType faces" - can it not assume from the first line? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

2
3
0 / 0

[JBoss JIRA] (FORGE-494) import java.lang.Override; @Entity public class ProductOrder implements java.io.Serializable {

by Burr Sutter (JIRA)

Burr Sutter created FORGE-494: --------------------------------- Summary: import java.lang.Override;@Entity public class ProductOrder implements java.io.Serializable { Key: FORGE-494 URL: https://issues.jboss.org/browse/FORGE-494 Project: Forge Issue Type: Bug Environment: Mac OS X Lion Reporter: Burr Sutter When creating entities, I notice that Forge puts the @Entity line on the same physical line as the last import statement: import java.lang.Override;@Entity public class ProductOrder implements java.io.Serializable { import java.lang.Override;@Entity public class Item implements java.io.Serializable { import javax.persistence.TemporalType;@Entity public class Customer implements java.io.Serializable { commands are: persistence setup --provider HIBERNATE --container JBOSS_AS7 entity --named Customer --package ~.model field string --named firstName field string --named lastName field temporal --type DATE --named birthDate entity --named Item field string --named name field number --named price --type java.lang.Double field int --named stock entity --named ProductOrder -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

2
1
0 / 0

[JBoss JIRA] (FORGE-495) Forge generated entity: The serializable class ProductOrder does not declare a static final serialVersionUID field of type long

by Burr Sutter (JIRA)

Burr Sutter created FORGE-495: --------------------------------- Summary: Forge generated entity: The serializable class ProductOrder does not declare a static final serialVersionUID field of type long Key: FORGE-495 URL: https://issues.jboss.org/browse/FORGE-495 Project: Forge Issue Type: Enhancement Environment: Inside of JBDS5 Reporter: Burr Sutter Forge generated entities result in the following Warning when inside of JBDS. Note: using Forge at the command line and then Maven Import into JBDS The serializable class ProductOrder does not declare a static final serialVersionUID field of type long -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

2
1
0 / 0

[JBoss JIRA] (FORGE-491) REST plugin creates compilation errors when "id" setter is not called "setId()"

by Lincoln Baxter III (JIRA)

Lincoln Baxter III created FORGE-491: ---------------------------------------- Summary: REST plugin creates compilation errors when "id" setter is not called "setId()" Key: FORGE-491 URL: https://issues.jboss.org/browse/FORGE-491 Project: Forge Issue Type: Bug Components: Builtin Plugins, Java EE APIs Affects Versions: 1.0.0.Final Reporter: Lincoln Baxter III Fix For: 1.0.1.CR1, 1.0.1.Final If type of ID field is not Long or setter is not called "setId()", compilation errors occur in generated Endpoints. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
1
0 / 0

[JBoss JIRA] (FORGE-492) REST facet does not recognize Application class with ApplicationPath annotation

by Lincoln Baxter III (JIRA)

Lincoln Baxter III created FORGE-492: ---------------------------------------- Summary: REST facet does not recognize Application class with ApplicationPath annotation Key: FORGE-492 URL: https://issues.jboss.org/browse/FORGE-492 Project: Forge Issue Type: Bug Components: Builtin Plugins, Java EE APIs Affects Versions: 1.0.0.Final Reporter: Lincoln Baxter III Fix For: 1.0.1.CR1, 1.0.1.Final RestFacet only checks web.xml for REST activation. It should also scan the source tree for the @ApplicationPath and Application class. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
1
0 / 0

[JBoss JIRA] (FORGE-426) Maven ArtifactResolver/RemoteRepository not using proxy information

by Simon Gunzenreiner (Created) (JIRA)

Maven ArtifactResolver/RemoteRepository not using proxy information ------------------------------------------------------------------- Key: FORGE-426 URL: https://issues.jboss.org/browse/FORGE-426 Project: Forge Issue Type: Enhancement Components: Shell Affects Versions: 1.0.0.Beta5 Environment: Windows Reporter: Simon Gunzenreiner When starting the Forge shell in my environment (it turns out that using a HTTP proxy is relavant), it takes a long time for the prompt to appear. When setting up the plugins component, multiple error indications appear after a few minutes. All of this basically results in Forge not even being usable for the first steps described in the documentation - and might be related to https://issues.jboss.org/browse/FORGE-421. To confirm my suspicion that this could be related to using a HTTP proxy, I ran Forge with remote debugging. What I found is this: The MavenDependencyFacet, using the DefaultModelBuilder, initializes RemoteRepository objects without Proxy information.These RemoteRepositories are eventually used in WagonRepositoryConnector to connect to get artifacts (again - without applying a Proxy information). MAVEN_HOME btw. points to a valid Maven installation (with appropriate repository mirrors configured), and in the user home directory a valid settings.xml has even configured HTTP proxy information - but both do not seem to matter. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

3
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues March 2012