June 2014 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-1799) Forge 1.4.3 in JBoss Developer Studio - forge install-plugin arquillian - Fatal error compiling: tools.jar not found: C:\Java\32-bit\jre7\..\lib\tools.jar -> [Help 1]

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1799?page=com.atlassian.jira.plugin... ] George Gastaldi commented on FORGE-1799: ---------------------------------------- You are using a JRE, install a JDK > Forge 1.4.3 in JBoss Developer Studio - forge install-plugin arquillian - Fatal error compiling: tools.jar not found: C:\Java\32-bit\jre7\..\lib\tools.jar -> [Help 1] > ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: FORGE-1799 > URL: https://issues.jboss.org/browse/FORGE-1799 > Project: Forge > Issue Type: Bug > Environment: JBoss Developer Studio 7.1.1 > Reporter: William Diaz Pabón > > IDE: JBoss Developer Studio 7.1.1. > Forge: 1.4.3.Final > S.O: Window 7 > JDK: C:\Java\32-bit\jdk1.7.0_55 > Command: forge install-plugin arquillian > Out: > [arquillian-tutorial] arquillian-tutorial $ forge install-plugin arquillian > ***INFO*** Preparing to install plugin: arquillian > ***INFO*** Checking out plugin source files to [C:\Users\William\AppData\Local\Temp\forgetemp3008896451163330389] via 'git' > ***INFO*** Switching to branch/tag [refs/heads/1.4.0.Final] > ***INFO*** Invoking build with underlying build system. > [INFO] Scanning for projects... > [INFO] > [INFO] ------------------------------------------------------------------------ > [INFO] Building arquillian-plugin 1.0.0-SNAPSHOT > [INFO] ------------------------------------------------------------------------ > [INFO] > [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @ arquillian-plugin --- > [INFO] > [INFO] --- maven-resources-plugin:2.4.3:resources (default-resources) @ arquillian-plugin --- > [INFO] Using 'UTF-8' encoding to copy filtered resources. > [INFO] Copying 6 resources > [INFO] > [INFO] --- maven-compiler-plugin:2.5.1:compile (default-compile) @ arquillian-plugin --- > [INFO] Compiling 25 source files to C:\Users\William\AppData\Local\Temp\forgetemp3008896451163330389\target\classes > [INFO] ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] ------------------------------------------------------------------------ > [INFO] Total time: 1.402s > [INFO] Finished at: Fri May 09 00:18:33 COT 2014 > [INFO] Final Memory: 32M/86M > [INFO] ------------------------------------------------------------------------ > [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.5.1:compile (default-compile) on project arquillian-plugin: Fatal error compiling: tools.jar not found: C:\Java\32-bit\jre7\..\lib\tools.jar -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please read the following articles: > [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException > ***INFO*** Cleaning up temp workspace [C:\Users\William\AppData\Local\Temp\forgetemp3008896451163330389] > org.jboss.forge.project.build.BuildException: Build failed.Deleted C:\Users\William\AppData\Local\Temp\forgetemp3008896451163330389 > ***ERROR*** Exception encountered: (type "set VERBOSE false" to disable stack traces) > [arquillian-tutorial] arquillian-tutorial $ > at org.jboss.forge.maven.facets.MavenProjectBuilder.build(MavenProjectBuilder.java:87) > at org.jboss.forge.shell.plugins.PluginManager.installFromProject(PluginManager.java:179) > at org.jboss.forge.shell.plugins.builtin.ForgePlugin.installFromGit(ForgePlugin.java:387) > at org.jboss.forge.shell.plugins.builtin.ForgePlugin.installFromIndex(ForgePlugin.java:206) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) > at java.lang.reflect.Method.invoke(Unknown Source) > 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(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) > at java.lang.reflect.Method.invoke(Unknown Source) > 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(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) > at java.lang.reflect.Method.invoke(Unknown Source) > 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(Unknown Source) -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ROASTER-12) Shade the JDT dependencies into Roaster-JDT

by Walter Medvedeo (JIRA)

[ https://issues.jboss.org/browse/ROASTER-12?page=com.atlassian.jira.plugin... ] Walter Medvedeo commented on ROASTER-12: ---------------------------------------- Done. > Shade the JDT dependencies into Roaster-JDT > ------------------------------------------- > > Key: ROASTER-12 > URL: https://issues.jboss.org/browse/ROASTER-12 > Project: Roaster > Issue Type: Feature Request > Components: JDT > Affects Versions: 2.3.0.Final > Reporter: George Gastaldi > Assignee: Lincoln Baxter III > Fix For: 2.4.0.Final > > > The current JDT version used conflicts with ECJ in Drools. We should shade the JDT classes since we don't expect people to use them directly with Roaster. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1729) Test harness should set the Configuration directory to use the test temp dir by default

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1729?page=com.atlassian.jira.plugin... ] George Gastaldi commented on FORGE-1729: ---------------------------------------- Is there any system property we might check if it is being running from a unit test? > Test harness should set the Configuration directory to use the test temp dir by default > --------------------------------------------------------------------------------------- > > Key: FORGE-1729 > URL: https://issues.jboss.org/browse/FORGE-1729 > Project: Forge > Issue Type: Enhancement > Components: Configuration > Affects Versions: 2.3.0.Final > Reporter: Lincoln Baxter III > Assignee: Lincoln Baxter III > Fix For: 2.5.0.Final > > > Currently the UserConfiguration references the current users home directory while running tests - it should use the available system property while running tests in order to direct the config dir to a temp location for that test execution: > {code} > static final String USER_CONFIG_PATH = "org.jboss.forge.addon.configuration.USER_CONFIG_PATH"; > String property = System.getProperty(USER_CONFIG_PATH);{code} -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1709) No way to generate one-to-many mapping

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1709?page=com.atlassian.jira.plugin... ] George Gastaldi commented on FORGE-1709: ---------------------------------------- That is because you are using the transient flag. It is not possible atm to create relationship fields while transient is set. > No way to generate one-to-many mapping > -------------------------------------- > > Key: FORGE-1709 > URL: https://issues.jboss.org/browse/FORGE-1709 > Project: Forge > Issue Type: Feature Request > Affects Versions: 2.3.0.Final > Reporter: Arun Gupta > Assignee: George Gastaldi > > jpa-new-field has only the following options: > --targetEntity --named --type --columnName --length --lob --transient > There is no way to generate one-to-many mapping. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1729) Test harness should set the Configuration directory to use the test temp dir by default

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1729?page=com.atlassian.jira.plugin... ] George Gastaldi commented on FORGE-1729: ---------------------------------------- Is there any system property we might check if it is being running from a unit test? > Test harness should set the Configuration directory to use the test temp dir by default > --------------------------------------------------------------------------------------- > > Key: FORGE-1729 > URL: https://issues.jboss.org/browse/FORGE-1729 > Project: Forge > Issue Type: Enhancement > Components: Configuration > Affects Versions: 2.3.0.Final > Reporter: Lincoln Baxter III > Assignee: Lincoln Baxter III > Fix For: 2.5.0.Final > > > Currently the UserConfiguration references the current users home directory while running tests - it should use the available system property while running tests in order to direct the config dir to a temp location for that test execution: > {code} > static final String USER_CONFIG_PATH = "org.jboss.forge.addon.configuration.USER_CONFIG_PATH"; > String property = System.getProperty(USER_CONFIG_PATH);{code} -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1709) No way to generate one-to-many mapping

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1709?page=com.atlassian.jira.plugin... ] George Gastaldi commented on FORGE-1709: ---------------------------------------- That is because you are using the transient flag. It is not possible atm to create relationship fields while transient is set. > No way to generate one-to-many mapping > -------------------------------------- > > Key: FORGE-1709 > URL: https://issues.jboss.org/browse/FORGE-1709 > Project: Forge > Issue Type: Feature Request > Affects Versions: 2.3.0.Final > Reporter: Arun Gupta > Assignee: George Gastaldi > > jpa-new-field has only the following options: > --targetEntity --named --type --columnName --length --lob --transient > There is no way to generate one-to-many mapping. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-451) Warn a user if generating relationship CRUD screens and HashCode/Equals are missing

by Matej Briskar (JIRA)

[ https://issues.jboss.org/browse/FORGE-451?page=com.atlassian.jira.plugin.... ] Matej Briskar commented on FORGE-451: ------------------------------------- not acting properly when testing manually.. working on it > Warn a user if generating relationship CRUD screens and HashCode/Equals are missing > ----------------------------------------------------------------------------------- > > Key: FORGE-451 > URL: https://issues.jboss.org/browse/FORGE-451 > Project: Forge > Issue Type: Feature Request > Components: Scaffold > Affects Versions: 1.0.6.Final > Reporter: Pete Muir > Assignee: Matej Briskar > Labels: Starter > Fix For: 2.x Future > > > It's necessary to provide these on the entities in order for drop downs to work. If not provided, there should be a WARN message. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1862) Forge2: CLI won't autocomplete workspace project names unless list them first

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/FORGE-1862?page=com.atlassian.jira.plugin... ] Koen Aers moved JBIDE-17491 to FORGE-1862: ------------------------------------------ Project: Forge (was: Tools (JBoss Tools)) Key: FORGE-1862 (was: JBIDE-17491) Affects Version/s: 2.6.0.Final (was: 4.2.0.Beta2) Component/s: (was: forge) > Forge2: CLI won't autocomplete workspace project names unless list them first > ----------------------------------------------------------------------------- > > Key: FORGE-1862 > URL: https://issues.jboss.org/browse/FORGE-1862 > Project: Forge > Issue Type: Bug > Affects Versions: 2.6.0.Final > Environment: Fedora 19, OpenJDK 7 > Reporter: Michelle Murray > > On forge2 start, on CLI type 'cd ' and beginning of workspace project name and press tab key for CLI to autocomplete project name. > But tab doesn't do anything. > To work around this, on CLI first enter 'ls' to list the projects in the workspace. Then type 'cd ' and beginning of workspace project name and press tab key and this time the autocomplete works. > This issues does not occur for forge1 CLI in same version of JBDS. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1622) It would be good if Aesh had access to export variables

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1622?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-1622: ----------------------------------- Status: Open (was: Pull Request Sent) > It would be good if Aesh had access to export variables > ------------------------------------------------------- > > Key: FORGE-1622 > URL: https://issues.jboss.org/browse/FORGE-1622 > Project: Forge > Issue Type: Feature Request > Components: UI - Shell > Affects Versions: 2.1.1.Final > Reporter: Antonio Goncalves > Assignee: Daniel Cunha > Priority: Minor > Fix For: 2.x Future > > > This would be a "nice to have" feature from the shell command line. > I'm under OS X and I have a set of variables that I've exported. As an example, all my code is under {{$CODE_HOME}}. It would be good if I code {{cd $CODE_HOME}} when I'm in Aesh : > {code} > ~$ cd $CODE_HOME // Under OS X > ~/Documents/Code$ forge // Entering Forge > _____ > | ___|__ _ __ __ _ ___ > | |_ / _ \| `__/ _` |/ _ \ \\ > | _| (_) | | | (_| | __/ // > |_| \___/|_| \__, |\___| > |___/ > JBoss Forge, version [ 2.1.1.Final ] - JBoss, by Red Hat, Inc. > [Code]$ cd ~ > [antoniombp]$ cd $CODE_HOME // Good if it goes to the right directory > [antoniombp]$ echo $CODE_HOME // Doesn't have access to the exported variable > [antoniombp]$ > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1855) Simple Container should support singleton services

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1855?page=com.atlassian.jira.plugin... ] George Gastaldi commented on FORGE-1855: ---------------------------------------- -1 to changing the Addon interface > Simple Container should support singleton services > -------------------------------------------------- > > Key: FORGE-1855 > URL: https://issues.jboss.org/browse/FORGE-1855 > Project: Forge > Issue Type: Feature Request > Components: Furnace Simple > Affects Versions: 2.6.0.Final > Reporter: George Gastaldi > Assignee: Matej Briskar > Fix For: 2.x Future > > > In CDI we use @Singleton to make a bean a singleton, however there is no equivalent on the simple container. > I propose a {{public interface SingletonService extends Service}} that could be checked while creating instances in {{SimpleExportedInstanceImpl}} -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues June 2014