[JBoss JIRA] (FORGE-2048) Using <optional> UI dependency causes Projects addon to fail to deploy (without UI addon)
by Lincoln Baxter III (JIRA)
Lincoln Baxter III created FORGE-2048:
-----------------------------------------
Summary: Using <optional> UI dependency causes Projects addon to fail to deploy (without UI addon)
Key: FORGE-2048
URL: https://issues.jboss.org/browse/FORGE-2048
Project: Forge
Issue Type: Feature Request
Components: Furnace CDI, Projects, UI - API
Affects Versions: 2.10.1.Final
Reporter: Lincoln Baxter III
Fix For: 2.x Future
Mark the org.jboss.forge.addon:ui addon as <optional>true</optional> and run the test suite. ConfigurationFactoryTest and others will fail due to Projects addon failing due to injection point resolution errors that should not have occurred. These beans should simply be deactivated and not provided. Seems like a Weld bug.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 7 months
[JBoss JIRA] (FORGE-2047) Commands to add and remove Maven plugins into pom.xml
by Antonio Goncalves (JIRA)
Antonio Goncalves created FORGE-2047:
----------------------------------------
Summary: Commands to add and remove Maven plugins into pom.xml
Key: FORGE-2047
URL: https://issues.jboss.org/browse/FORGE-2047
Project: Forge
Issue Type: Sub-task
Components: UI - Shell
Affects Versions: 2.10.1.Final
Reporter: Antonio Goncalves
Fix For: 2.x Future
Today we have commands to add/remove dependencies into a `pom.xml` :
{code}
project-add-dependencies
project-remove-dependencies
project-add-managed-dependencies
project-remove-managed-dependencies
{code}
We need to same functionnalites but for plugins. Commands such as :
{code}
project-add-plugin-dependencies
project-remove-plugin-dependencies
{code}
So a command like this :
{code}
project-add-plugin-dependencies org.codehaus.mojo:exec-maven-plugin:1.3.1
{code}
Would add the following to the {{pom.xml}} :
{code}
<plugins>
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>exec-maven-plugin</artifactId>
<version>1.3.1</version>
</plugin>
</plugins>
{code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 7 months
[JBoss JIRA] (FORGE-2046) 'ls' command throws un-useful error when child directory does not exist.
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-2046?page=com.atlassian.jira.plugin... ]
George Gastaldi closed FORGE-2046.
----------------------------------
Assignee: George Gastaldi
Fix Version/s: 2.10.2.Final
Resolution: Done
> 'ls' command throws un-useful error when child directory does not exist.
> ------------------------------------------------------------------------
>
> Key: FORGE-2046
> URL: https://issues.jboss.org/browse/FORGE-2046
> Project: Forge
> Issue Type: Feature Request
> Components: Builtin Plugins, UI - Shell
> Affects Versions: 2.10.1.Final
> Reporter: Lincoln Baxter III
> Assignee: George Gastaldi
> Fix For: 2.10.2.Final
>
>
> {code}
> [Desktop]$ ls /Users/lbaxter/projects/jboss-migration/windup/test-files/jee-example-app-1.0.0.ear
> ***ERROR*** Error while executing 'ls'
> java.lang.RuntimeException: no such child: projects
> at org.jboss.forge.addon.resource.util.ResourcePathResolver.resolve(ResourcePathResolver.java:235)
> at org.jboss.forge.addon.shell.command.LsCommand.execute(LsCommand.java:81)
> 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:606)
> at org.jboss.forge.furnace.proxy.ClassLoaderInterceptor$1.call(ClassLoaderInterceptor.java:87)
> at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42)
> at org.jboss.forge.furnace.proxy.ClassLoaderInterceptor.invoke(ClassLoaderInterceptor.java:103)
> at org.jboss.forge.addon.shell.command.LsCommand_$$_javassist_9eb4b11a-8950-4ee1-af6c-0859a534db50.execute(LsCommand_$$_javassist_9eb4b11a-8950-4ee1-af6c-0859a534db50.java)
> at org.jboss.forge.addon.ui.impl.controller.SingleCommandControllerImpl.execute(SingleCommandControllerImpl.java:88)
> at org.jboss.forge.addon.shell.aesh.CommandAdapter.execute(CommandAdapter.java:74)
> at org.jboss.aesh.console.AeshConsoleImpl$AeshConsoleCallbackImpl.execute(AeshConsoleImpl.java:325)
> at org.jboss.aesh.console.AeshProcess.run(AeshProcess.java:40)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> ***ERROR*** no such child: projects
> [Desktop]$
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 7 months
[JBoss JIRA] (FORGE-2046) 'ls' command throws un-useful error when child directory does not exist.
by Lincoln Baxter III (JIRA)
Lincoln Baxter III created FORGE-2046:
-----------------------------------------
Summary: 'ls' command throws un-useful error when child directory does not exist.
Key: FORGE-2046
URL: https://issues.jboss.org/browse/FORGE-2046
Project: Forge
Issue Type: Feature Request
Components: Builtin Plugins, UI - Shell
Affects Versions: 2.10.1.Final
Reporter: Lincoln Baxter III
{code}
[Desktop]$ ls /Users/lbaxter/projects/jboss-migration/windup/test-files/jee-example-app-1.0.0.ear
***ERROR*** Error while executing 'ls'
java.lang.RuntimeException: no such child: projects
at org.jboss.forge.addon.resource.util.ResourcePathResolver.resolve(ResourcePathResolver.java:235)
at org.jboss.forge.addon.shell.command.LsCommand.execute(LsCommand.java:81)
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:606)
at org.jboss.forge.furnace.proxy.ClassLoaderInterceptor$1.call(ClassLoaderInterceptor.java:87)
at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42)
at org.jboss.forge.furnace.proxy.ClassLoaderInterceptor.invoke(ClassLoaderInterceptor.java:103)
at org.jboss.forge.addon.shell.command.LsCommand_$$_javassist_9eb4b11a-8950-4ee1-af6c-0859a534db50.execute(LsCommand_$$_javassist_9eb4b11a-8950-4ee1-af6c-0859a534db50.java)
at org.jboss.forge.addon.ui.impl.controller.SingleCommandControllerImpl.execute(SingleCommandControllerImpl.java:88)
at org.jboss.forge.addon.shell.aesh.CommandAdapter.execute(CommandAdapter.java:74)
at org.jboss.aesh.console.AeshConsoleImpl$AeshConsoleCallbackImpl.execute(AeshConsoleImpl.java:325)
at org.jboss.aesh.console.AeshProcess.run(AeshProcess.java:40)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
***ERROR*** no such child: projects
[Desktop]$
{code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 7 months
[JBoss JIRA] (FORGEPLUGINS-175) Upgrade to Modernizr 2.8.3
by Vineet Reynolds (JIRA)
Vineet Reynolds created FORGEPLUGINS-175:
--------------------------------------------
Summary: Upgrade to Modernizr 2.8.3
Key: FORGEPLUGINS-175
URL: https://issues.jboss.org/browse/FORGEPLUGINS-175
Project: Forge Plugins/Addons
Issue Type: Task
Components: AngularJS Scaffold
Reporter: Vineet Reynolds
Assignee: Vineet Reynolds
Upgrade to Modernizr 2.8.3, as this is currently the most stable version of the component, to be used in WFK 2.7.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 7 months