November 2012 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-670) Redirect command output to a file

by George Gastaldi (JIRA)

George Gastaldi created FORGE-670: ------------------------------------- Summary: Redirect command output to a file Key: FORGE-670 URL: https://issues.jboss.org/browse/FORGE-670 Project: Forge Issue Type: Feature Request Components: Shell Reporter: George Gastaldi It should be possible to redirect output in shell to a file, so that the following command should work: {code} cat http://www.google.com > testme.txt {code} To append to the end of the file, use: {code} cat http://www.google.com >> testme.txt {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

12 years, 2 months

3
5
0 / 0

[JBoss JIRA] (FORGE-679) Add a step explaining how to import and use the Forge code formatter

by George Gastaldi (JIRA)

George Gastaldi created FORGE-679: ------------------------------------- Summary: Add a step explaining how to import and use the Forge code formatter Key: FORGE-679 URL: https://issues.jboss.org/browse/FORGE-679 Project: Forge Issue Type: Task Components: Website Reporter: George Gastaldi Fix For: 1.1.0.Final In http://forge.jboss.org/docs/get_involved/contribute.html there is a step missing about using the Forge code formatter in Eclipse -- 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

12 years, 2 months

2
3
0 / 0

[JBoss JIRA] (FORGE-693) Need an auto-update feature for plugins

by George Gastaldi (JIRA)

George Gastaldi created FORGE-693: ------------------------------------- Summary: Need an auto-update feature for plugins Key: FORGE-693 URL: https://issues.jboss.org/browse/FORGE-693 Project: Forge Issue Type: Feature Request Reporter: George Gastaldi FORGE-217 auto-updates the core and the core plugins. There should be a way to update the current installed plugins. Depending on the time taken to check, this could be done in the Forge startup. -- 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

12 years, 2 months

2
3
0 / 0

[JBoss JIRA] (FORGE-699) create a plugin for WildcardImportResolver

by fiorenzo pizza (JIRA)

fiorenzo pizza created FORGE-699: ------------------------------------ Summary: create a plugin for WildcardImportResolver Key: FORGE-699 URL: https://issues.jboss.org/browse/FORGE-699 Project: Forge Issue Type: Story Components: Parsers / File Manipulation Affects Versions: 1.1.1.Final Reporter: fiorenzo pizza Assignee: fiorenzo pizza Fix For: 1.1.2.Final general notes We need to create some WildcardImportResolver (Responsible for providing additional import resolution functionality for situations where classes have referenced a package or wild-card import) summary: - when start creation of index --> new-project - when update the index --> re-open project | add|remove plugins to the project | add|remove maven dependencies | add|remove new class inside forge project - where save the index --> always - how information to save for future search --> className, jarName (null if the class is in the project), packageName, absoluteClassName - how search inside the index --> (ram hashmap? ram db?) - how generate new entry for the index --> cdi event general considerations 1) when forge create a new-project we should create some structure to add all classes used referenced by project 2) we need to add all classes required from some plugin (persistence|scaffolding..) 2) we need to add all classes inside maven dependencies 3) we need to add all classes created in the project 4) we need remove all deleted classes 5) we need to remove all classes inside dependecies removed 6) we need to update the index files, when forge project is reopen (the user could modify the project out of forge) problems 1) with a lot of jars, the indexing process should be slow!! 2) how synchronize the access to index 3) how we should synchronize of index update? requirements 1) we need some fast library to extract classes from jar files 2) we should use cdi event to start a single jar indexing HOW CREATE INDEX FROM JAR: possibile libraries: jandex, tattletale, jarindexer FIRST CANDIDATE: JANDEX i started to hack jandex code, because jandex is very fast. Jandex opens the jar files using java jar utilities: JarFile jar = new JarFile(jarFile); and for every class generate a ClassInfo object: ClassInfo info = indexer.index(jar.getInputStream(entry)); For my test, i removed some methods inside jandex: we don't care about annotations inside classes. Also i removed the generation of file index. questions: 1) why don't use H2, the Java SQL database, for memorize all informations about classes? How memorize for a single class: 1) classname, jar name (with version), package name, complete name -- 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

12 years, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-282) Decouple Forge from System.in

by George Gastaldi (JIRA)

Decouple Forge from System.in ----------------------------- Key: SEAMFORGE-282 URL: https://issues.jboss.org/browse/SEAMFORGE-282 Project: Seam Forge Issue Type: Feature Request Reporter: George Gastaldi One of my to-do items is to create a web application using jQuery Terminal plugin (http://terminal.jcubic.pl) or Primefaces Terminal component (http://www.primefaces.org/showcase-labs/ui/terminal.jsf). For this to happen, Forge input should be decoupled from System.in, so that it can accept input from any source. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
2
0 / 0

[JBoss JIRA] (FORGE-539) Connection refused: **ERROR** [forge install-plugin] Connection to ... behind a proxy

by Esteve Aviles (JIRA)

Esteve Aviles created FORGE-539: ----------------------------------- Summary: Connection refused: **ERROR** [forge install-plugin] Connection to ... behind a proxy Key: FORGE-539 URL: https://issues.jboss.org/browse/FORGE-539 Project: Forge Issue Type: Bug Components: Shell Affects Versions: 1.0.2.Final Environment: windows7 forge 1.0.2 Reporter: Esteve Aviles Priority: Minor Hi, I am getting this error when using forge behind a proxy. I tried FORGE-421 Proxy support, but with no success. [seam3-test] seam3-test $ forge install-plugin arquillian Connecting to remote repository [https://raw.github.com/forge/plugin-repository/master/repository.yaml]... ***ERROR*** [forge install-plugin] Connection to https://raw.github.com refused org.jboss.forge.shell.exceptions.CommandExecutionException: Connection to https://raw.github.com refused at org.jboss.forge.shell.command.Execution.perform(Execution.java:153) at org.jboss.forge.shell.command.fshparser.FSHRuntime.run(FSHRuntime.java:125) at org.jboss.forge.shell.command.fshparser.FSHRuntime.run(FSHRuntime.java:63) at org.jboss.forge.shell.ShellImpl$ExecutorThread.run(ShellImpl.java:829) at org.jboss.forge.shell.ShellImpl.execute(ShellImpl.java:852) at org.jboss.forge.shell.ShellImpl.doShell(ShellImpl.java:642) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) 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.doShell(ShellImpl$Proxy$_$$_WeldClientProxy.java) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) 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:139) at java.lang.Thread.run(Unknown Source) Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.jboss.forge.shell.command.Execution.perform(Execution.java:149) ... 31 more Caused by: org.apache.http.conn.HttpHostConnectException: Connection to https://raw.github.com refused at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:127) at org.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoolEntry.java:147) at org.apache.http.impl.conn.AbstractPooledConnAdapter.open(AbstractPooledConnAdapter.java:108) at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:415) at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:641) at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:576) at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:554) at org.jboss.forge.shell.util.PluginUtil.findPlugin(PluginUtil.java:88) at org.jboss.forge.shell.plugins.builtin.ForgePlugin.installFromIndex(ForgePlugin.java:236) ... 36 more Caused by: java.net.ConnectException: Connection timed out: connect at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(Unknown Source) at java.net.PlainSocketImpl.connectToAddress(Unknown Source) at java.net.PlainSocketImpl.connect(Unknown Source) at java.net.SocksSocketImpl.connect(Unknown Source) at java.net.Socket.connect(Unknown Source) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.connect(Unknown Source) at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:333) at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:123) ... 44 more Thanks in advance -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

6
41
0 / 0

[JBoss JIRA] (FORGE-686) JavaSourceFacet eventualls returns an invalid base package

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-686?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-686: ---------------------------------- Status: Closed (was: Pull Request Sent) Assignee: George Gastaldi Resolution: Done Fixed > JavaSourceFacet eventualls returns an invalid base package > ---------------------------------------------------------- > > Key: FORGE-686 > URL: https://issues.jboss.org/browse/FORGE-686 > Project: Forge > Issue Type: Bug > Components: Resources API > Affects Versions: 1.0.5.Final > Reporter: Andre Dietisheim > Assignee: George Gastaldi > Fix For: 1.1.2.Final > > -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-686) JavaSourceFacet eventualls returns an invalid base package

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-686?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-686: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/forge/core/pull/238 > JavaSourceFacet eventualls returns an invalid base package > ---------------------------------------------------------- > > Key: FORGE-686 > URL: https://issues.jboss.org/browse/FORGE-686 > Project: Forge > Issue Type: Bug > Components: Resources API > Affects Versions: 1.0.5.Final > Reporter: Andre Dietisheim > Fix For: 1.1.2.Final > > -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-686) JavaSourceFacet eventualls returns an invalid base package

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-686?page=com.atlassian.jira.plugin.... ] George Gastaldi commented on FORGE-686: --------------------------------------- If you don't specify a default package when executing new-project, it leads to a default of _com.example.infinispan-demo_, which is not a valid package. We should fix that in the NewProjectPlugin class > JavaSourceFacet eventualls returns an invalid base package > ---------------------------------------------------------- > > Key: FORGE-686 > URL: https://issues.jboss.org/browse/FORGE-686 > Project: Forge > Issue Type: Bug > Components: Resources API > Affects Versions: 1.0.5.Final > Reporter: Andre Dietisheim > Fix For: 1.1.2.Final > > -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-32) FSHParser is too agressive (destroys command input)

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-32?page=com.atlassian.jira.plugin.s... ] George Gastaldi closed FORGE-32. -------------------------------- Fix Version/s: (was: 1.1.2.Final) Resolution: Deferred We couldn't find a viable way of fixing this in 1.x, since the shell always considers a valid MVEL2 expression. We should change that in 2.0 > FSHParser is too agressive (destroys command input) > --------------------------------------------------- > > Key: FORGE-32 > URL: https://issues.jboss.org/browse/FORGE-32 > Project: Forge > Issue Type: Bug > Components: Shell > Affects Versions: 1.0.0.Beta2 > Reporter: Lincoln Baxter III > Priority: Critical > > FSHParser is breaking up statements that clearly are not scripts: > [example] Customer.java $ prettyfaces mapping --resource /scaffold/customer/view.xhtml --pattern /customer/#{id} --id viewCustomer > ***INFO*** The command [mapping] takes [0] unnamed argument(s), but found [1]. > ***INFO*** Swallowed unknown token [{] for command [mapping]. > ***INFO*** Swallowed unknown token [id] for command [mapping]. > ***INFO*** Swallowed unknown token [}] for command [mapping]. > ... etc > [example] Customer.java $ -- 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

12 years, 2 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues November 2012