[JBoss JIRA] (FORGE-1125) Images path in forge-style.css is missing the contextPath
by George Gastaldi (JIRA)
George Gastaldi created FORGE-1125:
--------------------------------------
Summary: Images path in forge-style.css is missing the contextPath
Key: FORGE-1125
URL: https://issues.jboss.org/browse/FORGE-1125
Project: Forge
Issue Type: Feature Request
Components: Scaffold
Affects Versions: 1.3.3.Final
Reporter: George Gastaldi
Assignee: George Gastaldi
Priority: Trivial
Fix For: 1.4.0.Final
{quote}
<jp_2013> One thing I noticed about the scaffolding is that the CSS images don't seem to work. I had to update the background-image url to have #{request.contextPath}/resources/ in front of the file names
{quote}
--
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
11 years, 2 months
[JBoss JIRA] (FORGE-1114) Support multi-step UIWizard commands in Shell
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-1114?page=com.atlassian.jira.plugin... ]
George Gastaldi closed FORGE-1114.
----------------------------------
Fix Version/s: 2.0.0.Alpha11
(was: 2.x Future)
Resolution: Done
Done
> Support multi-step UIWizard commands in Shell
> ---------------------------------------------
>
> Key: FORGE-1114
> URL: https://issues.jboss.org/browse/FORGE-1114
> Project: Forge
> Issue Type: Feature Request
> Components: UI - Shell
> Affects Versions: 2.0.0.Alpha10
> Reporter: Lincoln Baxter III
> Assignee: George Gastaldi
> Fix For: 2.0.0.Alpha11
>
>
> {code}
> $ new-project --named blah
> User presses <TAB>:
> Options from Step 1 are displayed (Step 1 not yet valid):
> --type (required)
> --targetDir
> --topLevelPackage
> $ new-project --named blah --type “Forge Addon”
> User presses <TAB>:
> Options from Step 1 AND Step 2 are displayed (Step 1 is valid):
> --targetDir (Step 1)
> --topLevelPackage (Step 1)
> --projectLayout (Step 2)
> --installAddons (Step 2)
> $ new-project --named blah --type “Forge Addon” --projectLayout complex
> User presses <TAB>:
> Options from Step 2 only are displayed:
> --installAddons
> $ new-project --named blah --type “Maven” --projectLayout complex
> User presses <TAB>
> Shell throws error:
> “--projectLayout is not a valid input for “MavenProjectStep”
> Re-display previous line and let the user fix it. (Completion fails, but command line preserved.)
> $ new-project --named blah --type “Maven” --projectLayout complex
> {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
11 years, 2 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 closed FORGE-1124.
----------------------------------
Resolution: Rejected
User fixed himself
> 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
11 years, 2 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:
----------------------------------------
I replaced the POM to a from other project, it worked. Thanks for the help and good job with the project!
> 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
11 years, 2 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:
----------------------------------------
where can I find information of how forge works to know a project?
> 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
11 years, 2 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:
-------------------------------------------
It is possible for a mal-formed (incorrectly constructed) POM file to cause Forge to throw exceptions like this. I thought we had addressed most of those issues, but you may have found another (though it would help if you could try with the newest version of Forge.) Can you also check your POM file for syntax errors?
> 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
11 years, 2 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:
----------------------------------------
The stacktrace seems incomplete. Could you check the log inside ~/.forge ?
> 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
11 years, 2 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,
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
11 years, 2 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:
----------------------------------------
OK, Verbose worked... the stack trace follows:
***ERROR*** Exception encountered: (type "set VERBOSE false" to disable stack traces)
[no project] Workspace-JEE $ at org.jboss.forge.shell.plugins.builtin.ChangeDirectoryPlugin.run(ChangeDirectoryPlugin.java:52)
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.forge.shell.command.Execution.perform(Execution.java:134)
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:789)
at org.jboss.forge.shell.ShellImpl.execute(ShellImpl.java:812)
at org.jboss.forge.shell.ShellImpl.doShell(ShellImpl.java:602)
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.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: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:172)
at java.lang.Thread.run(Thread.java:722)
> 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
11 years, 2 months