[JBoss JIRA] (FORGE-1124) Was not possible to read a folder as a project after editing the POM file.
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-1124?page=com.atlassian.jira.plugin... ]
George Gastaldi edited comment on FORGE-1124 at 8/20/13 1:10 PM:
-----------------------------------------------------------------
Cleiton,
This looks like a bug in the Primefaces plugin. Unfortunately we don't support that.
was (Author: gastaldi):
Cleiton,
This This is a bug in the Primefaces plugin. Unfortunately we don't support that.
> Was not possible to read a folder as a project after editing the POM file.
> --------------------------------------------------------------------------
>
> Key: FORGE-1124
> URL: https://issues.jboss.org/browse/FORGE-1124
> Project: Forge
> Issue Type: Bug
> Components: Forge Scripting Language
> Affects Versions: 1.2.2.Final
> Environment: win7 64bits, 4gb ram, hd 500gb, eclipse JUNO x64.
> Reporter: cleiton cardoso
>
> While trying to open a project by command line, using >>> cd C:\Users\cleiton.cardoso\Desktop\Workspaces\Workspace-JEE\sesuite <<< I received the following error >>***ERROR*** Exception encountered: null (type "set VERBOSE true" to enable stack traces)<<
> after that I've tried "ls" command the directory structure from my project appears in console but unable to understand it as a project folder.
--
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, 7 months
[JBoss JIRA] (FORGE-1124) Was not possible to read a folder as a project after editing the POM file.
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-1124?page=com.atlassian.jira.plugin... ]
George Gastaldi updated FORGE-1124:
-----------------------------------
Comment: was deleted
(was: Cleiton,
This looks like a bug in the Primefaces plugin. Unfortunately we don't support that.)
> Was not possible to read a folder as a project after editing the POM file.
> --------------------------------------------------------------------------
>
> Key: FORGE-1124
> URL: https://issues.jboss.org/browse/FORGE-1124
> Project: Forge
> Issue Type: Bug
> Components: Forge Scripting Language
> Affects Versions: 1.2.2.Final
> Environment: win7 64bits, 4gb ram, hd 500gb, eclipse JUNO x64.
> Reporter: cleiton cardoso
>
> While trying to open a project by command line, using >>> cd C:\Users\cleiton.cardoso\Desktop\Workspaces\Workspace-JEE\sesuite <<< I received the following error >>***ERROR*** Exception encountered: null (type "set VERBOSE true" to enable stack traces)<<
> after that I've tried "ls" command the directory structure from my project appears in console but unable to understand it as a project folder.
--
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, 7 months
[JBoss JIRA] (FORGE-1124) Was not possible to read a folder as a project after editing the POM file.
by cleiton cardoso (JIRA)
[ https://issues.jboss.org/browse/FORGE-1124?page=com.atlassian.jira.plugin... ]
cleiton cardoso updated FORGE-1124:
-----------------------------------
Comment: was deleted
(was: While trying to restart the plugin in eclipse after update I have the following error:
Error during PostStartup eventjava.lang.NullPointerException
at org.primefaces.forge.PrimefacesFacet.hasDependency(PrimefacesFacet.java:100)
at org.primefaces.forge.PrimefacesFacet.isInstalled(PrimefacesFacet.java:78)
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.findProjectRecursively(ProjectFactory.java:117)
at org.jboss.forge.shell.project.ProjectInitializer.doInit(ProjectInitializer.java:92)
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:601)
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:628)
at org.jboss.weld.event.EventImpl.fire(EventImpl.java:75)
at org.jboss.forge.shell.project.ProjectInitializer.postStartupTrigger(ProjectInitializer.java:45)
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:601)
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:163)
at java.lang.Thread.run(Thread.java:722)
I set verbose to true but as the same.
I'm using the forge plugin with jboss tools in eclipse and the version 1.3.3 for windows, the problem happens in there also.
)
> Was not possible to read a folder as a project after editing the POM file.
> --------------------------------------------------------------------------
>
> Key: FORGE-1124
> URL: https://issues.jboss.org/browse/FORGE-1124
> Project: Forge
> Issue Type: Bug
> Components: Forge Scripting Language
> Affects Versions: 1.2.2.Final
> Environment: win7 64bits, 4gb ram, hd 500gb, eclipse JUNO x64.
> Reporter: cleiton cardoso
>
> While trying to open a project by command line, using >>> cd C:\Users\cleiton.cardoso\Desktop\Workspaces\Workspace-JEE\sesuite <<< I received the following error >>***ERROR*** Exception encountered: null (type "set VERBOSE true" to enable stack traces)<<
> after that I've tried "ls" command the directory structure from my project appears in console but unable to understand it as a project folder.
--
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, 7 months
[JBoss JIRA] (FORGE-1124) Was not possible to read a folder as a project after editing the POM file.
by cleiton cardoso (JIRA)
[ https://issues.jboss.org/browse/FORGE-1124?page=com.atlassian.jira.plugin... ]
cleiton cardoso commented on FORGE-1124:
----------------------------------------
While trying to restart the plugin in eclipse after update I have the following error:
Error during PostStartup eventjava.lang.NullPointerException
at org.primefaces.forge.PrimefacesFacet.hasDependency(PrimefacesFacet.java:100)
at org.primefaces.forge.PrimefacesFacet.isInstalled(PrimefacesFacet.java:78)
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.findProjectRecursively(ProjectFactory.java:117)
at org.jboss.forge.shell.project.ProjectInitializer.doInit(ProjectInitializer.java:92)
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:601)
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:628)
at org.jboss.weld.event.EventImpl.fire(EventImpl.java:75)
at org.jboss.forge.shell.project.ProjectInitializer.postStartupTrigger(ProjectInitializer.java:45)
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:601)
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:163)
at java.lang.Thread.run(Thread.java:722)
I set verbose to true but as the same.
I'm using the forge plugin with jboss tools in eclipse and the version 1.3.3 for windows, the problem happens in there also.
> Was not possible to read a folder as a project after editing the POM file.
> --------------------------------------------------------------------------
>
> Key: FORGE-1124
> URL: https://issues.jboss.org/browse/FORGE-1124
> Project: Forge
> Issue Type: Bug
> Components: Forge Scripting Language
> Affects Versions: 1.2.2.Final
> Environment: win7 64bits, 4gb ram, hd 500gb, eclipse JUNO x64.
> Reporter: cleiton cardoso
>
> While trying to open a project by command line, using >>> cd C:\Users\cleiton.cardoso\Desktop\Workspaces\Workspace-JEE\sesuite <<< I received the following error >>***ERROR*** Exception encountered: null (type "set VERBOSE true" to enable stack traces)<<
> after that I've tried "ls" command the directory structure from my project appears in console but unable to understand it as a project folder.
--
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, 7 months
[JBoss JIRA] (FORGE-1124) Was not possible to read a folder as a project after editing the POM file.
by Lincoln Baxter III (JIRA)
[ https://issues.jboss.org/browse/FORGE-1124?page=com.atlassian.jira.plugin... ]
Lincoln Baxter III commented on FORGE-1124:
-------------------------------------------
Also, if possible, could you update to the latest version of Forge? We've fixed many windows and path issues recently: http://forge.jboss.org
Thanks,
Lincoln
> Was not possible to read a folder as a project after editing the POM file.
> --------------------------------------------------------------------------
>
> Key: FORGE-1124
> URL: https://issues.jboss.org/browse/FORGE-1124
> Project: Forge
> Issue Type: Bug
> Components: Forge Scripting Language
> Affects Versions: 1.2.2.Final
> Environment: win7 64bits, 4gb ram, hd 500gb, eclipse JUNO x64.
> Reporter: cleiton cardoso
>
> While trying to open a project by command line, using >>> cd C:\Users\cleiton.cardoso\Desktop\Workspaces\Workspace-JEE\sesuite <<< I received the following error >>***ERROR*** Exception encountered: null (type "set VERBOSE true" to enable stack traces)<<
> after that I've tried "ls" command the directory structure from my project appears in console but unable to understand it as a project folder.
--
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, 7 months
[JBoss JIRA] (FORGE-749) Support rendering of choices when prompting user for input
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-749?page=com.atlassian.jira.plugin.... ]
George Gastaldi closed FORGE-749.
---------------------------------
Assignee: George Gastaldi
Fix Version/s: 2.0.0.Alpha10
(was: 1.x Future)
Resolution: Done
This is implemented in Forge 2 and will not be implemented in Forge 1.x
> Support rendering of choices when prompting user for input
> ----------------------------------------------------------
>
> Key: FORGE-749
> URL: https://issues.jboss.org/browse/FORGE-749
> Project: Forge
> Issue Type: Feature Request
> Components: UI - Shell
> Affects Versions: 1.2.0.Final
> Reporter: Aslak Knutsen
> Assignee: George Gastaldi
> Fix For: 2.0.0.Alpha10
>
>
> In order to display Typed choice objects to the user
> As a Plugin Developer
> I want to be able to control the rendering
> Given a list of choices of type List<T>
> And a call to built in Shell.promptChoice( String, List<T> )
> Then it should be possible to pass in a Renderer to the shell to control out displayed
--
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, 7 months
[JBoss JIRA] (FORGE-1124) Was not possible to read a folder as a project after editing the POM file.
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-1124?page=com.atlassian.jira.plugin... ]
George Gastaldi commented on FORGE-1124:
----------------------------------------
Cleiton,
Could you run again with
{code}
set VERBOSE true
{code}
enabled ?
Please paste the exception in here after doing that.
Thanks!
> Was not possible to read a folder as a project after editing the POM file.
> --------------------------------------------------------------------------
>
> Key: FORGE-1124
> URL: https://issues.jboss.org/browse/FORGE-1124
> Project: Forge
> Issue Type: Bug
> Components: Forge Scripting Language
> Affects Versions: 1.2.2.Final
> Environment: win7 64bits, 4gb ram, hd 500gb, eclipse JUNO x64.
> Reporter: cleiton cardoso
>
> While trying to open a project by command line, using >>> cd C:\Users\cleiton.cardoso\Desktop\Workspaces\Workspace-JEE\sesuite <<< I received the following error >>***ERROR*** Exception encountered: null (type "set VERBOSE true" to enable stack traces)<<
> after that I've tried "ls" command the directory structure from my project appears in console but unable to understand it as a project folder.
--
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, 7 months
[JBoss JIRA] (FORGE-886) Should be able to re-install an existing Addon if it is a SNAPSHOT
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-886?page=com.atlassian.jira.plugin.... ]
George Gastaldi commented on FORGE-886:
---------------------------------------
Not using marker files, but re-installation occurs anyway
> Should be able to re-install an existing Addon if it is a SNAPSHOT
> ------------------------------------------------------------------
>
> Key: FORGE-886
> URL: https://issues.jboss.org/browse/FORGE-886
> Project: Forge
> Issue Type: Feature Request
> Components: Furnace (Container), Plugin Repository
> Affects Versions: 2.0.0.Alpha3
> Reporter: Lincoln Baxter III
> Assignee: George Gastaldi
> Fix For: 2.0.0.Alpha10
>
>
> Currently re-installing Addons is not supported, because there is no way to tell Forge to stop using the existing deployed files without giving it time to detect the change and re-deploy the addon.
> In order to implement this, the Forge registry file probably needs to use some kind of marker files.
> {code}
> .dodeploy
> .deployed
> .undeployed
> {code}
> So that it knows how to respond when changes are made faster than timestamps can detect. This would (hopefully) also in theory be a step toward multi JVM (multiple running forge / concurrent modification instance) support.
> This has been partially implemented, but only naively. The files are actually re-written on UNIX based OS's, and will be re-loaded next time the addon is disabled/re-enabled, but this will not work on Windows.
--
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, 7 months
[JBoss JIRA] (FORGE-886) Should be able to re-install an existing Addon if it is a SNAPSHOT
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-886?page=com.atlassian.jira.plugin.... ]
George Gastaldi closed FORGE-886.
---------------------------------
Assignee: George Gastaldi
Fix Version/s: 2.0.0.Alpha10
(was: 2.x Future)
Resolution: Done
Implemented using furnace-manager
> Should be able to re-install an existing Addon if it is a SNAPSHOT
> ------------------------------------------------------------------
>
> Key: FORGE-886
> URL: https://issues.jboss.org/browse/FORGE-886
> Project: Forge
> Issue Type: Feature Request
> Components: Furnace (Container), Plugin Repository
> Affects Versions: 2.0.0.Alpha3
> Reporter: Lincoln Baxter III
> Assignee: George Gastaldi
> Fix For: 2.0.0.Alpha10
>
>
> Currently re-installing Addons is not supported, because there is no way to tell Forge to stop using the existing deployed files without giving it time to detect the change and re-deploy the addon.
> In order to implement this, the Forge registry file probably needs to use some kind of marker files.
> {code}
> .dodeploy
> .deployed
> .undeployed
> {code}
> So that it knows how to respond when changes are made faster than timestamps can detect. This would (hopefully) also in theory be a step toward multi JVM (multiple running forge / concurrent modification instance) support.
> This has been partially implemented, but only naively. The files are actually re-written on UNIX based OS's, and will be re-loaded next time the addon is disabled/re-enabled, but this will not work on Windows.
--
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, 7 months
