April 2013 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-874) Proxy settings not used for maven web project

by Yann Albou (JIRA)

[ https://issues.jboss.org/browse/FORGE-874?page=com.atlassian.jira.plugin.... ] Yann Albou updated FORGE-874: ----------------------------- Fix Version/s: 1.2.4.Final Git Pull Request: https://github.com/forge/core/pull/314 Ok I have provided a pull request (https://github.com/forge/core/pull/314) I did the work in the ProjectInitializer class so that all projects/plugins can have a correct proxy configuration (so I removed the proxy conf from ForgePlugin class) hope it is the … [View More]correct way... > Proxy settings not used for maven web project > --------------------------------------------- > > Key: FORGE-874 > URL: https://issues.jboss.org/browse/FORGE-874 > Project: Forge > Issue Type: Bug > Components: Builtin Plugins > Affects Versions: 1.2.3.Final > Reporter: Yann Albou > Priority: Minor > Fix For: 1.2.4.Final > > > Proxy settings not used for maven web project > When loading a maven project of "war" type the following exception occurs: > {code} > Error during Startup event > org.jboss.shrinkwrap.descriptor.api.DescriptorImportException: Could not import XML from stream > at org.jboss.shrinkwrap.descriptor.spi.node.dom.XmlDomNodeImporterImpl.importAsNode(XmlDomNodeImporterImpl.java:76) > at org.jboss.shrinkwrap.descriptor.spi.node.dom.XmlDomNodeImporter.importAsNode(XmlDomNodeImporter.java:46) > at org.jboss.shrinkwrap.descriptor.spi.node.NodeDescriptorImporterBase.from(NodeDescriptorImporterBase.java:72) > at org.jboss.shrinkwrap.descriptor.spi.DescriptorImporterBase.from(DescriptorImporterBase.java:142) > at org.jboss.forge.spec.javaee.servlet.ServletFacetImpl.getConfig(ServletFacetImpl.java:95) > at org.jboss.forge.spec.javaee.jsf.FacesFacetImpl.isInstalled(FacesFacetImpl.java:71) > 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:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > 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.CurrentProject.setCurrentResource(CurrentProject.java:79) > at org.jboss.forge.shell.ShellImpl.init(ShellImpl.java:376) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > 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.init(ShellImpl$Proxy$_$$_WeldClientProxy.java) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > 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:167) > at java.lang.Thread.run(Thread.java:662) > Caused by: java.net.ConnectException: Connection timed out: connect > at java.net.PlainSocketImpl.socketConnect(Native Method) > at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:351) > at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:213) > at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:200) > at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366) > at java.net.Socket.connect(Socket.java:529) > at java.net.Socket.connect(Socket.java:478) > at sun.net.NetworkClient.doConnect(NetworkClient.java:163) > at sun.net.www.http.HttpClient.openServer(HttpClient.java:395) > at sun.net.www.http.HttpClient.openServer(HttpClient.java:530) > at sun.net.www.http.HttpClient.<init>(HttpClient.java:234) > at sun.net.www.http.HttpClient.New(HttpClient.java:307) > at sun.net.www.http.HttpClient.New(HttpClient.java:324) > at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:970) > at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:911) > at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:836) > at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1172) > at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.setupCurrentEntity(XMLEntityManager.java:677) > at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.startEntity(XMLEntityManager.java:1315) > at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.startDTDEntity(XMLEntityManager.java:1282) > at com.sun.org.apache.xerces.internal.impl.XMLDTDScannerImpl.setInputSource(XMLDTDScannerImpl.java:283) > at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$DTDDriver.dispatch(XMLDocumentScannerImpl.java:1194) > at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$DTDDriver.next(XMLDocumentScannerImpl.java:1090) > at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$PrologDriver.next(XMLDocumentScannerImpl.java:1003) > at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:648) > at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:140) > at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:511) > at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:808) > at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:737) > at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:119) > at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:235) > at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:284) > at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:124) > at org.jboss.shrinkwrap.descriptor.spi.node.dom.XmlDomNodeImporterImpl.importAsNode(XmlDomNodeImporterImpl.java:67) > ... 56 more > {code} > It is because the parser try to connect to http://java.sun.com:80 to parse the web.xml file but the proxy settings in forge config.xml is not used: > {code:xml} > <?xml version="1.0" encoding="UTF-8" standalone="no"?> > <configuration> > <proxy> > <host>my.proxy.com</host> > <port>80</port> > </proxy> > <forge> > <analytics> > <enabled>false</enabled> > </analytics> > </forge> > </configuration> > {code} > A workaround is to set the FORGE_OPTS to use sun default proxy: -Dhttp.proxyHost=my.proxy.com -Dhttp.proxyPort=80 > But it would be better to set the proxy as it is done in https://github.com/forge/core/blob/master/shell/src/main/java/org/jboss/f... -- 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 [View Less]

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-877) Addon sub-module is not imported into eclipse workspace

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-877?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III commented on FORGE-877: ------------------------------------------ Nm. I see. I got confused by the Crucible notes. > Addon sub-module is not imported into eclipse workspace > ------------------------------------------------------- > > Key: FORGE-877 > URL: https://issues.jboss.org/browse/FORGE-877 > Project: Forge … [View More]

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-877) Addon sub-module is not imported into eclipse workspace

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-877?page=com.atlassian.jira.plugin.... ] George Gastaldi commented on FORGE-877: --------------------------------------- The solution was the addition of -parent in the parent folder name, until we reach an agreement about what would be the best behavior > Addon sub-module is not imported into eclipse workspace > ------------------------------------------------------- > > Key: FORGE-877 > … [View More]

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-877) Addon sub-module is not imported into eclipse workspace

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-877?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III commented on FORGE-877: ------------------------------------------ This (adding "-parent") is fine. I personally think that using the Eclipse workspace as a default location *is* the only sane location. Where else would you default? The user's home dir? The desktop?... Nothing else makes sense, and this is something that can easily be changed via the directory selector that "new project" … [View More]

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-877) Addon sub-module is not imported into eclipse workspace

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-877?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III commented on FORGE-877: ------------------------------------------ Wait, what was the resolution of this? How was it solved? > Addon sub-module is not imported into eclipse workspace > ------------------------------------------------------- > > Key: FORGE-877 > URL: https://issues.jboss.org/browse/FORGE-877 > … [View More]

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-877) Addon sub-module is not imported into eclipse workspace

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-877?page=com.atlassian.jira.plugin.... ] George Gastaldi closed FORGE-877. --------------------------------- Resolution: Done > Addon sub-module is not imported into eclipse workspace > ------------------------------------------------------- > > Key: FORGE-877 > URL: https://issues.jboss.org/browse/FORGE-877 > Project: Forge > Issue Type: Bug > Affects Versions: 2.… [View More]

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-877) Addon sub-module is not imported into eclipse workspace

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-877?page=com.atlassian.jira.plugin.... ] George Gastaldi commented on FORGE-877: --------------------------------------- Transcript from a chat with [~maxandersen]: {quote} <maxandersen> gastaldi: btw. just saw your chat with fbricon about folders in workspaces…..just never import/create projects *inside* your workspace. its a bad practice in almost any scenario. gastaldi> maxandersen, cool, that would solve this importing problem <… [View More]gastaldi> which folder do you recommend besides the workspace folder ? <gastaldi> the user dir location ? <maxandersen> gastaldi: what is the importing problem actually ? i couldn't figure out what you were bumping into ? is it a committer of forge problem or a user of forge problem ? <maxandersen> gastaldi: where the user has his projects. <gastaldi> there is a forge addon that creates a multi-project structure <maxandersen> gastaldi: there unfortunately aren't any preference for it in eclipse -the closest is egit setting forwhere git projects will be defalt cloned to since egit also doees not like living "inside" workspace. <maxandersen> gastaldi: okey ? <gastaldi> I'm fine with that <maxandersen> that shouldn't be done inside a workspace anyway IMO <maxandersen> (if the multi project follows the eclipse anti—pattern of nested layout ;) <gastaldi> yes, it is nested <gastaldi> maxandersen, we're following the eclipse pattern of using the workspace as a default location for new projects <gastaldi> If you try to create a new Java project you'll see this behavior <maxandersen> gastaldi: noone uses that … it is not sane. <maxandersen> gastaldi: always annoyed me forge tooling did that - its just wrong for anyhing but toy projects {quote} > Addon sub-module is not imported into eclipse workspace > ------------------------------------------------------- > > Key: FORGE-877 > URL: https://issues.jboss.org/browse/FORGE-877 > Project: Forge > Issue Type: Bug > Affects Versions: 2.0.0.Alpha3 > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 2.0.0.Alpha4 > > > When a new forge addon is created using the "New Project" addon, and the option "Split project" is chosen, the addon submodule is not imported -- 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 [View Less]

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-877) Addon sub-module is not imported into eclipse workspace

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-877?page=com.atlassian.jira.plugin.... ] George Gastaldi reopened FORGE-877: ----------------------------------- > Addon sub-module is not imported into eclipse workspace > ------------------------------------------------------- > > Key: FORGE-877 > URL: https://issues.jboss.org/browse/FORGE-877 > Project: Forge > Issue Type: Bug > Affects Versions: 2.0.0.Alpha3 > … [View More]

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-877) Addon sub-module is not imported into eclipse workspace

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-877?page=com.atlassian.jira.plugin.... ] George Gastaldi closed FORGE-877. --------------------------------- Resolution: Done Fixed by renaming the parent folder meanwhile > Addon sub-module is not imported into eclipse workspace > ------------------------------------------------------- > > Key: FORGE-877 > URL: https://issues.jboss.org/browse/FORGE-877 > Project: … [View More]

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (FORGE-875) the `scaffold setup --scaffoldType faces; ` command. failed to create beans.xml

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-875?page=com.atlassian.jira.plugin.... ] Vineet Reynolds commented on FORGE-875: --------------------------------------- This was reproducible in JBoss Tools, but not in the Forge CLI version. Although beans.xml is created by the script in both cases (in JBT, the log output indicates so), the file is 'lost' in JBT and is no longer available in the filesystem. Needs some more investigation to triage the failing component. > the `… [View More]

11 years, 11 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues April 2013