December 2015 - forge-issues - Jboss List Archives

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

by Raghunath Kale (JIRA)

[ https://issues.jboss.org/browse/FORGE-874?page=com.atlassian.jira.plugin.... ] Raghunath Kale commented on FORGE-874: -------------------------------------- Good Day, I am getting same exception n linux from below highlighed code. Node applicationXmlNode = targetEar.get(ArchiveDescriptors.APPLICATION_XML.fullPath()); InputStream applicationXmlNodeInputStream = applicationXmlNode.getAsset().openStream(); {color:red} ApplicationDescriptor appDescriptor = Descriptors.importAs(ApplicationDescriptor.class).fromStream(applicationXmlNodeInputStream);{color} > 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 > Assignee: George Gastaldi > Priority: Minor > Fix For: 1.3.0.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 was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2570) Migrate artifact deployment to oss.sonatype.org

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2570?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-2570. ---------------------------------- Resolution: Done > Migrate artifact deployment to oss.sonatype.org > ----------------------------------------------- > > Key: FORGE-2570 > URL: https://issues.jboss.org/browse/FORGE-2570 > Project: Forge > Issue Type: Task > Affects Versions: 3.0.0.Alpha3 > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 3.0.0.Beta1 > > > Because sync with maven central takes too long in repository.jboss.org/nexus > Instructions: http://central.sonatype.org/pages/ossrh-guide.html > Example: https://github.com/wildfly-swarm/wildfly-swarm/blob/master/pom.xml#L313-L322 > {quote} > <gastaldi> bobmcw, I wonder if we are allowed to publish to oss.sonatype.org directly instead > <bobmcw> gastaldi: yes, we are > bobmcw does > <bobmcw> newton encourages it > <bobmcw> that was his response on thecore to sebersole 2-3 steaming-pile-of-poop threads ago > <bobmcw> I'm trying to push everyone to oss.sonatype now > <gastaldi> bobmcw, cool, I will use it then > <bobmcw> you'll need creds there and for them to setup the sync > <bobmcw> which means signing up for JIRA and filing one like https://issues.sonatype.org/browse/OSSRH-18308 > <bobmcw> plus a gpg key registered in a well-known keyserver, like mit.edu > <bobmcw> and sign your artifacts > <gastaldi> awesome > <bobmcw> https://github.com/wildfly-swarm/wildfly-swarm/blob/master/pom.xml#L325-L344 > <gastaldi> are these steps documented somewhere? > <bobmcw> we jam it into a plugin so that CI doesn't break when it deploys to a local repo > <gastaldi> smart > <bobmcw> http://central.sonatype.org/pages/ossrh-guide.html > <jbossbot> Title: OSSRH Guide > <bobmcw> there ya go! > <bobmcw> s/plugin/profile/ > <bobmcw> then deploy as usual (mvn release plugin or whatnot) and oss.sonatype.org has your staging repo. close/release per usual > <bobmcw> it's verifications at close will ensure you've met the requirements wrt signed artifacts and a registered key > <gastaldi> sweet > <bobmcw> when you release the staging repo, sync from oss.sonatype -> central happens within about 10 minutes > <bobmcw> it's glorious > <bobmcw> stil takes a few hours to show up in the search.maven.org index, but mvn can find them during a build > <gastaldi> perfect! > <gastaldi> bobmcw, thank you so much > <bobmcw> my pleasure! > <gastaldi> just created https://issues.sonatype.org/browse/OSSRH-19598 > <gastaldi> omg, they already resolved it > <bobmcw> Joel's always been zippyfast for anything we've needed > <bobmcw> there's a settings.xml change you do to keep up with your key passphrase, so you don't have to type it a lot. that doc should link to it, I think. > <bobmcw> or the maven-sign-plugin's docs > <gastaldi> bobmcw, I added the following properties to my pom.xml > <gastaldi> <jboss.releases.repo.url>https://oss.sonatype.org/service/local/staging/deploy/maven2/</jboss.releases.repo.url> > <gastaldi> <jboss.snapshots.repo.url>https://oss.sonatype.org/nexus/content/repositories/snapshots/</jboss.snapshots.repo.url> > <gastaldi> and maintained the same password I use in repository.jboss.org/nexus > <bobmcw> I've not tried that > <bobmcw> https://github.com/wildfly-swarm/wildfly-swarm/blob/master/pom.xml#L313-L322 > <bobmcw> but I dunno how jboss-parent works anymore, so those props may suffice > <gastaldi> gotcha > {quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2531) Using mixed versions of slf4j causes SLF4J to print to console a WARN about this

by christian posta (JIRA)

[ https://issues.jboss.org/browse/FORGE-2531?page=com.atlassian.jira.plugin... ] christian posta commented on FORGE-2531: ---------------------------------------- +1 exclude all references including slf4j-api. sample project that hangs when you don't (and its behavior fwiw) is here https://github.com/christian-posta/failing-logging-example > Using mixed versions of slf4j causes SLF4J to print to console a WARN about this > -------------------------------------------------------------------------------- > > Key: FORGE-2531 > URL: https://issues.jboss.org/browse/FORGE-2531 > Project: Forge > Issue Type: Bug > Affects Versions: 2.20.1.Final > Reporter: Claus Ibsen > Assignee: George Gastaldi > Priority: Minor > Fix For: 3.0.0.Beta1 > > > You can reproduce by installing the fabric8 devops addon > {code} > addon-install --coordinate io.fabric8.forge:devops,2.2.63 > ***SUCCESS*** Addon io.fabric8.forge:devops,2.2.63 was installed successfully. > [forge-distribution-2.20.1.Final]$ deSLF4J: Class path contains multiple SLF4J bindings. > SLF4J: Found binding in [jar:file:/opt/forge-distribution-2.20.1.Final/addons/org-jboss-forge-addon-maven-2-20-1-Final/slf4j-jdk14-1.7.5.jar!/org/slf4j/impl/StaticLoggerBinder.class] > SLF4J: Found binding in [jar:file:/opt/forge-distribution-2.20.1.Final/addons/org-jboss-forge-addon-database-tools-2-20-1-Final/slf4j-jdk14-1.5.8.jar!/org/slf4j/impl/StaticLoggerBinder.class] > SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation. > SLF4J: Actual binding is of type [org.slf4j.impl.JDK14LoggerFactory] > {code} > And then wait some seconds then you see all the slf4j logging. As you can see those 2 addons from forge itself are using mixed slf4j versions. > 1.7.5 and 1.5.8 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2570) Migrate artifact deployment to oss.sonatype.org

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2570?page=com.atlassian.jira.plugin... ] George Gastaldi commented on FORGE-2570: ---------------------------------------- Issue created in Sonatype: https://issues.sonatype.org/browse/OSSRH-19598 > Migrate artifact deployment to oss.sonatype.org > ----------------------------------------------- > > Key: FORGE-2570 > URL: https://issues.jboss.org/browse/FORGE-2570 > Project: Forge > Issue Type: Task > Affects Versions: 3.0.0.Alpha3 > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 3.0.0.Beta1 > > > Because sync with maven central takes too long in repository.jboss.org/nexus > Instructions: http://central.sonatype.org/pages/ossrh-guide.html > Example: https://github.com/wildfly-swarm/wildfly-swarm/blob/master/pom.xml#L313-L322 > {quote} > <gastaldi> bobmcw, I wonder if we are allowed to publish to oss.sonatype.org directly instead > <bobmcw> gastaldi: yes, we are > bobmcw does > <bobmcw> newton encourages it > <bobmcw> that was his response on thecore to sebersole 2-3 steaming-pile-of-poop threads ago > <bobmcw> I'm trying to push everyone to oss.sonatype now > <gastaldi> bobmcw, cool, I will use it then > <bobmcw> you'll need creds there and for them to setup the sync > <bobmcw> which means signing up for JIRA and filing one like https://issues.sonatype.org/browse/OSSRH-18308 > <bobmcw> plus a gpg key registered in a well-known keyserver, like mit.edu > <bobmcw> and sign your artifacts > <gastaldi> awesome > <bobmcw> https://github.com/wildfly-swarm/wildfly-swarm/blob/master/pom.xml#L325-L344 > <gastaldi> are these steps documented somewhere? > <bobmcw> we jam it into a plugin so that CI doesn't break when it deploys to a local repo > <gastaldi> smart > <bobmcw> http://central.sonatype.org/pages/ossrh-guide.html > <jbossbot> Title: OSSRH Guide > <bobmcw> there ya go! > <bobmcw> s/plugin/profile/ > <bobmcw> then deploy as usual (mvn release plugin or whatnot) and oss.sonatype.org has your staging repo. close/release per usual > <bobmcw> it's verifications at close will ensure you've met the requirements wrt signed artifacts and a registered key > <gastaldi> sweet > <bobmcw> when you release the staging repo, sync from oss.sonatype -> central happens within about 10 minutes > <bobmcw> it's glorious > <bobmcw> stil takes a few hours to show up in the search.maven.org index, but mvn can find them during a build > <gastaldi> perfect! > <gastaldi> bobmcw, thank you so much > <bobmcw> my pleasure! > <gastaldi> just created https://issues.sonatype.org/browse/OSSRH-19598 > <gastaldi> omg, they already resolved it > <bobmcw> Joel's always been zippyfast for anything we've needed > <bobmcw> there's a settings.xml change you do to keep up with your key passphrase, so you don't have to type it a lot. that doc should link to it, I think. > <bobmcw> or the maven-sign-plugin's docs > <gastaldi> bobmcw, I added the following properties to my pom.xml > <gastaldi> <jboss.releases.repo.url>https://oss.sonatype.org/service/local/staging/deploy/maven2/</jboss.releases.repo.url> > <gastaldi> <jboss.snapshots.repo.url>https://oss.sonatype.org/nexus/content/repositories/snapshots/</jboss.snapshots.repo.url> > <gastaldi> and maintained the same password I use in repository.jboss.org/nexus > <bobmcw> I've not tried that > <bobmcw> https://github.com/wildfly-swarm/wildfly-swarm/blob/master/pom.xml#L313-L322 > <bobmcw> but I dunno how jboss-parent works anymore, so those props may suffice > <gastaldi> gotcha > {quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2570) Migrate artifact deployment to oss.sonatype.org

by George Gastaldi (JIRA)

George Gastaldi created FORGE-2570: -------------------------------------- Summary: Migrate artifact deployment to oss.sonatype.org Key: FORGE-2570 URL: https://issues.jboss.org/browse/FORGE-2570 Project: Forge Issue Type: Task Affects Versions: 3.0.0.Alpha3 Reporter: George Gastaldi Assignee: George Gastaldi Fix For: 3.0.0.Beta1 Because sync with maven central takes too long in repository.jboss.org/nexus Instructions: http://central.sonatype.org/pages/ossrh-guide.html Example: https://github.com/wildfly-swarm/wildfly-swarm/blob/master/pom.xml#L313-L322 {quote} <gastaldi> bobmcw, I wonder if we are allowed to publish to oss.sonatype.org directly instead <bobmcw> gastaldi: yes, we are bobmcw does <bobmcw> newton encourages it <bobmcw> that was his response on thecore to sebersole 2-3 steaming-pile-of-poop threads ago <bobmcw> I'm trying to push everyone to oss.sonatype now <gastaldi> bobmcw, cool, I will use it then <bobmcw> you'll need creds there and for them to setup the sync <bobmcw> which means signing up for JIRA and filing one like https://issues.sonatype.org/browse/OSSRH-18308 <bobmcw> plus a gpg key registered in a well-known keyserver, like mit.edu <bobmcw> and sign your artifacts <gastaldi> awesome <bobmcw> https://github.com/wildfly-swarm/wildfly-swarm/blob/master/pom.xml#L325-L344 <gastaldi> are these steps documented somewhere? <bobmcw> we jam it into a plugin so that CI doesn't break when it deploys to a local repo <gastaldi> smart <bobmcw> http://central.sonatype.org/pages/ossrh-guide.html <jbossbot> Title: OSSRH Guide <bobmcw> there ya go! <bobmcw> s/plugin/profile/ <bobmcw> then deploy as usual (mvn release plugin or whatnot) and oss.sonatype.org has your staging repo. close/release per usual <bobmcw> it's verifications at close will ensure you've met the requirements wrt signed artifacts and a registered key <gastaldi> sweet <bobmcw> when you release the staging repo, sync from oss.sonatype -> central happens within about 10 minutes <bobmcw> it's glorious <bobmcw> stil takes a few hours to show up in the search.maven.org index, but mvn can find them during a build <gastaldi> perfect! <gastaldi> bobmcw, thank you so much <bobmcw> my pleasure! <gastaldi> just created https://issues.sonatype.org/browse/OSSRH-19598 <gastaldi> omg, they already resolved it <bobmcw> Joel's always been zippyfast for anything we've needed <bobmcw> there's a settings.xml change you do to keep up with your key passphrase, so you don't have to type it a lot. that doc should link to it, I think. <bobmcw> or the maven-sign-plugin's docs <gastaldi> bobmcw, I added the following properties to my pom.xml <gastaldi> <jboss.releases.repo.url>https://oss.sonatype.org/service/local/staging/deploy/maven2/</jboss.releases.repo.url> <gastaldi> <jboss.snapshots.repo.url>https://oss.sonatype.org/nexus/content/repositories/snapshots/</jboss.snapshots.repo.url> <gastaldi> and maintained the same password I use in repository.jboss.org/nexus <bobmcw> I've not tried that <bobmcw> https://github.com/wildfly-swarm/wildfly-swarm/blob/master/pom.xml#L313-L322 <bobmcw> but I dunno how jboss-parent works anymore, so those props may suffice <gastaldi> gotcha {quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2566) Provider apple.applescript.AppleScriptEngineFactory not found

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2566?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-2566. ---------------------------------- Resolution: Done > Provider apple.applescript.AppleScriptEngineFactory not found > ------------------------------------------------------------- > > Key: FORGE-2566 > URL: https://issues.jboss.org/browse/FORGE-2566 > Project: Forge > Issue Type: Bug > Components: Script, UI - Shell > Affects Versions: 3.0.0.Alpha3 > Environment: ceposta@postamac(target (master)) $ java -version > java version "1.8.0_65" > Java(TM) SE Runtime Environment (build 1.8.0_65-b17) > Java HotSpot(TM) 64-Bit Server VM (build 25.65-b01, mixed mode) > on Mac OS X > Reporter: christian posta > Assignee: George Gastaldi > Fix For: 3.0.0.Beta1 > > > trying to run any command for the first time using Forge 2.x or 3.x on Mac OSX with JDK 8 I get this: > {code} > [forge-distribution-3.0.0-SNAPSHOT]$ addScriptEngineManager providers.next(): javax.script.ScriptEngineFactory: Provider apple.applescript.AppleScriptEngineFactory not found > ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory: Provider apple.applescript.AppleScriptEngineFactory not found > ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory: Provider apple.applescript.AppleScriptEngineFactory not found > ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory: Provider apple.applescript.AppleScriptEngineFactory not found > ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory: Provider apple.applescript.AppleScriptEngineFactory not found > ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory: Provider apple.applescript.AppleScriptEngineFactory not found > ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory: Provider apple.applescript.AppleScriptEngineFactory not found > ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory: Provider apple.applescript.AppleScriptEngineFactory not found > ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory: Provider apple.applescript.AppleScriptEngineFactory not found > ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory: Provider apple.applescript.AppleScriptEngineFactory not found > ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory: Provider apple.applescript.AppleScriptEngineFactory not found > ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory: Provider apple.applescript.AppleScriptEngineFactory not found > ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory: Provider apple.applescript.AppleScriptEngineFactory not found > ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory: Provider apple.applescript.AppleScriptEngineFactory not found > ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory: Provider apple.applescript.AppleScriptEngineFactory not found > ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory: Provider apple.applescript.AppleScriptEngineFactory not found > ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory: Provider apple.applescript.AppleScriptEngineFactory not found > ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory: Provider apple.applescript.AppleScriptEngineFactory not found > ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory: Provider apple.applescript.AppleScriptEngineFactory not found > ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory: Provider apple.applescript.AppleScriptEngineFactory not found > ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory: Provider apple.applescript.AppleScriptEngineFactory not found > ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory: Provider apple.applescript.AppleScriptEngineFactory not found > ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory: Provider apple.applescript.AppleScriptEngineFactory not found > ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory: Provider apple.applescript.AppleScriptEngineFactory not found > ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory: Provider apple.applescript.AppleScriptEngineFactory not found > ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory: Provider apple.applescript.AppleScriptEngineFactory not found > ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory: Provider apple.applescript.AppleScriptEngineFactory not found > ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory: Provider apple.applescript.AppleScriptEngineFactory not found > ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory: Provider apple.applescript.AppleScriptEngineFactory not found > ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory: Provider apple.applescript.AppleScriptEngineFactory not found > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2569) Upgrade to Furnace 2.22.10.Final

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2569?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-2569. ---------------------------------- Resolution: Done > Upgrade to Furnace 2.22.10.Final > -------------------------------- > > Key: FORGE-2569 > URL: https://issues.jboss.org/browse/FORGE-2569 > Project: Forge > Issue Type: Component Upgrade > Components: Furnace (Container) > Affects Versions: 3.0.0.Alpha3 > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 3.0.0.Beta1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2569) Upgrade to Furnace 2.22.10.Final

by George Gastaldi (JIRA)

George Gastaldi created FORGE-2569: -------------------------------------- Summary: Upgrade to Furnace 2.22.10.Final Key: FORGE-2569 URL: https://issues.jboss.org/browse/FORGE-2569 Project: Forge Issue Type: Component Upgrade Components: Furnace (Container) Affects Versions: 3.0.0.Alpha3 Reporter: George Gastaldi Assignee: George Gastaldi Fix For: 3.0.0.Beta1 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FURNACE-99) furnance-demo - do not work and is not up to date

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FURNACE-99?page=com.atlassian.jira.plugin... ] George Gastaldi closed FURNACE-99. ---------------------------------- Fix Version/s: 2.22.10.Final Assignee: George Gastaldi Resolution: Done > furnance-demo - do not work and is not up to date > ------------------------------------------------- > > Key: FURNACE-99 > URL: https://issues.jboss.org/browse/FURNACE-99 > Project: Forge: Furnace > Issue Type: Bug > Reporter: Claus Ibsen > Assignee: George Gastaldi > Fix For: 2.22.10.Final > > > This repo is out of date > https://github.com/forge/furnace-demo > And it does not work if you use latest furnance 2.22.9.Final version with forge 2.20.1.Final > You get a class cast exception such as > {code} > Dec 19, 2015 12:28:36 PM org.jboss.forge.furnace.impl.FurnaceImpl start > INFO: Furnace [2.22.9.Final] starting. > Dec 19, 2015 12:28:36 PM org.jboss.forge.furnace.impl.addons.AddonLoader loadAddon > WARNING: Addon [io.fabric8.forge:camel,2.2.81-SNAPSHOT +NEW] has [8] missing dependencies: [[MISSING: org.jboss.forge.addon:ui,2.20.1.Final: [IMPORTED] [REQUIRED]], [MISSING: org.jboss.forge.addon:rest-client,2.20.1.Final: [IMPORTED] [REQUIRED]], [MISSING: org.jboss.forge.furnace.container:cdi,2.22.7.Final: [IMPORTED] [REQUIRED]], [MISSING: org.jboss.forge.addon:maven,2.20.1.Final: [IMPORTED] [REQUIRED]], [MISSING: org.jboss.forge.addon:parser-java,2.20.1.Final: [IMPORTED] [REQUIRED]], [MISSING: org.jboss.forge.addon:projects,2.20.1.Final: [IMPORTED] [REQUIRED]], [MISSING: org.jboss.forge.addon:parser-xml,2.20.1.Final: [IMPORTED] [REQUIRED]], [MISSING: org.jboss.forge.addon:templates,2.20.1.Final: [IMPORTED] [REQUIRED]]] and will be not be loaded until all required dependencies are available. > Dec 19, 2015 12:28:36 PM org.jboss.forge.furnace.impl.addons.AddonLoader loadAddon > WARNING: Addon [io.fabric8.forge:camel,2.2.81-SNAPSHOT +NEW] has [8] missing dependencies: [[MISSING: org.jboss.forge.addon:ui,2.20.1.Final: [IMPORTED] [REQUIRED]], [MISSING: org.jboss.forge.addon:rest-client,2.20.1.Final: [IMPORTED] [REQUIRED]], [MISSING: org.jboss.forge.furnace.container:cdi,2.22.7.Final: [IMPORTED] [REQUIRED]], [MISSING: org.jboss.forge.addon:maven,2.20.1.Final: [IMPORTED] [REQUIRED]], [MISSING: org.jboss.forge.addon:parser-java,2.20.1.Final: [IMPORTED] [REQUIRED]], [MISSING: org.jboss.forge.addon:projects,2.20.1.Final: [IMPORTED] [REQUIRED]], [MISSING: org.jboss.forge.addon:parser-xml,2.20.1.Final: [IMPORTED] [REQUIRED]], [MISSING: org.jboss.forge.addon:templates,2.20.1.Final: [IMPORTED] [REQUIRED]]] and will be not be loaded until all required dependencies are available. > Exception in thread "main" java.lang.ClassCastException: org.jboss.forge.furnace.versions.SingleVersion cannot be cast to org.jboss.forge.furnace.versions.Version > at org.jboss.forge.furnace.versions.SingleVersion.compareTo(SingleVersion.java:37) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback$2.call(ClassLoaderAdapterCallback.java:123) > at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42) > at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.invoke(ClassLoaderAdapterCallback.java:96) > at org.jboss.forge.furnace.versions.Version_$$_javassist_007f9a16-5bd3-4c49-8a64-f19be424f395.compareTo(Version_$$_javassist_007f9a16-5bd3-4c49-8a64-f19be424f395.java) > at org.jboss.forge.furnace.manager.impl.AddonManagerImpl.createRequest(AddonManagerImpl.java:202) > at org.jboss.forge.furnace.manager.impl.AddonManagerImpl.install(AddonManagerImpl.java:91) > at org.jboss.forge.furnace.manager.impl.AddonManagerImpl.install(AddonManagerImpl.java:78) > at io.fabric8.forge.camel.maven.DeleteMe.execute(DeleteMe.java:57) > at io.fabric8.forge.camel.maven.DeleteMe.main(DeleteMe.java:44) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at com.intellij.rt.execution.application.AppMain.main(AppMain.java:144) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2568) Upgrade to Roaster 2.17.4.Final

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2568?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-2568. ---------------------------------- Resolution: Done > Upgrade to Roaster 2.17.4.Final > ------------------------------- > > Key: FORGE-2568 > URL: https://issues.jboss.org/browse/FORGE-2568 > Project: Forge > Issue Type: Component Upgrade > Components: Parsers / File Manipulation > Affects Versions: 3.0.0.Alpha3 > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 3.0.0.Beta1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues December 2015