January 2012 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-441) Running the admin_layout.fsh script in ticketmonster produces broken classes

by Pete Muir (JIRA)

Pete Muir created FORGE-441: ------------------------------- Summary: Running the admin_layout.fsh script in ticketmonster produces broken classes Key: FORGE-441 URL: https://issues.jboss.org/browse/FORGE-441 Project: Forge Issue Type: Bug Environment: HEAD Reporter: Pete Muir Try running the script at https://github.com/pmuir/ticket-monster-1/blob/minor_build/admin_layer.fsh having checked out the project (note it is on the minor_build branch). -- 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, 5 months

4
9
0 / 0

[JBoss JIRA] (FORGE-466) Use "gnome-open" instead of "gedit" for edit command on Linux

by Dan Allen (JIRA)

Dan Allen created FORGE-466: ------------------------------- Summary: Use "gnome-open" instead of "gedit" for edit command on Linux Key: FORGE-466 URL: https://issues.jboss.org/browse/FORGE-466 Project: Forge Issue Type: Enhancement Components: Builtin Plugins Affects Versions: 1.0.0.Beta5 Reporter: Dan Allen Priority: Minor Use the more generic "gnome-open" to edit a file rather than "gedit". This is a very simple, one-line fix that can provide the ability to use an alternate editor in the short term until a formal configuration solution is implemented. sed -i 's/gedit/gnome-open/' shell/src/main/java/org/jboss/forge/shell/plugins/builtin/EditPlugin.java You may want to take it one step further and check if gnome-open is there. If not, try kde-open. As a last resort, you can just open the file normally (like the view 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

12 years, 5 months

3
3
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-336) Need a way of supplying JARs to Plugins (e.g. Hibernate Tools)

by Lincoln Baxter III (JIRA)

Need a way of supplying JARs to Plugins (e.g. Hibernate Tools) --------------------------------------------------------------- Key: SEAMFORGE-336 URL: https://issues.jboss.org/browse/SEAMFORGE-336 Project: Seam Forge Issue Type: Feature Request Components: Plugin API, Usability Affects Versions: 1.0.0.Beta2 Reporter: Lincoln Baxter III You could (in theory) add a JAR to the plugin module where it is installed: .forge/plugins/org/jboss/hibernate/forge/hibernate-tools-plugin/dependencies/1.0.0-SNAPSHOT-*** and also add that jar as a resource in the module.xml file .forge/plugins/org/jboss/hibernate/forge/hibernate-tools-plugin/dependencies/1.0.0-SNAPSHOT-***/modules.xml That should do it, but it's not easy. This needs to be streamlined -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

2
12
0 / 0

[JBoss JIRA] (FORGE-379) Add user profiles

by Pete Muir (Created) (JIRA)

Add user profiles ----------------- Key: FORGE-379 URL: https://issues.jboss.org/browse/FORGE-379 Project: Forge Issue Type: Feature Request Affects Versions: 1.0.0.Beta3 Reporter: Pete Muir Assignee: Lincoln Baxter III At the moment Forge assumes that every user needs the same level of hand-holding. This means that advanced users are shortchanged (as they want more control) and newbies can get lost. Introducing a number of user profiles (e.g. newbie, intermediate, god) could help here. For example, if in newbie mode, the faces plugin wouldn't ask if you wanted to change from jar -> war packaging, assuming that the person does... -- 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, 5 months

3
2
0 / 0

[JBoss JIRA] (FORGE-407) Tab completion not working on forge-startup

by Tobias Boehnert (Created) (JIRA)

Tab completion not working on forge-startup ------------------------------------------- Key: FORGE-407 URL: https://issues.jboss.org/browse/FORGE-407 Project: Forge Issue Type: Bug Components: Shell Affects Versions: 1.0.0.Beta4 Environment: Win 7 64bit, JDK 1.6.0_29 32bit Reporter: Tobias Boehnert Priority: Minor When starting Forge to create a new project, the autocomplete-function on pressing <Tab> doesn't work. After calling any function or just pressing <Enter>, autocomplete works like a charm. -- 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, 5 months

5
7
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-342) Get online help from plugin's javadoc

by Jonathan Fuerth (JIRA)

Get online help from plugin's javadoc ------------------------------------- Key: SEAMFORGE-342 URL: https://issues.jboss.org/browse/SEAMFORGE-342 Project: Seam Forge Issue Type: Feature Request Components: Plugin API Reporter: Jonathan Fuerth Priority: Minor IDEs already have lots of great tooling to help write good javadoc and keep it neatly formatted and up to date. It would be excellent if forge's source of help text for plugins came straight from the javadoc. This could be done either via a doclet that operates on the Java source code, or by scraping the output of the default doclet (like Eclipse will do if you attach generated JavaDoc rather than library source code). Lowering the barrier to providing high-quality documentation should help encourage plugin authors to provide good help, and in turn that should help everyone pick up and learn Forge faster. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

2
1
0 / 0

[JBoss JIRA] (FORGE-378) Add "environments" as a first class construct

by Pete Muir (Created) (JIRA)

Add "environments" as a first class construct --------------------------------------------- Key: FORGE-378 URL: https://issues.jboss.org/browse/FORGE-378 Project: Forge Issue Type: Feature Request Reporter: Pete Muir Assignee: Lincoln Baxter III For example: {code} set environment JBOSS_AS7 --version 7.1.0.Final {code} Where JBOSS_AS7 is a built in profile that contains necessary info on various versions of JBoss AS 7. For example, the persistence plugin could read from this, changing {code} persistence setup --provider HIBERNATE --container JBOSS_AS7 {code} to {code} persistence setup {code} Or, when setting up CDI, this would remove the need to ask ask which API to use (always use the Java EE BOM with JBoss AS), and as the metadata builds, remove the need to ask the version of the spec BOM to use. Lot's of other places where this could provide better defaulting, or remove the need to ask questions. This also seems fairly consistent with the Forge approach - good understanding of the project in question. -- 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, 5 months

3
2
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-343) Package up some sample scripts into the Forge distribution

by Lincoln Baxter III (JIRA)

Package up some sample scripts into the Forge distribution ---------------------------------------------------------- Key: SEAMFORGE-343 URL: https://issues.jboss.org/browse/SEAMFORGE-343 Project: Seam Forge Issue Type: Task Components: Forge Build Affects Versions: 1.0.0.Beta2 Reporter: Lincoln Baxter III Fix For: 1.0.0.Final This will help show people how to 1. do scripting, 2. get started quickly. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

2
8
0 / 0

[JBoss JIRA] (FORGE-427) Facet cannot find @RequiresFacet in another resource JAR

by Tom Cunningham (JIRA)

Tom Cunningham created FORGE-427: ------------------------------------ Summary: Facet cannot find @RequiresFacet in another resource JAR Key: FORGE-427 URL: https://issues.jboss.org/browse/FORGE-427 Project: Forge Issue Type: Bug Components: Event Bus Affects Versions: 1.0.0.Beta4 Reporter: Tom Cunningham We've put a number of different plugins inside a common module, and SwitchYardFacet is in switchyard.forge-plugin-0.4.0-SNAPSHOT.jar. Can a facet in one of my other plugin JARs refer to that one? Do I need to go back to shading? Example - this Facet is in switchyard-camel-plugin-0.4.0-SNAPSHOT.jar but refers to SwitchYardFacet which is in another resource-root : switchyard-forge-plugin-0.4.0-SNAPSHOT.jar. import org.switchyard.tools.forge.plugin.SwitchYardFacet; /** * Forge facet for Camel bindings and services. */ @Alias("switchyard.camel") @RequiresFacet({ DependencyFacet.class, PackagingFacet.class, SwitchYardFacet.class }) @RequiresPackagingType(PackagingType.JAR) public class CamelFacet extends AbstractFacet { module.xml : <?xml version="1.0" encoding="UTF-8" standalone="no"?> <module xmlns="urn:jboss:module:1.0" name="org.switchyard.switchyard-forge-plugin" slot="0.4.0-SNAPSHOT"> <resources>  <resource-root path="switchyard-forge-common-0.4.0-SNAPSHOT.jar"/> <resource-root path="switchyard-component-common-rules-0.4.0-SNAPSHOT.jar"/>  <resource-root path="switchyard-forge-plugin-0.4.0-SNAPSHOT.jar"/> <resource-root path="switchyard-forge-bean-plugin-0.4.0-SNAPSHOT.jar"/> <resource-root path="switchyard-forge-soap-plugin-0.4.0-SNAPSHOT.jar"/> <resource-root path="switchyard-forge-rules-plugin-0.4.0-SNAPSHOT.jar"/> <resource-root path="switchyard-forge-bpm-plugin-0.4.0-SNAPSHOT.jar"/> <resource-root path="switchyard-forge-camel-plugin-0.4.0-SNAPSHOT.jar"/> </resources> Error - the missing Type seems to be SwitchYardFacet : tcunning at localhost:tmp]$ forge Listening for transport dt_socket at address: 8787 Plugin system disabled due to failure while loading one or more plugins; try removing offending plugins with "forge remove-plugin <TAB>". com.google.common.collect.ComputationException: java.lang.ArrayStoreException: sun.reflect.annotation.TypeNotPresentExceptionProxy at com.google.common.collect.ComputingConcurrentHashMap.compute(ComputingConcurrentHashMap.java:218) at com.google.common.collect.ComputingConcurrentHashMap.apply(ComputingConcurrentHashMap.java:100) at com.google.common.collect.MapMaker$ComputingMapAdapter.get(MapMaker.java:515) at org.jboss.weld.resources.ClassTransformer.loadClass(ClassTransformer.java:183) at org.jboss.weld.bootstrap.BeanDeployer.addClass(BeanDeployer.java:95) at org.jboss.weld.bootstrap.BeanDeployer.addClasses(BeanDeployer.java:134) at org.jboss.weld.bootstrap.BeanDeployment.createBeans(BeanDeployment.java:191) at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:368) at org.jboss.weld.environment.se.Weld.initialize(Weld.java:92) at org.jboss.forge.shell.Bootstrap$1.run(Bootstrap.java:87) at java.lang.Thread.run(Thread.java:662) Caused by: java.lang.ArrayStoreException: sun.reflect.annotation.TypeNotPresentExceptionProxy at sun.reflect.annotation.AnnotationParser.parseClassArray(AnnotationParser.java:653) at sun.reflect.annotation.AnnotationParser.parseArray(AnnotationParser.java:460) at sun.reflect.annotation.AnnotationParser.parseMemberValue(AnnotationParser.java:286) at sun.reflect.annotation.AnnotationParser.parseAnnotation(AnnotationParser.java:222) at sun.reflect.annotation.AnnotationParser.parseAnnotations2(AnnotationParser.java:69) at sun.reflect.annotation.AnnotationParser.parseAnnotations(AnnotationParser.java:52) at java.lang.Class.initAnnotationsIfNecessary(Class.java:3070) at java.lang.Class.getAnnotations(Class.java:3050) at org.jboss.weld.introspector.jlr.WeldClassImpl.of(WeldClassImpl.java:98) at org.jboss.weld.resources.ClassTransformer$TransformTypeToWeldClass.apply(ClassTransformer.java:54) at org.jboss.weld.resources.ClassTransformer$TransformTypeToWeldClass.apply(ClassTransformer.java:42) at com.google.common.collect.ComputingConcurrentHashMap.compute(ComputingConcurrentHashMap.java:206) ... 10 more -- 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, 5 months

5
12
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-330) Display a diff of available commands when starting forge after installing/removing a plugin

by Lincoln Baxter III (JIRA)

Display a diff of available commands when starting forge after installing/removing a plugin ------------------------------------------------------------------------------------------- Key: SEAMFORGE-330 URL: https://issues.jboss.org/browse/SEAMFORGE-330 Project: Seam Forge Issue Type: Feature Request Components: Brainstorming Affects Versions: 1.0.0.Beta2 Reporter: Lincoln Baxter III Fix For: Future In order to help people understand which new commands are available, or which plugins are no longer available, this would be very useful: {code}The following plugins have been activated [rhc, rhc-login] $ {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

2
5
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues January 2012