April 2012 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-464) Create Debian/Ubuntu package for Forge

by Dan Allen (JIRA)

Dan Allen created FORGE-464: ------------------------------- Summary: Create Debian/Ubuntu package for Forge Key: FORGE-464 URL: https://issues.jboss.org/browse/FORGE-464 Project: Forge Issue Type: Feature Request Components: Forge Build Affects Versions: 1.0.0.Beta5 Reporter: Dan Allen This issue should act as an umbrella for this project. Use related issues to track the steps. Creating and publishing Forge packages for Debian & Ubuntu would really help boost adoption of Forge, IMO. Telling someone to download an unzip seems simple enough, but there's just something even more elegant about: sudo apt-get install jboss-forge (no sudo if you're hip enough, one of those GUIs if your glitzy enough) Debian provides guidelines for new package maintainers [1]. [1] http://www.debian.org/doc/manuals/maint-guide/ -- 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

11 years, 6 months

4
6
0 / 0

[JBoss JIRA] (FORGE-518) projectFactory.createProjet doesn't work out of embeded plugins

by Guillaume Gustin (JIRA)

Guillaume Gustin created FORGE-518: -------------------------------------- Summary: projectFactory.createProjet doesn't work out of embeded plugins Key: FORGE-518 URL: https://issues.jboss.org/browse/FORGE-518 Project: Forge Issue Type: Bug Components: Builtin Plugins, Forge Build Affects Versions: 1.0.0.Final Environment: Windows XP Professional Service Pack 3 - 32 bits Reporter: Guillaume Gustin Priority: Blocker I want to create a new plugin which allow to create a solution (set of projects) based on a specific solution model. But when the forge execute the project building code "projectFactory.createProject(targetProjectDir, DependencyFacet.class, MetadataFacet.class, JavaSourceFacet.class, ResourceFacet.class)" i receive the exception "org.jboss.forge.project.ProjectModelException" with the message "Could not create Maven project building request" When i fire my new plugin, my forge promps is "[no project] myTempdir $ ", I have the same exception when I copy the "new-project plugin" as "new-new-project plugin". -- 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

11 years, 6 months

4
15
0 / 0

[JBoss JIRA] (FORGE-554) Tab AutoCompletion in forge ignores already typed options

by George Gastaldi (JIRA)

George Gastaldi created FORGE-554: ------------------------------------- Summary: Tab AutoCompletion in forge ignores already typed options Key: FORGE-554 URL: https://issues.jboss.org/browse/FORGE-554 Project: Forge Issue Type: Bug Reporter: George Gastaldi Inside a project, when you "cd" and press <TAB> to navigate between nested folders, the prompt resets to "cd" only, losing the folders previously selected when typing. -- 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

11 years, 6 months

4
8
0 / 0

[JBoss JIRA] (FORGE-553) Forge Console does not display special characters

by George Gastaldi (JIRA)

George Gastaldi created FORGE-553: ------------------------------------- Summary: Forge Console does not display special characters Key: FORGE-553 URL: https://issues.jboss.org/browse/FORGE-553 Project: Forge Issue Type: Bug Reporter: George Gastaldi When you try typing accented characters, like áéíóú, they are erroneously displayed in Forge console. There must be a way to set the encoding or leave as default -- 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

11 years, 6 months

4
13
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

11 years, 6 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

11 years, 6 months

6
41
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-321) FSH parser interprets '=' as an MVEL command, cannot be used in normal commands without "quoting it"

by Lincoln Baxter III (JIRA)

FSH parser interprets '=' as an MVEL command, cannot be used in normal commands without "quoting it" ---------------------------------------------------------------------------------------------------- Key: SEAMFORGE-321 URL: https://issues.jboss.org/browse/SEAMFORGE-321 Project: Seam Forge Issue Type: Bug Components: Forge Scripting Language Affects Versions: 1.0.0.Beta2 Reporter: Lincoln Baxter III Assignee: Mike Brock Fix For: 1.0.0.Final {code}$ alias foo=echo foo{code} causes MVEL exception "alias cannot be resolved." works with quotes, however {code}$ alias "foo=echo foo"{code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

2
14
0 / 0

[JBoss JIRA] (FORGE-424) JavaParser does not understand wildcard imports like "javax.persistence.*"

by Lincoln Baxter III (Created) (JIRA)

JavaParser does not understand wildcard imports like "javax.persistence.*" -------------------------------------------------------------------------- Key: FORGE-424 URL: https://issues.jboss.org/browse/FORGE-424 Project: Forge Issue Type: Bug Components: Parsers / File Manipulation Affects Versions: 1.0.0.Beta5 Reporter: Lincoln Baxter III Fix For: 1.0.0.Final The JavaParser Annotation.getQualifiedName() will return "Column" instead of "javax.persistence.Column" for the following example class scenario. It should be able to understand the wildcard, given the proper metadata: {code}package demo.entities; import javax.persistence.*; @Entity public class Contact implements java.io.Serializable { @Id private @GeneratedValue(strategy = GenerationType.AUTO) @Column(name = "id", updatable = false, nullable = false) Long id = null; @Version private @Column(name = "version") int version = 0; public Long getId() { return this.id; } public void setId(final Long id) { this.id = id; } public int getVersion() { return this.version; } public void setVersion(final int version) { this.version = version; } @Override public boolean equals(Object that) { if (this == that) { return true; } if (that == null) { return false; } if (getClass() != that.getClass()) { return false; } if (id != null) { return id.equals(((Contact) that).id); } return super.equals(that); } @Override public int hashCode() { if (id != null) { return id.hashCode(); } return super.hashCode(); } private String name; public String getName() { return this.name; } public void setName(final String name) { this.name = name; } public String toString() { return "" + name; } }{code} -- 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

11 years, 7 months

5
11
0 / 0

[JBoss JIRA] (FORGE-430) Fix MavenCoreFacetImpl getPom()

by Max Schwaab (JIRA)

Max Schwaab created FORGE-430: --------------------------------- Summary: Fix MavenCoreFacetImpl getPom() Key: FORGE-430 URL: https://issues.jboss.org/browse/FORGE-430 Project: Forge Issue Type: Bug Affects Versions: 1.0.0.Beta5 Environment: Windows 7, Desktop PC Reporter: Max Schwaab Priority: Minor Fix For: Future Please have a look at org.jboss.forge.maven.facets.MavenCoreFacetImpl in the forge-project-model-maven project. The getPom() method reads the pom directly from the file resource. This results in a warning when using maven properties for dependency versions, e.g. when you try to install a plugin via the source-plugin command (***WARNING*** Could not resolve dependency [org.some:dependency:jar::${some.version}]) The plugin works after installation and I don't know if its important to resolve this issue, but in the code is a "//FIXME"-remark too. The same may be relevant for setPOM(final Model pom) too. {code:title=MavenCoreFacetImpl getPom()} @Override public Model getPOM() { try { Model result = new Model(); // FIXME this should/can-not use the Maven Native file writer if we are going to abstract file APIs MavenXpp3Reader reader = new MavenXpp3Reader(); FileInputStream stream = new FileInputStream(getPOMFile().getUnderlyingResourceObject()); if (stream.available() > 0) { result = reader.read(stream); } stream.close(); result.setPomFile(getPOMFile().getUnderlyingResourceObject()); return result; } catch (IOException e) { throw new ProjectModelException("Could not open POM file: " + getPOMFile(), e); } catch (XmlPullParserException e) { throw new ProjectModelException("Could not parse POM file: " + getPOMFile(), e); } } {code} Example for my plugins pom.xml {code:xml} <?xml version="1.0" encoding="UTF-8"?> <project xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd" xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> . . . <properties> <some.version>1.0</some.version> </properties> <dependencies> . . . <dependency> <groupId>org.some</groupId> <artifactId>dependency</artifactId> <version>${some.version}</version> </dependency> . . . </dependencies> <repositories> . . . <repository> <id>repository.some</id> <name>Some Repository for Maven</name> <url>http://some.repo.url</url> </repository> . . . </repositories> . . . </project> {code} Best regards Max -- 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

11 years, 7 months

2
9
0 / 0

[JBoss JIRA] (FORGE-367) Java Parser needs to support wildcard (.*) imports.

by Paul Bakker (Created) (JIRA)

Java Parser needs to support wildcard (.*) imports. --------------------------------------------------- Key: FORGE-367 URL: https://issues.jboss.org/browse/FORGE-367 Project: Forge Issue Type: Enhancement Reporter: Paul Bakker Assignee: Lincoln Baxter III It is now impossible to do this: {code} JavaClass testClass... testClass.addImport("org.junit.Assert.*").setStatic(true); {code} This is mainly required for static imports. -- 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

11 years, 7 months

5
9
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues April 2012