[JBoss JIRA] (FORGE-779) Class parameters are not correctly loaded for the consuming addon's classloader
by Lincoln Baxter III (JIRA)
[ https://issues.jboss.org/browse/FORGE-779?page=com.atlassian.jira.plugin.... ]
Lincoln Baxter III closed FORGE-779.
------------------------------------
Fix Version/s: 2.0.1.Final
(was: 2.x Future)
Resolution: Done
DONE.
> 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
> Components: Furnace (Container)
> Reporter: George Gastaldi
> Assignee: Lincoln Baxter III
> Priority: Critical
> Fix For: 2.0.1.Final
>
>
> 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
10 years, 4 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 commented on FORGE-1432:
-------------------------------------------
Hey [~stalep] - Could you look at this class and tell me if you can think of any reason why it would freeze after executing the first line of a script?
https://github.com/forge/core/blob/master/shell/impl/src/main/java/org/jb...
Thanks!
> 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
10 years, 4 months
[JBoss JIRA] (FORGE-1590) Forge2 behind proxy
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-1590?page=com.atlassian.jira.plugin... ]
George Gastaldi commented on FORGE-1590:
----------------------------------------
Ok, no problem. Thanks!
(Restricted to Patch Contributor role)
> Forge2 behind proxy
> -------------------
>
> Key: FORGE-1590
> URL: https://issues.jboss.org/browse/FORGE-1590
> Project: Forge
> Issue Type: Feature Request
> Affects Versions: 2.0.0.Final
> Environment: Windows
> Reporter: Abhijith Nagarajan
> Assignee: George Gastaldi
> Priority: Critical
> Fix For: 2.0.1.Final
>
>
> Trying to work with Forge 2 behind proxy but not successful.
>
> Proxy configuration in Maven is done and works fine.
> Proxy configuration in config.xml in %USER_HOME%/.forge does not work. This use to work fine with forge 1.x.
> Raising this issue as suggested by George Gastaldi
>
--
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
10 years, 4 months
[JBoss JIRA] (FORGE-1590) Forge2 behind proxy
by Abhijith Nagarajan (JIRA)
[ https://issues.jboss.org/browse/FORGE-1590?page=com.atlassian.jira.plugin... ]
Abhijith Nagarajan commented on FORGE-1590:
-------------------------------------------
I have trouble downloading few dependent jars. I will do that today and will let you know the result by tomorrow.
Hope this is fine to you.
Thanks
(Restricted to Patch Contributor role)
> Forge2 behind proxy
> -------------------
>
> Key: FORGE-1590
> URL: https://issues.jboss.org/browse/FORGE-1590
> Project: Forge
> Issue Type: Feature Request
> Affects Versions: 2.0.0.Final
> Environment: Windows
> Reporter: Abhijith Nagarajan
> Assignee: George Gastaldi
> Priority: Critical
> Fix For: 2.0.1.Final
>
>
> Trying to work with Forge 2 behind proxy but not successful.
>
> Proxy configuration in Maven is done and works fine.
> Proxy configuration in config.xml in %USER_HOME%/.forge does not work. This use to work fine with forge 1.x.
> Raising this issue as suggested by George Gastaldi
>
--
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
10 years, 4 months
[JBoss JIRA] (FORGE-1590) Forge2 behind proxy
by Abhijith Nagarajan (JIRA)
[ https://issues.jboss.org/browse/FORGE-1590?page=com.atlassian.jira.plugin... ]
Abhijith Nagarajan commented on FORGE-1590:
-------------------------------------------
[ERROR] Failed to execute goal org.jboss.forge.furnace:furnace-maven-plugin:2.0.1-SNAPSHOT:addon-install (deploy-addons) on project forge-distribution: Execution deploy-addons of goal org.jboss.forge.furnace:furnace-maven-plugin:2.0.1-SNAPSHOT:addon-install failed: org.eclipse.aether.collection.DependencyCollectionException: Failed to read artifact descriptor for org.jboss.forge.addon:core:jar:forge-addon:2.0.1-SNAPSHOT: Could not transfer artifact org.jboss.forge.addon:core:pom:2.0.1-SNAPSHOT from/to com.springsource.repository.libraries.release (http://repository.springsource.com/maven/libraries/release): Error transferring file: Connection timed out: connect from http://repository.springsource.com/maven/libraries/release/org/jboss/forg... -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.jboss.forge.furnace:furnace-maven-plugin:2.0.1-SNAPSHOT:addon-install (deploy-addons) on project forge-distribution: Execution deploy-addons of goal org.jboss.forge.furnace:furnace-maven-plugin:2.0.1-SNAPSHOT:addon-install failed: org.eclipse.aether.collection.DependencyCollectionException: Failed to read artifact descriptor for org.jboss.forge.addon:core:jar:forge-addon:2.0.1-SNAPSHOT
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:224)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at org.apache.maven.lifecycle.internal.LifecycleThreadedBuilder$1.call(LifecycleThreadedBuilder.java:169)
at org.apache.maven.lifecycle.internal.LifecycleThreadedBuilder$1.call(LifecycleThreadedBuilder.java:165)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
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:744)
Caused by: org.apache.maven.plugin.PluginExecutionException: Execution deploy-addons of goal org.jboss.forge.furnace:furnace-maven-plugin:2.0.1-SNAPSHOT:addon-install failed: org.eclipse.aether.collection.DependencyCollectionException: Failed to read artifact descriptor for org.jboss.forge.addon:core:jar:forge-addon:2.0.1-SNAPSHOT
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:115)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
... 11 more
Caused by: java.lang.RuntimeException: org.eclipse.aether.collection.DependencyCollectionException: Failed to read artifact descriptor for org.jboss.forge.addon:core:jar:forge-addon:2.0.1-SNAPSHOT
at org.jboss.forge.furnace.manager.maven.addon.MavenAddonDependencyResolver.traverseAddonGraph(MavenAddonDependencyResolver.java:327)
at org.jboss.forge.furnace.manager.maven.addon.MavenAddonDependencyResolver.resolveAddonDependencyHierarchy(MavenAddonDependencyResolver.java:82)
at org.jboss.forge.furnace.manager.impl.AddonManagerImpl.info(AddonManagerImpl.java:54)
at org.jboss.forge.furnace.manager.impl.AddonManagerImpl.install(AddonManagerImpl.java:67)
at org.jboss.forge.furnace.maven.plugin.AddonInstallMojo.execute(AddonInstallMojo.java:75)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:106)
> Forge2 behind proxy
> -------------------
>
> Key: FORGE-1590
> URL: https://issues.jboss.org/browse/FORGE-1590
> Project: Forge
> Issue Type: Feature Request
> Affects Versions: 2.0.0.Final
> Environment: Windows
> Reporter: Abhijith Nagarajan
> Assignee: George Gastaldi
> Priority: Critical
> Fix For: 2.0.1.Final
>
>
> Trying to work with Forge 2 behind proxy but not successful.
>
> Proxy configuration in Maven is done and works fine.
> Proxy configuration in config.xml in %USER_HOME%/.forge does not work. This use to work fine with forge 1.x.
> Raising this issue as suggested by George Gastaldi
>
--
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
10 years, 4 months
[JBoss JIRA] (FORGE-1590) Forge2 behind proxy
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-1590?page=com.atlassian.jira.plugin... ]
George Gastaldi commented on FORGE-1590:
----------------------------------------
Can you paste2.org the stacktrace?
> Forge2 behind proxy
> -------------------
>
> Key: FORGE-1590
> URL: https://issues.jboss.org/browse/FORGE-1590
> Project: Forge
> Issue Type: Feature Request
> Affects Versions: 2.0.0.Final
> Environment: Windows
> Reporter: Abhijith Nagarajan
> Assignee: George Gastaldi
> Priority: Critical
> Fix For: 2.0.1.Final
>
>
> Trying to work with Forge 2 behind proxy but not successful.
>
> Proxy configuration in Maven is done and works fine.
> Proxy configuration in config.xml in %USER_HOME%/.forge does not work. This use to work fine with forge 1.x.
> Raising this issue as suggested by George Gastaldi
>
--
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
10 years, 4 months
[JBoss JIRA] (FORGE-1590) Forge2 behind proxy
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-1590?page=com.atlassian.jira.plugin... ]
George Gastaldi commented on FORGE-1590:
----------------------------------------
Try running with the {{-Dfurnace.dot.skip=true}} option set.
(Restricted to Developers role)
> Forge2 behind proxy
> -------------------
>
> Key: FORGE-1590
> URL: https://issues.jboss.org/browse/FORGE-1590
> Project: Forge
> Issue Type: Feature Request
> Affects Versions: 2.0.0.Final
> Environment: Windows
> Reporter: Abhijith Nagarajan
> Assignee: George Gastaldi
> Priority: Critical
> Fix For: 2.0.1.Final
>
>
> Trying to work with Forge 2 behind proxy but not successful.
>
> Proxy configuration in Maven is done and works fine.
> Proxy configuration in config.xml in %USER_HOME%/.forge does not work. This use to work fine with forge 1.x.
> Raising this issue as suggested by George Gastaldi
>
--
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
10 years, 4 months