January 2012 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-385) Current directory is poor default for new-project location when existing project is detected

by Dan Allen (Created) (JIRA)

Current directory is poor default for new-project location when existing project is detected -------------------------------------------------------------------------------------------- Key: FORGE-385 URL: https://issues.jboss.org/browse/FORGE-385 Project: Forge Issue Type: Enhancement Components: Builtin Plugins Affects Versions: 1.0.0.Beta3 Reporter: Dan Allen Assignee: Lincoln Baxter III Priority: Minor When creating a new project using the new-project command, forge will offer the current directory as the target location if a project with the same name is found. {code} $ new-project --named example --topLevelPackage org.example ***ERROR*** [/home/dallen/example] already contains a project; please use a different folder. Where would you like to create the project? [Press ENTER to use the current directory: dallen] {code} This default is a recipe for disaster. If there is a project in the way, then using the current directory puts that project *in* the project being created. Additionally, if the current directory is $HOME, then the project will get overlaid in a directory which has many other files and directories. A better default is to append a number to the end of the project name. For example: {code} $ new-project --named example --topLevelPackage org.example ***ERROR*** [/home/dallen/example] already contains a project; please use a different folder. Where would you like to create the project? [Press ENTER to use an alternative directory: example2] {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, 5 months

3
6
0 / 0

[JBoss JIRA] (FORGE-463) Create Fedora package for Forge

by Dan Allen (JIRA)

Dan Allen created FORGE-463: ------------------------------- Summary: Create Fedora package for Forge Key: FORGE-463 URL: https://issues.jboss.org/browse/FORGE-463 Project: Forge Issue Type: Feature Request Components: Forge Build Affects Versions: 1.0.0.Beta5 Reporter: Dan Allen This is an umbrella issue for creating a Fedora package for Forge. Track steps using additional issues. Creating and publishing Forge packages for Fedora 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 yum install jboss-forge (no sudo if you're hip enough, one of those GUIs if your glitzy enough) I discovered that Fedora is trying to make package development easier than ever for Java developers. They've created a plugin for Eclipse [1] that walks you through creating a package, starting from git clone all the way to publish to Bodhi [2] (think of it like Nexus for Fedora, sort of). This effort relates to, and my help drive, the JBoss AS 7 on Fedora initiative [3]. [1] http://fedoraproject.org/wiki/Fedora_Packager_For_Eclipse_User_Guide [2] http://fedoraproject.org/wiki/Bodhi [3] http://fedoraproject.org/wiki/JBossAS7 -- 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, 5 months

6
13
0 / 0

[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, 5 months

4
6
0 / 0

[JBoss JIRA] (FORGE-451) Edit screen missing default selection on drop downs

by Pete Muir (JIRA)

Pete Muir created FORGE-451: ------------------------------- Summary: Edit screen missing default selection on drop downs Key: FORGE-451 URL: https://issues.jboss.org/browse/FORGE-451 Project: Forge Issue Type: Bug Reporter: Pete Muir When loading an edit screen, a @ManyToOne relationship is missing the default selection, instead the no selection option is chosen. -- 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, 5 months

5
11
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] 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, 6 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, 6 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, 6 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, 6 months

5
9
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-281) Repositories are not read from parent POM hierarchy when resoliving dependencies

by Lincoln Baxter III (JIRA)

Repositories are not read from parent POM hierarchy when resoliving dependencies -------------------------------------------------------------------------------- Key: SEAMFORGE-281 URL: https://issues.jboss.org/browse/SEAMFORGE-281 Project: Seam Forge Issue Type: Bug Components: Maven Integration Affects Versions: 1.0.0.Beta1 Reporter: Lincoln Baxter III With JBOSS_NEXUS: {code}[metawidget-forge-scaffold] scaffold-metawidget-lib $ scaffold setup ? No scaffold type was selected, use default (Metawidget & JSF)? [Y/n] ? Scaffold provider [metawidget] is not installed. Install it? [Y/n] Received Facet installation request [class org.metawidget.forge.MetawidgetScaffold] Install which version of Metawidget? 1 - [org.metawidget.modules.faces:metawidget-faces:::1.15] 2 - [org.metawidget.modules.faces:metawidget-faces:::1.20] 3 - [org.metawidget.modules.faces:metawidget-faces:::1.25-SNAPSHOT] 4 - [org.metawidget.modules.faces:metawidget-faces:::1.25] 5 - [org.metawidget.modules.faces:metawidget-faces:::1.30-SNAPSHOT] ? Choose an option by typing the number of the selection: {code} Without JBOSS_NEXUS: {code}[metawidget-forge-scaffold] scaffold-metawidget-lib $ scaffold setup ? No scaffold type was selected, use default (Metawidget & JSF)? [Y/n] ? Scaffold provider [metawidget] is not installed. Install it? [Y/n] Received Facet installation request [class org.metawidget.forge.MetawidgetScaffold] ***ERROR*** [scaffold setup] promptChoice() Cannot ask user to select from a list of nothing. Ensure you have values in your options list. org.jboss.forge.shell.exceptions.CommandExecutionException: promptChoice() Cannot ask user to select from a list of nothing. Ensure you have values in your options list. at org.jboss.forge.shell.command.Execution.perform(Execution.java:149) 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.execute(ShellImpl.java:698) at org.jboss.forge.shell.ShellImpl.doShell(ShellImpl.java:495) 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.doShell(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:83) at java.lang.Thread.run(Thread.java:662) Caused by: java.lang.reflect.InvocationTargetException 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.forge.shell.command.Execution.perform(Execution.java:144) ... 30 more Caused by: java.lang.IllegalArgumentException: promptChoice() Cannot ask user to select from a list of nothing. Ensure you have values in your options list. at org.jboss.forge.shell.AbstractShellPrompt.promptChoiceTyped(AbstractShellPrompt.java:238) at org.jboss.forge.shell.ShellImpl$Proxy$_$$_WeldClientProxy.promptChoiceTyped(ShellImpl$Proxy$_$$_WeldClientProxy.java) at org.metawidget.forge.MetawidgetScaffoldBase.install(MetawidgetScaffoldBase.java:291) at org.jboss.forge.project.BaseProject.performInstallation(BaseProject.java:258) at org.jboss.forge.project.BaseProject.installFacet(BaseProject.java:172) 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.weld.proxies.Project$-1946286523$Proxy$_$$_WeldClientProxy.installFacet(Project$-1946286523$Proxy$_$$_WeldClientProxy.java) at org.jboss.forge.shell.project.FacetInstallationHandler.performInstallation(FacetInstallationHandler.java:121) at org.jboss.forge.shell.project.FacetInstallationHandler.install(FacetInstallationHandler.java:97) at org.jboss.forge.shell.project.FacetInstallationHandler.installRequest(FacetInstallationHandler.java:75) 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.scaffold.plugins.ScaffoldPlugin.getScaffoldType(ScaffoldPlugin.java:186) at org.jboss.forge.scaffold.plugins.ScaffoldPlugin.setup(ScaffoldPlugin.java:94) ... 35 more {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
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues January 2012