February 2013 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-781) forge install-plugin command fails with cygwin

by Andreas Karalus (JIRA)

[ https://issues.jboss.org/browse/FORGE-781?page=com.atlassian.jira.plugin.... ] Andreas Karalus updated FORGE-781: ---------------------------------- Description: @See: https://community.jboss.org/message/797250 forge install-plugin <plugin> command fails if it is called from cygwin. I tried this with different forge versions (1.1.2, 1.1.3, 1.2.0) and different plugins (jboss-as-7, richfaces) I think the problem relies in the path resolution for loading modules with cygwin. This path ist not present: C:\cygwin\home\297646\.forge\plugins {code} roots: D:\Programme\forge-distribution-1.2.0.Final\modules,C:\cygwin\home\297646\.forge\plugins,D:\workspaces\forge-jbossas-quickstart\ {code} The .forge folder is installed under: C:\Users\297646\.forge\plugin (even if forge was called from cygwin first time). {code} 297646@TB01448C ~/workspaces/forge-jbossas-quickstart # forge Failed loading: org.richfaces.forge.richfaces-forge-plugin:1.0.5.Final:1.0.0-SNAPSHOT-d292c53d-b7ad-41b8-800e-8c2b4ea1475b org.jboss.modules.ModuleNotFoundException: Module org.richfaces.forge.richfaces-forge-plugin:1.0.0-SNAPSHOT-d292c53d-b7ad-41b8-800e-8c2b4ea1475b is not found in local module loader @2fcac6db (roots: D:\Programme\forge-distribution-1.2.0.Final\modules,C:\cygwin\home\297646\.forge\plugins,D:\workspaces\forge-jbossas-quickstart\.) at org.jboss.modules.LocalModuleLoader.findModule(LocalModuleLoader.java:126) at org.jboss.modules.ModuleLoader.loadModuleLocal(ModuleLoader.java:275) at org.jboss.modules.ModuleLoader.preloadModule(ModuleLoader.java:222) at org.jboss.modules.LocalModuleLoader.preloadModule(LocalModuleLoader.java:94) at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:204) at org.jboss.forge.shell.Bootstrap.loadPlugins(Bootstrap.java:254) at org.jboss.forge.shell.Bootstrap.access$200(Bootstrap.java:38) at org.jboss.forge.shell.Bootstrap$1.run(Bootstrap.java:125) at java.lang.Thread.run(Thread.java:662) _____ | ___|__ _ __ __ _ ___ | |_ / _ \| `__/ _` |/ _ \ \\ | _| (_) | | | (_| | __/ // |_| \___/|_| \__, |\___| |___/ JBoss Forge, version [ 1.2.0.Final ] - JBoss, by Red Hat, Inc. [ http://jboss.org/forge ] [jboss-as-quickstarts-parent] forge-jbossas-quickstart $ {code} was: @See: https://community.jboss.org/message/797250 forge install-plugin <plugin> command fails if it is called from cygwin. I tried this with different forge versions (1.1.2, 1.1.3, 1.2.0) and different plugins (jboss-as-7, richfaces) I think the problem relies in the path resolution for loading modules with cygwin. This path ist not present: C:\cygwin\home\297646\.forge\plugins The .forge folder is installed under: C:\Users\297646\.forge\plugin (even if called from cygwin). {code} 297646@TB01448C ~/workspaces/forge-jbossas-quickstart # forge Failed loading: org.richfaces.forge.richfaces-forge-plugin:1.0.5.Final:1.0.0-SNAPSHOT-d292c53d-b7ad-41b8-800e-8c2b4ea1475b org.jboss.modules.ModuleNotFoundException: Module org.richfaces.forge.richfaces-forge-plugin:1.0.0-SNAPSHOT-d292c53d-b7ad-41b8-800e-8c2b4ea1475b is not found in local module loader @2fcac6db (roots: D:\Programme\forge-distribution-1.2.0.Final\modules,C:\cygwin\home\297646\.forge\plugins,D:\workspaces\forge-jbossas-quickstart\.) at org.jboss.modules.LocalModuleLoader.findModule(LocalModuleLoader.java:126) at org.jboss.modules.ModuleLoader.loadModuleLocal(ModuleLoader.java:275) at org.jboss.modules.ModuleLoader.preloadModule(ModuleLoader.java:222) at org.jboss.modules.LocalModuleLoader.preloadModule(LocalModuleLoader.java:94) at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:204) at org.jboss.forge.shell.Bootstrap.loadPlugins(Bootstrap.java:254) at org.jboss.forge.shell.Bootstrap.access$200(Bootstrap.java:38) at org.jboss.forge.shell.Bootstrap$1.run(Bootstrap.java:125) at java.lang.Thread.run(Thread.java:662) _____ | ___|__ _ __ __ _ ___ | |_ / _ \| `__/ _` |/ _ \ \\ | _| (_) | | | (_| | __/ // |_| \___/|_| \__, |\___| |___/ JBoss Forge, version [ 1.2.0.Final ] - JBoss, by Red Hat, Inc. [ http://jboss.org/forge ] [jboss-as-quickstarts-parent] forge-jbossas-quickstart $ {code} > forge install-plugin command fails with cygwin > ----------------------------------------------- > > Key: FORGE-781 > URL: https://issues.jboss.org/browse/FORGE-781 > Project: Forge > Issue Type: Story > Affects Versions: 1.1.2.Final, 1.1.3.Final, 1.2.0.Final > Environment: cygwin > Reporter: Andreas Karalus > > @See: https://community.jboss.org/message/797250 > forge install-plugin <plugin> command fails if it is called from cygwin. > I tried this with different forge versions (1.1.2, 1.1.3, 1.2.0) and different plugins (jboss-as-7, richfaces) > I think the problem relies in the path resolution for loading modules with cygwin. This path ist not present: C:\cygwin\home\297646\.forge\plugins > {code} > roots: D:\Programme\forge-distribution-1.2.0.Final\modules,C:\cygwin\home\297646\.forge\plugins,D:\workspaces\forge-jbossas-quickstart\ > {code} > The .forge folder is installed under: C:\Users\297646\.forge\plugin (even if forge was called from cygwin first time). > {code} > 297646@TB01448C ~/workspaces/forge-jbossas-quickstart > # forge > Failed loading: org.richfaces.forge.richfaces-forge-plugin:1.0.5.Final:1.0.0-SNAPSHOT-d292c53d-b7ad-41b8-800e-8c2b4ea1475b > org.jboss.modules.ModuleNotFoundException: Module org.richfaces.forge.richfaces-forge-plugin:1.0.0-SNAPSHOT-d292c53d-b7ad-41b8-800e-8c2b4ea1475b is not found in local module loader @2fcac6db (roots: D:\Programme\forge-distribution-1.2.0.Final\modules,C:\cygwin\home\297646\.forge\plugins,D:\workspaces\forge-jbossas-quickstart\.) > at org.jboss.modules.LocalModuleLoader.findModule(LocalModuleLoader.java:126) > at org.jboss.modules.ModuleLoader.loadModuleLocal(ModuleLoader.java:275) > at org.jboss.modules.ModuleLoader.preloadModule(ModuleLoader.java:222) > at org.jboss.modules.LocalModuleLoader.preloadModule(LocalModuleLoader.java:94) > at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:204) > at org.jboss.forge.shell.Bootstrap.loadPlugins(Bootstrap.java:254) > at org.jboss.forge.shell.Bootstrap.access$200(Bootstrap.java:38) > at org.jboss.forge.shell.Bootstrap$1.run(Bootstrap.java:125) > at java.lang.Thread.run(Thread.java:662) > _____ > | ___|__ _ __ __ _ ___ > | |_ / _ \| `__/ _` |/ _ \ \\ > | _| (_) | | | (_| | __/ // > |_| \___/|_| \__, |\___| > |___/ > JBoss Forge, version [ 1.2.0.Final ] - JBoss, by Red Hat, Inc. [ http://jboss.org/forge ] > [jboss-as-quickstarts-parent] forge-jbossas-quickstart $ > {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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-781) forge install-plugin command fails with cygwin

by Andreas Karalus (JIRA)

Andreas Karalus created FORGE-781: ------------------------------------- Summary: forge install-plugin command fails with cygwin Key: FORGE-781 URL: https://issues.jboss.org/browse/FORGE-781 Project: Forge Issue Type: Story Affects Versions: 1.2.0.Final, 1.1.3.Final, 1.1.2.Final Environment: cygwin Reporter: Andreas Karalus @See: https://community.jboss.org/message/797250 forge install-plugin <plugin> command fails if it is called from cygwin. I tried this with different forge versions (1.1.2, 1.1.3, 1.2.0) and different plugins (jboss-as-7, richfaces) I think the problem relies in the path resolution for loading modules with cygwin. This path ist not present: C:\cygwin\home\297646\.forge\plugins The .forge folder is installed under: C:\Users\297646\.forge\plugin (even if called from cygwin). {code} 297646@TB01448C ~/workspaces/forge-jbossas-quickstart # forge Failed loading: org.richfaces.forge.richfaces-forge-plugin:1.0.5.Final:1.0.0-SNAPSHOT-d292c53d-b7ad-41b8-800e-8c2b4ea1475b org.jboss.modules.ModuleNotFoundException: Module org.richfaces.forge.richfaces-forge-plugin:1.0.0-SNAPSHOT-d292c53d-b7ad-41b8-800e-8c2b4ea1475b is not found in local module loader @2fcac6db (roots: D:\Programme\forge-distribution-1.2.0.Final\modules,C:\cygwin\home\297646\.forge\plugins,D:\workspaces\forge-jbossas-quickstart\.) at org.jboss.modules.LocalModuleLoader.findModule(LocalModuleLoader.java:126) at org.jboss.modules.ModuleLoader.loadModuleLocal(ModuleLoader.java:275) at org.jboss.modules.ModuleLoader.preloadModule(ModuleLoader.java:222) at org.jboss.modules.LocalModuleLoader.preloadModule(LocalModuleLoader.java:94) at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:204) at org.jboss.forge.shell.Bootstrap.loadPlugins(Bootstrap.java:254) at org.jboss.forge.shell.Bootstrap.access$200(Bootstrap.java:38) at org.jboss.forge.shell.Bootstrap$1.run(Bootstrap.java:125) at java.lang.Thread.run(Thread.java:662) _____ | ___|__ _ __ __ _ ___ | |_ / _ \| `__/ _` |/ _ \ \\ | _| (_) | | | (_| | __/ // |_| \___/|_| \__, |\___| |___/ JBoss Forge, version [ 1.2.0.Final ] - JBoss, by Red Hat, Inc. [ http://jboss.org/forge ] [jboss-as-quickstarts-parent] forge-jbossas-quickstart $ {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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-780) `forge install-plugin` from central repository fails when plugin name collides with tags in other entries

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-780?page=com.atlassian.jira.plugin.... ] George Gastaldi closed FORGE-780. --------------------------------- Resolution: Done Fixed > `forge install-plugin` from central repository fails when plugin name collides with tags in other entries > --------------------------------------------------------------------------------------------------------- > > Key: FORGE-780 > URL: https://issues.jboss.org/browse/FORGE-780 > Project: Forge > Issue Type: Bug > Components: Plugin Repository > Affects Versions: 1.2.0.Final > Reporter: Lincoln Baxter III > Assignee: George Gastaldi > Priority: Critical > Fix For: 1.2.1.Final > > > {code}forge install-plugin webapp{code} > Should result in "plugin not found," but instead you can see that it finds multiple entries. This is due to the fact that the installation is not using the plugin name, but rather the full text search used in "find-plugin". > This needs to be changed to resolve against only the plugin name when performing an install. -- 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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-780) `forge install-plugin` from central repository fails when plugin name collides with tags in other entries

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-780?page=com.atlassian.jira.plugin.... ] George Gastaldi reassigned FORGE-780: ------------------------------------- Assignee: George Gastaldi > `forge install-plugin` from central repository fails when plugin name collides with tags in other entries > --------------------------------------------------------------------------------------------------------- > > Key: FORGE-780 > URL: https://issues.jboss.org/browse/FORGE-780 > Project: Forge > Issue Type: Bug > Components: Plugin Repository > Affects Versions: 1.2.0.Final > Reporter: Lincoln Baxter III > Assignee: George Gastaldi > Priority: Critical > Fix For: 1.2.1.Final > > > {code}forge install-plugin webapp{code} > Should result in "plugin not found," but instead you can see that it finds multiple entries. This is due to the fact that the installation is not using the plugin name, but rather the full text search used in "find-plugin". > This needs to be changed to resolve against only the plugin name when performing an install. -- 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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-780) `forge install-plugin` from central repository fails when plugin name collides with tags in other entries

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-780?page=com.atlassian.jira.plugin.... ] George Gastaldi commented on FORGE-780: --------------------------------------- Raised the priority on this one, since it may lead to unexpected results > `forge install-plugin` from central repository fails when plugin name collides with tags in other entries > --------------------------------------------------------------------------------------------------------- > > Key: FORGE-780 > URL: https://issues.jboss.org/browse/FORGE-780 > Project: Forge > Issue Type: Bug > Components: Plugin Repository > Affects Versions: 1.2.0.Final > Reporter: Lincoln Baxter III > Priority: Critical > Fix For: 1.2.1.Final > > > {code}forge install-plugin webapp{code} > Should result in "plugin not found," but instead you can see that it finds multiple entries. This is due to the fact that the installation is not using the plugin name, but rather the full text search used in "find-plugin". > This needs to be changed to resolve against only the plugin name when performing an install. -- 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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-780) `forge install-plugin` from central repository fails when plugin name collides with tags in other entries

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-780?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-780: ---------------------------------- Priority: Critical (was: Major) > `forge install-plugin` from central repository fails when plugin name collides with tags in other entries > --------------------------------------------------------------------------------------------------------- > > Key: FORGE-780 > URL: https://issues.jboss.org/browse/FORGE-780 > Project: Forge > Issue Type: Bug > Components: Plugin Repository > Affects Versions: 1.2.0.Final > Reporter: Lincoln Baxter III > Priority: Critical > Fix For: 1.2.1.Final > > > {code}forge install-plugin webapp{code} > Should result in "plugin not found," but instead you can see that it finds multiple entries. This is due to the fact that the installation is not using the plugin name, but rather the full text search used in "find-plugin". > This needs to be changed to resolve against only the plugin name when performing an install. -- 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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-780) `forge install-plugin` from central repository fails when plugin name collides with tags in other entries

by Lincoln Baxter III (JIRA)

Lincoln Baxter III created FORGE-780: ---------------------------------------- Summary: `forge install-plugin` from central repository fails when plugin name collides with tags in other entries Key: FORGE-780 URL: https://issues.jboss.org/browse/FORGE-780 Project: Forge Issue Type: Bug Components: Plugin Repository Affects Versions: 1.2.0.Final Reporter: Lincoln Baxter III Fix For: 1.2.1.Final {code}forge install-plugin webapp{code} Should result in "plugin not found," but instead you can see that it finds multiple entries. This is due to the fact that the installation is not using the plugin name, but rather the full text search used in "find-plugin". This needs to be changed to resolve against only the plugin name when performing an install. -- 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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-779) Class parameters are not correctly loaded for the consuming addon's classloader

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-779?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-779: ---------------------------------- Workaround Description: The following method in ForgeWizard was created to temporarily workaround the issue: {code} private <T> Class<T> locateNativeClass(Class<T> type) { Class<T> result = type; AddonRegistry registry = ForgeService.INSTANCE.getAddonRegistry(); for (Addon addon : registry.getRegisteredAddons()) { try { ClassLoader classLoader = addon.getClassLoader(); result = (Class<T>) classLoader.loadClass(type.getName()); break; } catch (ClassNotFoundException e) { } } return result; } {code} was: The following method in ForgeWizard was created to temporarily workaround the issue: {code} private <T> Class<T> locateNativeClass(Class<T> type) { Class<T> result = type; AddonRegistry registry = ForgeService.INSTANCE.getAddonRegistry(); for (Addon addon : registry.getRegisteredAddons()) { try { ClassLoader classLoader = addon.getClassLoader(); result = (Class<T>) classLoader.loadClass(type.getName()); break; } catch (ClassNotFoundException e) { } } return result; } {code} > Class parameters are not correctly loaded for the consuming addon's classloader > ------------------------------------------------------------------------------- > > Key: FORGE-779 > URL: https://issues.jboss.org/browse/FORGE-779 > Project: Forge > Issue Type: Bug > Reporter: George Gastaldi > Priority: Critical > Fix For: 2.0.0.Alpha1 > > > Having the following scenario: > Eclipse plugin -> calls ConverterFactory -> passes Resource.class as a parameter > {code:java} > ConverterFactory.getConverter(File.class, Resource.class) > {code} > in ResourceConverterGenerator (resources addon): > {code:java} > @Override > public boolean handles(Class<?> source, Class<?> target) > { > return Resource.class.isAssignableFrom(target); > } > {code} > Returns false, because the classloader that loaded the Resource class is the Eclipse classloader, not the Resource addon classloader AND Resource.class is not visible in the convert addon. -- 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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-778) Include Hints plugin in Core

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-778?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III commented on FORGE-778: ------------------------------------------ +1 > Include Hints plugin in Core > ---------------------------- > > Key: FORGE-778 > URL: https://issues.jboss.org/browse/FORGE-778 > Project: Forge > Issue Type: Enhancement > Components: Builtin Plugins > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 1.2.1.Final > > > As for the F2F meeting in 2013, it has been decided that the Hint plugin should take part in core. -- 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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-778) Include Hints plugin in Core

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-778?page=com.atlassian.jira.plugin.... ] George Gastaldi commented on FORGE-778: --------------------------------------- I'd rather bundle it with JBT, altogether with the Hibernate tools (Reverse engineering) plugin. WDYT? > Include Hints plugin in Core > ---------------------------- > > Key: FORGE-778 > URL: https://issues.jboss.org/browse/FORGE-778 > Project: Forge > Issue Type: Enhancement > Components: Builtin Plugins > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 1.2.1.Final > > > As for the F2F meeting in 2013, it has been decided that the Hint plugin should take part in core. -- 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

13 years, 3 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues February 2013