December 2011 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-340) Change default plugin checkout location to use the .forge/plugins-sources directory

by Lincoln Baxter III (Updated) (JIRA)

[ https://issues.jboss.org/browse/FORGE-340?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III updated FORGE-340: ------------------------------------- Fix Version/s: 1.0.0.CR1 (was: 1.0.0.Beta4) > Change default plugin checkout location to use the .forge/plugins-sources directory > ----------------------------------------------------------------------------------- > > Key: FORGE-340 > URL: https://issues.jboss.org/browse/FORGE-340 > Project: Forge > Issue Type: Task > Components: Shell > Affects Versions: 1.0.0.Alpha4 > Reporter: Lincoln Baxter III > Assignee: Rodney Russ > Priority: Minor > Fix For: 1.0.0.CR1 > > > {code}$ forge git-plugin git@github.com:repo/etc{code} > needs to use ~/.forge/plugins-sources/ instead of the /tmp directory - so that developers can hack on installed plugins more easily. > this code lives here: > https://github.com/forge/core/blob/master/shell/src/main/java/org/jboss/f... -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (FORGE-399) Provide project and global settings API

by Lincoln Baxter III (Created) (JIRA)

Provide project and global settings API --------------------------------------- Key: FORGE-399 URL: https://issues.jboss.org/browse/FORGE-399 Project: Forge Issue Type: Feature Request Components: Plugin API Affects Versions: 1.0.0.Beta3 Reporter: Lincoln Baxter III Fix For: 1.0.0.Final Need an API with which plugins may save settings either at the project level ($PROJECT_ROOT/.forge) or at the global level (~/.forge/settings). This would be the first step in allowing plugins to use more intelligent defaults, and remember what users have done previously to avoid tedious interactions. -- 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

13 years, 1 month

5
6
0 / 0

[JBoss JIRA] (FORGE-404) Cannot scaffold for entities with DATE fields

by Lincoln Baxter III (Created) (JIRA)

Cannot scaffold for entities with DATE fields --------------------------------------------- Key: FORGE-404 URL: https://issues.jboss.org/browse/FORGE-404 Project: Forge Issue Type: Bug Components: Scaffold Affects Versions: 1.0.0.Beta3 Reporter: Lincoln Baxter III Assignee: Richard Kennard Fix For: 1.0.0.Beta4 {code} new-project --named example --topLevelPackage com.e ls cat pom.xml scaffold setup cat pom.xml ls persistence setup --provider HIBERNATE --container JBOSS_AS7 ls entity --named Customer field string --named FirstName field string --named lastName field temporal --type DATE --named birthdate entity --named Profile cd ../Customer.jav field string --named bio cd ../Customer.java field oneToOne --named profile --fieldType com.e.domain.Profile.java --inverseFieldName customer cd ../Profile.java ls ls customer::Customer set VERBOSE true scaffold from-entity com.e.domain.*{code} Boom. Once you've removed the DATE field from Customer, scaffolding works fine. -- 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

13 years, 1 month

3
2
0 / 0

[JBoss JIRA] (FORGE-95) NPE when holding CTRL + arrow

by Lincoln Baxter III (Commented) (JIRA)

[ https://issues.jboss.org/browse/FORGE-95?page=com.atlassian.jira.plugin.s... ] Lincoln Baxter III commented on FORGE-95: ----------------------------------------- Any chance you could figure out what the difference is? I am unable to reproduce this issue. We have also now forked JLine into Forge itself, so we can directly fix any issue. > NPE when holding CTRL + arrow > ------------------------------ > > Key: FORGE-95 > URL: https://issues.jboss.org/browse/FORGE-95 > Project: Forge > Issue Type: Bug > Components: Shell, Windows > Affects Versions: 1.0.0.Beta2 > Environment: Windows 7 > Reporter: George Gastaldi > Fix For: 1.0.0.Final > > > The following stacktrace is presented with "set VERBOSE true": > {code:java} > java.lang.NullPointerException > at jline.WindowsTerminal.readVirtualKey(WindowsTerminal.java:200) > at jline.console.ConsoleReader.readVirtualKey(ConsoleReader.java:983) > at jline.console.ConsoleReader.readBinding(ConsoleReader.java:1208) > at jline.console.ConsoleReader.readLine(ConsoleReader.java:1300) > at jline.console.ConsoleReader.readLine(ConsoleReader.java:1246) > at jline.console.ConsoleReader.readLine(ConsoleReader.java:1232) > at org.jboss.seam.forge.shell.ShellImpl.readLine(ShellImpl.java:601) > at org.jboss.seam.forge.shell.ShellImpl.doShell(ShellImpl.java:486) > 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.seam.forge.shell.org$jboss$weld$bean-classpath-ManagedBean-class_org$jboss$seam$forge$shell$ShellImpl_$$_WeldClientProxy.doShell(org$jboss$weld$bean-classpath-ManagedBean-class_or > g$jboss$seam$forge$shell$ShellImpl_$$_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: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:632) > at org.jboss.weld.manager.BeanManagerImpl.fireEvent(BeanManagerImpl.java:619) > at org.jboss.weld.manager.BeanManagerImpl.fireEvent(BeanManagerImpl.java:613) > at org.jboss.seam.forge.shell.Bootstrap$2.run(Bootstrap.java:92) > {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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (FORGE-95) NPE when holding CTRL + arrow

by Lincoln Baxter III (Updated) (JIRA)

[ https://issues.jboss.org/browse/FORGE-95?page=com.atlassian.jira.plugin.s... ] Lincoln Baxter III updated FORGE-95: ------------------------------------ Fix Version/s: 1.0.0.Final (was: 1.0.0.Beta4) > NPE when holding CTRL + arrow > ------------------------------ > > Key: FORGE-95 > URL: https://issues.jboss.org/browse/FORGE-95 > Project: Forge > Issue Type: Bug > Components: Shell, Windows > Affects Versions: 1.0.0.Beta2 > Environment: Windows 7 > Reporter: George Gastaldi > Fix For: 1.0.0.Final > > > The following stacktrace is presented with "set VERBOSE true": > {code:java} > java.lang.NullPointerException > at jline.WindowsTerminal.readVirtualKey(WindowsTerminal.java:200) > at jline.console.ConsoleReader.readVirtualKey(ConsoleReader.java:983) > at jline.console.ConsoleReader.readBinding(ConsoleReader.java:1208) > at jline.console.ConsoleReader.readLine(ConsoleReader.java:1300) > at jline.console.ConsoleReader.readLine(ConsoleReader.java:1246) > at jline.console.ConsoleReader.readLine(ConsoleReader.java:1232) > at org.jboss.seam.forge.shell.ShellImpl.readLine(ShellImpl.java:601) > at org.jboss.seam.forge.shell.ShellImpl.doShell(ShellImpl.java:486) > 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.seam.forge.shell.org$jboss$weld$bean-classpath-ManagedBean-class_org$jboss$seam$forge$shell$ShellImpl_$$_WeldClientProxy.doShell(org$jboss$weld$bean-classpath-ManagedBean-class_or > g$jboss$seam$forge$shell$ShellImpl_$$_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: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:632) > at org.jboss.weld.manager.BeanManagerImpl.fireEvent(BeanManagerImpl.java:619) > at org.jboss.weld.manager.BeanManagerImpl.fireEvent(BeanManagerImpl.java:613) > at org.jboss.seam.forge.shell.Bootstrap$2.run(Bootstrap.java:92) > {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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-339) Run a script from a (non-local) URL

by Jonathan Fuerth (JIRA)

Run a script from a (non-local) URL ----------------------------------- Key: SEAMFORGE-339 URL: https://issues.jboss.org/browse/SEAMFORGE-339 Project: Seam Forge Issue Type: Feature Request Components: Forge Scripting Language Reporter: Jonathan Fuerth Priority: Minor Forge is a great way to help people get started with a new framework. Quick start guides can be simplified by using Forge scripts, but right now the instructions have to include "right click on the script, save as, remember where you saved it, run it in the Forge shell..." Being able to name a script by an HTTP/HTTPS URL would simplify quick-start guides greatly: they can say "To get started, type this Forge command exactly" and it will work. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

3
2
0 / 0

[JBoss JIRA] (FORGE-401) PersistencePlugin should not initialize default value for @ManyToOne

by Richard Kennard (Created) (JIRA)

PersistencePlugin should not initialize default value for @ManyToOne -------------------------------------------------------------------- Key: FORGE-401 URL: https://issues.jboss.org/browse/FORGE-401 Project: Forge Issue Type: Bug Reporter: Richard Kennard At present the PersistencePlugin generates the following default values in its entity beans: @OneToMany private Set<Grocery> groceries = new HashSet<Grocery>(); @OneToOne private Employer employer = new Employer(); @ManyToOne private Employer employer = new Employer(); The first one is non-controversial. The second is slightly controversial but actually makes things much easier for the UI so please keep it :) But the final one I definitely think should be removed. We should just leave @ManyToOne relationships as 'null' by default. It doesn't make sense to pre-initialize them, even for new entities, because they are meant to point to *existing* entities. -- 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

13 years, 1 month

6
7
0 / 0

[JBoss JIRA] (FORGE-390) Plugin builds successfully but cannot be executed

by Ryan Bradley (Created) (JIRA)

Plugin builds successfully but cannot be executed ------------------------------------------------- Key: FORGE-390 URL: https://issues.jboss.org/browse/FORGE-390 Project: Forge Issue Type: Bug Components: Plugin API, Usability Affects Versions: 1.0.0.Beta3 Environment: OS: Fedora 15, JPA Provider: Hibernate 4.0.0.CR6, Container: JBoss AS 7.0.3.Final Reporter: Ryan Bradley My plugin, created and developed in Forge, stopped being recognized by Forge. I tried removing the plugin from .forge/plugins/installed.xml, running 'forge source-plugin ${PATH_TO_PLUGIN}' again, confirming that it had been added to installed.xml again, and, although the build was successful, when I tried to execute the plugin, the command was not found. A pastebin of the build and subsequent attempted execution is provided at: http://pastebin.com/5us0GAMP. (Yes, I did double check that I used the same name as the plugin alias). Perhaps this could be a problem with the Forge plugin setup process? Note: as a workaround, I had to create a new plugin and copy over source code from the previous plugin. -- 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

13 years, 1 month

4
3
0 / 0

[JBoss JIRA] (FORGE-397) PersistencePlugin does not mark one side of a OneToOne as 'mappedBy'

by Richard Kennard (Created) (JIRA)

PersistencePlugin does not mark one side of a OneToOne as 'mappedBy' -------------------------------------------------------------------- Key: FORGE-397 URL: https://issues.jboss.org/browse/FORGE-397 Project: Forge Issue Type: Enhancement Reporter: Richard Kennard The PersistencePlugin currently generates OneToOne relationships like this: @OneToOne private Profile profile; public Profile getProfile() { return this.profile; } public void setProfile(final Profile profile) { this.profile = profile; } ...and... @OneToOne private Customer customer; public Customer getCustomer() { return this.customer; } public void setCustomer(final Customer customer) { this.customer = customer; } Ideally one side of the relationship should be marked as the 'inverse': @OneToOne(mappedBy="profile") private Customer customer; public Customer getCustomer() { return this.customer; } public void setCustomer(final Customer customer) { this.customer = customer; } -- 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

13 years, 1 month

3
2
0 / 0

[JBoss JIRA] (FORGE-384) Use dependency management and BOMs not direct manipulation of dependencies

by Pete Muir (Created) (JIRA)

Use dependency management and BOMs not direct manipulation of dependencies -------------------------------------------------------------------------- Key: FORGE-384 URL: https://issues.jboss.org/browse/FORGE-384 Project: Forge Issue Type: Bug Affects Versions: 1.0.0.Beta3 Reporter: Pete Muir Assignee: Lincoln Baxter III The recommended practice we have for archetypes and quickstarts mandates this, so Forge needs to follow. -- 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

13 years, 1 month

4
4
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues December 2011