December 2011 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-137) Add explode and deploy goals to pom.xml during scaffold generation

by Lincoln Baxter III (Closed) (JIRA)

[ https://issues.jboss.org/browse/FORGE-137?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III closed FORGE-137. ------------------------------------ Fix Version/s: 1.0.0.Beta4 Resolution: Done The AS7 plugin supports --deployExploded > Add explode and deploy goals to pom.xml during scaffold generation > ------------------------------------------------------------------ > > Key: FORGE-137 > URL: https://issues.jboss.org/browse/FORGE-137 > Project: Forge > Issue Type: Enhancement > Components: Forge Build, Maven Integration > Environment: JBoss 7, JBoss 6, Glassfish 3.1 > Reporter: Kevin Sapper > Fix For: 1.0.0.Beta4 > > > Hi Guys, > One of the most compelling features about seam-gen is that after you've build the projects scaffold deploying and exploding to an application server just goes by calling an ant target. It really would be nice to have such a goal in the projects pom.xml after creating the scaffold and boilerplate code. Adding that functionality yourself really takes an awful lot of time. Especially with glassfish 3.1 I failed to accomplish that task. > Best regards//Kevin -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-311) Support bookmarking in generated pages

by Lincoln Baxter III (JIRA)

Support bookmarking in generated pages -------------------------------------- Key: SEAMFORGE-311 URL: https://issues.jboss.org/browse/SEAMFORGE-311 Project: Seam Forge Issue Type: Feature Request Components: Scaffold Affects Versions: 1.0.0.Beta2 Reporter: Lincoln Baxter III Fix For: 1.0.0.Final -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

4
3
0 / 0

[JBoss JIRA] (FORGE-400) Build and Run Problems on Different Platforms

by Koen Aers (Created) (JIRA)

Build and Run Problems on Different Platforms --------------------------------------------- Key: FORGE-400 URL: https://issues.jboss.org/browse/FORGE-400 Project: Forge Issue Type: Bug Components: Forge Build Reporter: Koen Aers On Windows XP: - 'mvn clean install' hangs while executing: org.jboss.forge.spec.validation.ValidationPluginTest; The problem is reproduceable while executing the test in isolation e.g. in Eclipse. - 'mvn -DskipTests clean install' finishes successfully but running the created Forge runtime hangs during startup -- 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, 1 month

6
10
0 / 0

[JBoss JIRA] (FORGE-290) Code coverage plugin - Support Mavan Failsafe plugin

by Lincoln Baxter III (Closed) (JIRA)

[ https://issues.jboss.org/browse/FORGE-290?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III closed FORGE-290. ------------------------------------ Resolution: Migrated to another ITS > Code coverage plugin - Support Mavan Failsafe plugin > ---------------------------------------------------- > > Key: FORGE-290 > URL: https://issues.jboss.org/browse/FORGE-290 > Project: Forge > Issue Type: Feature Request > Components: Blessed Plugins > Reporter: Paul Bakker > > It's a best practice to split unit tests and integration tests because integration tests might be slower. Maven uses the failsafe plugin to run integration tests, but requires a lot of setup. This should be handled by the code quality 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (FORGE-334) Tools for Forge Roadmap and Ideas

by Lincoln Baxter III (Closed) (JIRA)

[ https://issues.jboss.org/browse/FORGE-334?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III closed FORGE-334. ------------------------------------ Resolution: Done Will open individual specific feature requests as they come up. Otherwise this issue will never close. > Tools for Forge Roadmap and Ideas > --------------------------------- > > Key: FORGE-334 > URL: https://issues.jboss.org/browse/FORGE-334 > Project: Forge > Issue Type: Task > Reporter: Koen Aers > Assignee: Koen Aers > > I want to open a discussion about the JBoss Tools integration. The baseline of this integration is the Forge Console currently available in the JBoss Tools SVN repository. Evidently a whole bunch of improvements and additional features need to be implemented. I would be good if all the ideas around this could be gathered in this issue and result in new tasks. > I'll start off myself by giving a list of functionality that I think should be included. > (1) normally, pressing the tab character should result in Forge suggesting the list of possible commands; this is not working currently > (2) the usual colors you get when running Forge from the command line result in garbled output in the Eclipse Forge console; we need to find a way of getting this functionality up and running in Eclipse > (3) after performing each Forge command, appropriate actions need to be performed and feedback needs to be given to the user; this feedback will be highly dependent on the particular command; > (a) e.g. after creating a project the project should be imported in the workspace > (b) e.g. after creating an entity, the created containing folder needs to be refreshed and the file opened > (c) e.g. after creating a field, the field needs to be selected in the open editor > (4) imo, it doesn't make sense to perform Forge commands outside the Eclipse workspace; therefore, i think it should be made impossible to cd out of the workspace folder; similarly, a pwd command should probably be rooted in the workspace root. > (5) at this time the Forge runtime is embedded in the plugin; while it is not necessarily a bad idea to continue to ship a runtime in an Eclipse plugin, it's probably wise to offer the users a way to add additional runtimes by means of a preference page and evidently provide a way to select the default Forge runtime; this is similar to the way you select a default JVM for an Eclipse workspace. > (6) use a preference page to add Forge plugin repositories > (7) maintain the command history; currently the upward arrow just moves the cursor upward in the console viewer. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-284) AS7 Plugin Should be able to Download, Install, & Run AS7

by Lincoln Baxter III (JIRA)

AS7 Plugin Should be able to Download, Install, & Run AS7 --------------------------------------------------------- Key: SEAMFORGE-284 URL: https://issues.jboss.org/browse/SEAMFORGE-284 Project: Seam Forge Issue Type: Feature Request Components: Builtin Plugins Affects Versions: 1.0.0.Beta1 Reporter: Lincoln Baxter III https://github.com/lincolnthree/jboss-as-test-example/blob/master/pom.xml Can use something similar to the AS7 explode maven plugin, then use arquillian APIs to do deployments via AS7 *Managed* adapter. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

3
4
0 / 0

[JBoss JIRA] (FORGE-219) jbpm5 forge plugin

by Lincoln Baxter III (Closed) (JIRA)

[ https://issues.jboss.org/browse/FORGE-219?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III closed FORGE-219. ------------------------------------ Resolution: Rejected Don't need to file core JIRA issues for creating new plugins. Have a blast :) Keep it up! > jbpm5 forge plugin > ------------------ > > Key: FORGE-219 > URL: https://issues.jboss.org/browse/FORGE-219 > Project: Forge > Issue Type: Feature Request > Components: Blessed Plugins > Reporter: Michael Schuetz > > creating plugin for jbpm5. > I would like to do this and started to work locally already. Within next few days, I'll push first implementation to github. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-278) add an option to provide external templates for the metawidget scaffolding plugin

by Dror Bereznitsky (JIRA)

add an option to provide external templates for the metawidget scaffolding plugin --------------------------------------------------------------------------------- Key: SEAMFORGE-278 URL: https://issues.jboss.org/browse/SEAMFORGE-278 Project: Seam Forge Issue Type: Feature Request Components: Scaffold Affects Versions: 1.0.0.Beta1 Reporter: Dror Bereznitsky Current implementation uses built-in templates and there is no way to override them. It would be nice to be able to provide an alternative path for templates or look them up in the project resources directory (or any other convention) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

2
1
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-349) When Creating an Arquillian test and the class file select requires any web-only features the Test.java class should create a WebArchive rather than a JavaArchive.

by Craig Schwarzwald (JIRA)

When Creating an Arquillian test and the class file select requires any web-only features the Test.java class should create a WebArchive rather than a JavaArchive. ------------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: SEAMFORGE-349 URL: https://issues.jboss.org/browse/SEAMFORGE-349 Project: Forge Issue Type: Enhancement Components: JBoss Tools Integration, Plugin Repository Affects Versions: 1.0.0.Beta3 Environment: Any environment Reporter: Craig Schwarzwald End result of the created arquillian test class should have Deployment method as follows: @Deployment public static WebArchive createDeployment() { return ShrinkWrap.create(WebArchive.class, "test.war") .addPackage(<ClassBeingTested>.class.getPackage()) //To ensure all necessary classes are added .addAsResource("META-INF/persistence.xml") //If this file exists .addAsWebResource(new StringAsset("<beans/>"), ArchivePaths.create("WEB-INF/beans.xml")); } Currently when running: arquillian create-test --class MyClass.java An Arquillian test is created, but as a JavaArchive which is not correct. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

4
3
0 / 0

[JBoss JIRA] (SEAMFORGE-358) Seam JMS plugin - ERROR: Could not load specified importer class from CompositeClassLoader

by Marek Schmidt (Created) (JIRA)

Seam JMS plugin - ERROR: Could not load specified importer class from CompositeClassLoader ------------------------------------------------------------------------------------------ Key: SEAMFORGE-358 URL: https://issues.jboss.org/browse/SEAMFORGE-358 Project: Forge Issue Type: Bug Components: Blessed Plugins Environment: Seam JMS 3.1.0.Beta3, Forge 1.0.0.Beta3 Reporter: Marek Schmidt {noformat} ____ _____ / ___| ___ __ _ _ __ ___ | ___|__ _ __ __ _ ___ \___ \ / _ \/ _` | '_ ` _ \ | |_ / _ \| '__/ _` |/ _ \ \\ ___) | __/ (_| | | | | | | | _| (_) | | | (_| | __/ // |____/ \___|\__,_|_| |_| |_| |_| \___/|_| \__, |\___| |___/ [seamtest] seamtest $ jms install Install which version of Seam JMS? 1 - [org.jboss.seam.jms:seam-jms:::3.0.0.Alpha1] 2 - [org.jboss.seam.jms:seam-jms:::3.1.0-SNAPSHOT] 3 - [org.jboss.seam.jms:seam-jms:::3.1.0.Beta3] ? Choose an option by typing the number of the selection: 3 Wrote /home/maschmid/testing/forge/tmp/seamtest/pom.xml [seamtest] seamtest $ [seamtest] seamtest $ jms hornetq-queue ? [name=The name of the queue (of type java.lang.String)]: myqueue ***ERROR*** [jms hornetq-queue] Could not load specified importer class from CompositeClassLoader [classLoaders=[ModuleClassLoader for Module "org.jboss.seam.jms.seam-jms-forge-plugin:1.0.0-SNAPSHOT-e4ba2b11-a330-4175-b755-f8286953ba43" from local module loader @3b6f0be8 (roots: /home/maschmid/testing/forge/forge-1.0.0.Beta3/modules,/home/maschmid/.forge/plugins), ModuleClassLoader for Module "org.jboss.forge.seam.persistence.plugin-seam-persistence:1.0.0-SNAPSHOT-dbc94c2c-4c91-41df-a231-8ecb5566aae0" from local module loader @3b6f0be8 (roots: /home/maschmid/testing/forge/forge-1.0.0.Beta3/modules,/home/maschmid/.forge/plugins), ModuleClassLoader for Module "org.jboss.forge:main" from local module loader @3b6f0be8 (roots: /home/maschmid/testing/forge/forge-1.0.0.Beta3/modules,/home/maschmid/.forge/plugins)]]: org.jboss.shrinkwrap.descriptor.impl.base.XMLImporter [seamtest] seamtest $ jms hornetq- hornetq-topic hornetq-queue [seamtest] seamtest $ jms hornetq- hornetq-topic hornetq-queue [seamtest] seamtest $ jms hornetq-topic ? [name=The name of the topic (of type java.lang.String)]: mytopic ***ERROR*** [jms hornetq-topic] Could not load specified importer class from CompositeClassLoader [classLoaders=[ModuleClassLoader for Module "org.jboss.seam.jms.seam-jms-forge-plugin:1.0.0-SNAPSHOT-e4ba2b11-a330-4175-b755-f8286953ba43" from local module loader @3b6f0be8 (roots: /home/maschmid/testing/forge/forge-1.0.0.Beta3/modules,/home/maschmid/.forge/plugins), ModuleClassLoader for Module "org.jboss.forge.seam.persistence.plugin-seam-persistence:1.0.0-SNAPSHOT-dbc94c2c-4c91-41df-a231-8ecb5566aae0" from local module loader @3b6f0be8 (roots: /home/maschmid/testing/forge/forge-1.0.0.Beta3/modules,/home/maschmid/.forge/plugins), ModuleClassLoader for Module "org.jboss.forge:main" from local module loader @3b6f0be8 (roots: /home/maschmid/testing/forge/forge-1.0.0.Beta3/modules,/home/maschmid/.forge/plugins)]]: org.jboss.shrinkwrap.descriptor.impl.base.XMLImporter [seamtest] seamtest $ {noformat} -- 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, 1 month

2
1
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues December 2011