May 2012 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-573) IllegalStateException when launching forge

by Hubert Schumacher (JIRA)

Hubert Schumacher created FORGE-573: --------------------------------------- Summary: IllegalStateException when launching forge Key: FORGE-573 URL: https://issues.jboss.org/browse/FORGE-573 Project: Forge Issue Type: Bug Components: Forge Build Affects Versions: 1.0.4.Final Environment: uname -a: Linux i7 3.3.4-1.fc16.x86_64 #1 SMP Fri Apr 27 20:12:28 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux java -version: java version "1.7.0" Java(TM) SE Runtime Environment (build 1.7.0-b147) Java HotSpot(TM) 64-Bit Server VM (build 21.0-b17, mixed mode) jboss 7.1.1 Reporter: Hubert Schumacher 1. FORGE_HOME and PATH configured as described in 'https://docs.jboss.org/author/display/FORGE/Installation' 2. launch forge 3. Console output: [hrrbrt@i7 kg]$ forge java.lang.IllegalStateException: Plugin entry.getApiVersion() must not be null. at org.jboss.forge.parser.java.util.Assert.notNull(Assert.java:13) at org.jboss.forge.shell.InstalledPluginRegistry.isApiCompatible(InstalledPluginRegistry.java:411) at org.jboss.forge.shell.InstalledPluginRegistry.listByAPICompatibleVersion(InstalledPluginRegistry.java:99) at org.jboss.forge.shell.Bootstrap.loadPlugins(Bootstrap.java:206) at org.jboss.forge.shell.Bootstrap.access$200(Bootstrap.java:55) at org.jboss.forge.shell.Bootstrap$1.run(Bootstrap.java:131) at java.lang.Thread.run(Thread.java:722) _____ | ___|__ _ __ __ _ ___ | |_ / _ \| `__/ _` |/ _ \ \\ | _| (_) | | | (_| | __/ // |_| \___/|_| \__, |\___| |___/ [no project] kg $ -- 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

13 years, 11 months

2
3
0 / 0

[JBoss JIRA] (FORGE-567) Update to jboss-javaee-6.0 BOm version 3

by Pete Muir (JIRA)

Pete Muir created FORGE-567: ------------------------------- Summary: Update to jboss-javaee-6.0 BOm version 3 Key: FORGE-567 URL: https://issues.jboss.org/browse/FORGE-567 Project: Forge Issue Type: Task Components: Scaffold Reporter: Pete Muir Scaffold is adding version 2.0.0.Final still, needs to be 3.0.0.Final -- 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

13 years, 11 months

2
2
0 / 0

[JBoss JIRA] (FORGE-571) Top level package should have a default value

by Dan Allen (JIRA)

Dan Allen created FORGE-571: ------------------------------- Summary: Top level package should have a default value Key: FORGE-571 URL: https://issues.jboss.org/browse/FORGE-571 Project: Forge Issue Type: Enhancement Components: Builtin Plugins Affects Versions: 1.0.2.Final Reporter: Dan Allen Priority: Minor When creating a new project, the top level package option should provide a default value to allow the question to be skipped. Currently, the user is prompted as follows: {code} ? [topLevelPackage=The top-level java package for the project [e.g: "com.example.project"] (of type java.lang.String)]: {code} There should be a default value for this option that is derived from the project name, such as: 1) equal to project name 2) "com.example." + project name I don't have a preference. I just want to be able to be able to skip this question when I'm creating a throwaway project. -- 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

13 years, 11 months

3
5
0 / 0

[JBoss JIRA] (FORGE-555) tab completion appends wrongly escapes last space of a unique candidate

by Koen Aers (JIRA)

Koen Aers created FORGE-555: ------------------------------- Summary: tab completion appends wrongly escapes last space of a unique candidate Key: FORGE-555 URL: https://issues.jboss.org/browse/FORGE-555 Project: Forge Issue Type: Bug Reporter: Koen Aers Assignee: Koen Aers Fix For: 1.0.3.Final This is a glitch resulting from the implementation of FORGE-43: type 'new-pro' + tab results in 'new-project\ '. -- 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

13 years, 11 months

2
4
0 / 0

[JBoss JIRA] (FORGE-521) Fix the formatting of Forge-generated JPA entity

by Ivan St. Ivanov (JIRA)

Ivan St. Ivanov created FORGE-521: ------------------------------------- Summary: Fix the formatting of Forge-generated JPA entity Key: FORGE-521 URL: https://issues.jboss.org/browse/FORGE-521 Project: Forge Issue Type: Enhancement Components: Builtin Plugins Reporter: Ivan St. Ivanov Fix For: 1.0.2.Final An entity generated by Forge looks like this: package com.test.entity; // Some imports go here // below is the last import, and not only import java.lang.Override;@Entity public class Employee implements java.io.Serializable { It's ugly because the statements on the last line above should be on at least three (and at best four) separate lines: import java.lang.Override; @Entity public class Employee implements java.io.Serializable { -- 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

13 years, 11 months

2
7
0 / 0

[JBoss JIRA] (FORGE-560) ascii art when you start up forge still says Seam Forge

by Jason Porter (JIRA)

Jason Porter created FORGE-560: ---------------------------------- Summary: ascii art when you start up forge still says Seam Forge Key: FORGE-560 URL: https://issues.jboss.org/browse/FORGE-560 Project: Forge Issue Type: Enhancement Components: Shell Affects Versions: 1.0.4.Final Reporter: Jason Porter Priority: Minor The ascii art needs to be updated to reflect the name JBoss Forge -- 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

13 years, 11 months

3
4
0 / 0

[JBoss JIRA] (FORGE-550) Should be able to list all available (not necessarily in use) scaffold providers

by Lincoln Baxter III (JIRA)

Lincoln Baxter III created FORGE-550: ---------------------------------------- Summary: Should be able to list all available (not necessarily in use) scaffold providers Key: FORGE-550 URL: https://issues.jboss.org/browse/FORGE-550 Project: Forge Issue Type: Enhancement Components: Scaffold Affects Versions: 1.0.2.Final Reporter: Lincoln Baxter III Right now the only way to "discover" which types of scaffold are installed is to either: a) Check your installed plugins b) type: "scaffold setup --scaffoldType <TAB>" and see which options it comes up with as completion proposals. It would be grand to have a "scaffold list-providers" command, to list and display basic information about each scaffold. E.g: {code} $ scaffold list-providers * Aerogear: Basic PoH5 & Rest Mobile Scaffolding * Faces: JavaServer Faces scaffolding * SpringMVC: What it sounds like... {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

13 years, 11 months

2
6
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues May 2012