[JBoss JIRA] (FORGE-1335) Creating new project, JVM IBM 1.7
by Martin Basovnik (JIRA)
[ https://issues.jboss.org/browse/FORGE-1335?page=com.atlassian.jira.plugin... ]
Martin Basovnik commented on FORGE-1335:
----------------------------------------
Hello,
I checked it and it works now for forge version 2.0.0.Final.
java:
java version "1.7.0"
Java(TM) SE Runtime Environment (build pxa6470sr4ifix-20130305_01(SR4+IV37419))
IBM J9 VM (build 2.6, JRE 1.7.0 Linux amd64-64 Compressed References 20130205_137358 (JIT enabled, AOT enabled)
J9VM - R26_Java726_SR4_20130205_1656_B137358
JIT - r11.b03_20130131_32403
GC - R26_Java726_SR4_20130205_1656_B137358_CMPRSS
J9CL - 20130205_137358)
JCL - 20130303_01 based on Oracle 7u13-b08
Martin
> 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
12 years, 2 months
[JBoss JIRA] (FORGE-1432) run command is missing (and with it, scripting)
by Antonio Goncalves (JIRA)
[ https://issues.jboss.org/browse/FORGE-1432?page=com.atlassian.jira.plugin... ]
Antonio Goncalves updated FORGE-1432:
-------------------------------------
Parent Issue: FORGE-1491 (was: FORGE-1505)
> run command is missing (and with it, scripting)
> -----------------------------------------------
>
> Key: FORGE-1432
> URL: https://issues.jboss.org/browse/FORGE-1432
> Project: Forge
> Issue Type: Sub-task
> Components: UI - Shell
> Affects Versions: 2.0.0.CR2
> Reporter: Antonio Goncalves
> Assignee: Lincoln Baxter III
> Fix For: 2.x Future
>
>
> I use a lot of scripts to start my projects, add/remove Maven dependencies.... So when I'm in Forge console, I type {{run ../myScript.fsh}}. For example, here is a script I use to get ride of EE 6 dependencies and add EE7 :
> {code}
> @/* ====================================== */;
> @/* == From Java EE 6 to 7 Dependencies == */;
> @/* ====================================== */;
> project remove-dependency org.hibernate.javax.persistence:hibernate-jpa-2.0-api ;
> project remove-dependency javax.validation:validation-api ;
> project remove-dependency org.hibernate:hibernate-validator ;
> project remove-dependency javax.enterprise:cdi-api ;
> project remove-dependency org.jboss.spec.javax.annotation:jboss-annotations-api_1.1_spec ;
> project remove-dependency org.jboss.spec.javax.ws.rs:jboss-jaxrs-api_1.1_spec ;
> project remove-dependency org.jboss.spec.javax.transaction:jboss-transaction-api_1.1_spec ;
> project remove-dependency org.jboss.spec.javax.ejb:jboss-ejb-api_3.1_spec ;
> project remove-dependency org.jboss.spec.javax.faces:jboss-jsf-api_2.1_spec ;
> project remove-dependency org.jboss.spec.javax.servlet:jboss-servlet-api_3.0_spec ;
> project add-dependency javax:javaee-api:7.0:provided ;
> project add-dependency org.primefaces:primefaces:4.0 ;
> project add-repository primefaces-repo http://repository.primefaces.org ;
> {code}
> I have other scripts like that. The good this is, without leaving the console, I can write :
> {code}
> [Forge]$ run script1.fsh
> [Forge]$ run script2.fsh
> [Forge]$ run script3.fsh
> {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
12 years, 2 months
[JBoss JIRA] (FORGE-1373) Native Aesh commands do not properly receive/resolve file paths
by Lincoln Baxter III (JIRA)
[ https://issues.jboss.org/browse/FORGE-1373?page=com.atlassian.jira.plugin... ]
Lincoln Baxter III updated FORGE-1373:
--------------------------------------
Fix Version/s: 2.x Future
(was: 2.0.0.Final)
> Native Aesh commands do not properly receive/resolve file paths
> ---------------------------------------------------------------
>
> Key: FORGE-1373
> URL: https://issues.jboss.org/browse/FORGE-1373
> Project: Forge
> Issue Type: Sub-task
> Components: UI - Shell
> Affects Versions: 2.0.0.Beta3
> Reporter: Lincoln Baxter III
> Fix For: 2.x Future
>
>
> {code}
> [Desktop]$ cd ~
> [lb3]$ cd projects/
> [projects]$ less
> .DS_Store jboss/ lincoln_javascript_code_style.xml runtime-EclipseApplication(1)/ talks/
> jboss-eclipse-formatting-rules.xml lb3_eclipse_preferences.epf ocpsoft/ runtime-EclipseApplication/
> [projects]$ ls
> .DS_Store jboss/ lincoln_javascript_code_style.xml runtime-EclipseApplication(1)/ talks/
> jboss-eclipse-formatting-rules.xml lb3_eclipse_preferences.epf ocpsoft/ runtime-EclipseApplication/
> [projects]$ less lincoln_javascript_code_style.xml
> /Users/lb3/Desktop/lincoln_javascript_code_style.xml: No such file or directory
> {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
12 years, 2 months
[JBoss JIRA] (FORGE-1432) run command is missing (and with it, scripting)
by Lincoln Baxter III (JIRA)
[ https://issues.jboss.org/browse/FORGE-1432?page=com.atlassian.jira.plugin... ]
Lincoln Baxter III updated FORGE-1432:
--------------------------------------
Fix Version/s: 2.x Future
(was: 2.0.0.Final)
> run command is missing (and with it, scripting)
> -----------------------------------------------
>
> Key: FORGE-1432
> URL: https://issues.jboss.org/browse/FORGE-1432
> Project: Forge
> Issue Type: Sub-task
> Components: UI - Shell
> Affects Versions: 2.0.0.CR2
> Reporter: Antonio Goncalves
> Assignee: Lincoln Baxter III
> Fix For: 2.x Future
>
>
> I use a lot of scripts to start my projects, add/remove Maven dependencies.... So when I'm in Forge console, I type {{run ../myScript.fsh}}. For example, here is a script I use to get ride of EE 6 dependencies and add EE7 :
> {code}
> @/* ====================================== */;
> @/* == From Java EE 6 to 7 Dependencies == */;
> @/* ====================================== */;
> project remove-dependency org.hibernate.javax.persistence:hibernate-jpa-2.0-api ;
> project remove-dependency javax.validation:validation-api ;
> project remove-dependency org.hibernate:hibernate-validator ;
> project remove-dependency javax.enterprise:cdi-api ;
> project remove-dependency org.jboss.spec.javax.annotation:jboss-annotations-api_1.1_spec ;
> project remove-dependency org.jboss.spec.javax.ws.rs:jboss-jaxrs-api_1.1_spec ;
> project remove-dependency org.jboss.spec.javax.transaction:jboss-transaction-api_1.1_spec ;
> project remove-dependency org.jboss.spec.javax.ejb:jboss-ejb-api_3.1_spec ;
> project remove-dependency org.jboss.spec.javax.faces:jboss-jsf-api_2.1_spec ;
> project remove-dependency org.jboss.spec.javax.servlet:jboss-servlet-api_3.0_spec ;
> project add-dependency javax:javaee-api:7.0:provided ;
> project add-dependency org.primefaces:primefaces:4.0 ;
> project add-repository primefaces-repo http://repository.primefaces.org ;
> {code}
> I have other scripts like that. The good this is, without leaving the console, I can write :
> {code}
> [Forge]$ run script1.fsh
> [Forge]$ run script2.fsh
> [Forge]$ run script3.fsh
> {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
12 years, 2 months
[JBoss JIRA] (FORGE-1479) Explicitly setup in Bean Validation, not in JPA
by Lincoln Baxter III (JIRA)
[ https://issues.jboss.org/browse/FORGE-1479?page=com.atlassian.jira.plugin... ]
Lincoln Baxter III commented on FORGE-1479:
-------------------------------------------
We will attempt to make the commands auto-setup their respective specs to resolve this.
> Explicitly setup in Bean Validation, not in JPA
> -----------------------------------------------
>
> Key: FORGE-1479
> URL: https://issues.jboss.org/browse/FORGE-1479
> Project: Forge
> Issue Type: Sub-task
> Components: UI - Shell
> Affects Versions: 2.0.0.CR2
> Reporter: Antonio Goncalves
> Fix For: 2.x Future
>
>
> Just after a creating a project, a create a new entity without setting up the persistence ({{jpa-setup}}) :
> {code}
> ***SUCCESS*** Project named 'test' has been created.
> [test]$ jpa-new-entity --named Author
> [Author.java]$ jpa-new-field --named firstname --length 50
> ***SUCCESS*** Field firstname created
> {code}
> This hasn't created a {{persistence.xml}} file. But on the other hand, if I want to add a constraint on the entity, I need to explicitelly setup Bean Validation :
> {code}
> [Author.java]$ con
> connection-profile-create connection-profile-remove constraint-setup
> [Author.java]$ constraint-setup
> ***SUCCESS*** Bean Validation is installed.
> [Author.java]$ con
> connection-profile-create connection-profile-remove constraint-add constraint-setup
> [Author.java]$ constraint-add --constraint NotNull --onProperty firstname
> ***SUCCESS*** Constraint NotNull successfully configured
> {code}
> if most of the information is giving at project creation, do we still need to explicitly setup Java EE components ? At the moment we have the following :
> {code}
> servlet-setup
> ejb-setup
> soap-setup
> cdi-setup
> jms-setup
> rest-setup
> jpa-setup
> faces-setup
> jstl-setup
> jta-setup
> constraint-setup
> {code}
> Most of these commands do not have parameters (except for persistence, rest, validation). So why not activate them by default (or only if {{export ACCEPT_DEFAULTS=true}} ) ? Something like : "if the command {{constraint-add}} is entered, Forge would go {{if constraint is not setup, then I invoke constraint-setup}}", "if the command {{ejb-new}} is entered, Forge would go {{if ejb is not setup, then I invoke ejb-setup}}"
> That would save some bugs (developers forgetting to setup things), less typing and shorter scripts.
--
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
12 years, 2 months
[JBoss JIRA] (FORGE-1489) Remove addon removes incorrect addon
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-1489?page=com.atlassian.jira.plugin... ]
George Gastaldi closed FORGE-1489.
----------------------------------
Fix Version/s: (was: 2.x Future)
Resolution: Cannot Reproduce Bug
Couldn't reproduce the issue with the latest SNAPSHOT. Please reopen if it happens again with the latest JBT plugin as well.
> Remove addon removes incorrect addon
> ------------------------------------
>
> Key: FORGE-1489
> URL: https://issues.jboss.org/browse/FORGE-1489
> Project: Forge
> Issue Type: Feature Request
> Components: Plugin Repository
> Affects Versions: 2.0.0.CR1
> Reporter: Tom Cunningham
> Assignee: George Gastaldi
> Priority: Critical
> Attachments: Graphic1.jpg, Graphic2.jpg
>
>
> I've been installing two addons off and on and noticed that when I choose "Remove Addon" in the forge menu, one of my addons is selected for removal by default (see Graphic1). I unselect it, select my other addon (see Graphic2), but the first addon that was selected by default is removed and the addon that I selected is kept.
--
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
12 years, 2 months
[JBoss JIRA] (FORGE-2) 'mv' command does not function on directories
by Lincoln Baxter III (JIRA)
[ https://issues.jboss.org/browse/FORGE-2?page=com.atlassian.jira.plugin.sy... ]
Lincoln Baxter III deleted FORGE-2:
-----------------------------------
> 'mv' command does not function on directories
> ---------------------------------------------
>
> Key: FORGE-2
> URL: https://issues.jboss.org/browse/FORGE-2
> Project: Forge
> Issue Type: Bug
> Reporter: Lincoln Baxter III
> Assignee: Jose Donizetti
> Labels: Starter
>
> [forge-distribution] dist $ cd ~/Projects/
> [no project] Projects $ mv
> jline/ gshell/ plugin-prettyfaces/ seam-render/
> gcode-issue-import/ prettyfaces/ viPlugin.license shrinkwrap-descriptors/
> maven-debug/ fpak/ javarebel.lic eclipse-code-formatter-profile.xml
> forge/
> [no project] Projects $ mv
> [source (of type org.jboss.seam.forge.resources.Resource)]
> jline/ gshell/ plugin-prettyfaces/ seam-render/
> gcode-issue-import/ prettyfaces/ viPlugin.license shrinkwrap-descriptors/
> maven-debug/ fpak/ javarebel.lic eclipse-code-formatter-profile.xml
> forge/
> [no project] Projects $ mv plugin-prettyfaces/
> [target (of type java.lang.String)]
> [no project] Projects $ mv plugin-prettyfaces/ prettyfaces/forge-plugin
> ***ERROR*** [mv] [UnknownFileResource] can have no children
> [no project] Projects $
--
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
12 years, 2 months