November 2011 - forge-issues - Jboss List Archives

[JBoss JIRA] Created: (SEAMFORGE-320) Verify that all "Blessed Plugins" compile, install, and run on Forge 1.0.0.Final before releasing

by Lincoln Baxter III (JIRA)

Verify that all "Blessed Plugins" compile, install, and run on Forge 1.0.0.Final before releasing ------------------------------------------------------------------------------------------------- Key: SEAMFORGE-320 URL: https://issues.jboss.org/browse/SEAMFORGE-320 Project: Seam Forge Issue Type: Task Components: Blessed Plugins Affects Versions: 1.0.0.Final 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

12 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-310) Support generation of @Entity "finder" methods

by Lincoln Baxter III (JIRA)

Support generation of @Entity "finder" methods ---------------------------------------------- Key: SEAMFORGE-310 URL: https://issues.jboss.org/browse/SEAMFORGE-310 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 Support generation of "Finder" methods for entities "findByNameAndAddress(String name, Address address)" and corresponding Finder pages for the User interface. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

7
7
0 / 0

[JBoss JIRA] (SEAMFORGE-363) Simple example on Forge main page fails to deploy on JBoss 6 with *_WeldBootstrapBean NPE

by Steve Tarver (Created) (JIRA)

Simple example on Forge main page fails to deploy on JBoss 6 with *_WeldBootstrapBean NPE ----------------------------------------------------------------------------------------- Key: SEAMFORGE-363 URL: https://issues.jboss.org/browse/SEAMFORGE-363 Project: Forge Issue Type: Bug Components: Forge Build Affects Versions: 1.0.0.Beta3 Environment: Mac OSX 10.7.2, jdk 1.6.0_26 Reporter: Steve Tarver Simple example from https://docs.jboss.org/author/display/SEAMFORGE/Generating+a+basic+Java+E... fails on deploy. With a fresh forge-1.0.0.Beta3 and fresh JBoss 6.0.0.Final, construct the example, build, copy war to JBoss deploy directory, start JBoss and get Error installing to Create: name=vfs:///Users/starver/dev/jboss/jboss-6.0.0.Final/server/dev/jb6_eg/deploy/savvis/forgetest.war_WeldBootstrapBean state=Configured: java.lang.NullPointerException -- 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, 3 months

4
3
0 / 0

[JBoss JIRA] (FORGE-372) Qualifier on Forge EntityManager

by Paul Dijou (Created) (JIRA)

Qualifier on Forge EntityManager -------------------------------- Key: FORGE-372 URL: https://issues.jboss.org/browse/FORGE-372 Project: Forge Issue Type: Enhancement Components: Scaffold Affects Versions: 1.0.0.Beta3 Reporter: Paul Dijou Assignee: Lincoln Baxter III The EntityManager (same for the EntityManagerFactory) generated by Forge in org.metawidget.forge.persistence.DatasourceProducer has no Qualifier. It becomes a problem when I need to create my own EntityManager because they both have the @Default qualifier and CDI throws an exception. The only solution is to add a qualifier to my EntityManager but it bother me since I want it to be the default EntityManager. To reproduce the problem, just install the seam-persistence plugin, ask "seam-persistence install-managed-persistence-context" and it will generate another EntityManagerFactory with no qualifier and here is the CDI exception. Would it be possible to add a qualifier like "@ForgeEntityManager" and "@ForgeEntityManagerFactory" on the DatasourceProducer class ? (and, of course, on the PersistenceUtil class too). This way, if a user add it's own EntityManager, it well be the @Default. Thanks. -- 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, 4 months

10
14
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-295) Support automatic "Use Defaults" mmode

by Lincoln Baxter III (JIRA)

Support automatic "Use Defaults" mmode -------------------------------------- Key: SEAMFORGE-295 URL: https://issues.jboss.org/browse/SEAMFORGE-295 Project: Seam Forge Issue Type: Feature Request Components: Shell Affects Versions: 1.0.0.Beta2 Reporter: Lincoln Baxter III For supporting scripting and "more rapid generation" - Forge should support a mode in which, when set, if a prompt supplies a default value, that value should be submitted/returned without prompting the user. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

2
1
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-339) Run a script from a (non-local) URL

by Jonathan Fuerth (JIRA)

Run a script from a (non-local) URL ----------------------------------- Key: SEAMFORGE-339 URL: https://issues.jboss.org/browse/SEAMFORGE-339 Project: Seam Forge Issue Type: Feature Request Components: Forge Scripting Language Reporter: Jonathan Fuerth Priority: Minor Forge is a great way to help people get started with a new framework. Quick start guides can be simplified by using Forge scripts, but right now the instructions have to include "right click on the script, save as, remember where you saved it, run it in the Forge shell..." Being able to name a script by an HTTP/HTTPS URL would simplify quick-start guides greatly: they can say "To get started, type this Forge command exactly" and it will work. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

3
2
0 / 0

[JBoss JIRA] (FORGE-390) Plugin builds successfully but cannot be executed

by Ryan Bradley (Created) (JIRA)

Plugin builds successfully but cannot be executed ------------------------------------------------- Key: FORGE-390 URL: https://issues.jboss.org/browse/FORGE-390 Project: Forge Issue Type: Bug Components: Plugin API, Usability Affects Versions: 1.0.0.Beta3 Environment: OS: Fedora 15, JPA Provider: Hibernate 4.0.0.CR6, Container: JBoss AS 7.0.3.Final Reporter: Ryan Bradley My plugin, created and developed in Forge, stopped being recognized by Forge. I tried removing the plugin from .forge/plugins/installed.xml, running 'forge source-plugin ${PATH_TO_PLUGIN}' again, confirming that it had been added to installed.xml again, and, although the build was successful, when I tried to execute the plugin, the command was not found. A pastebin of the build and subsequent attempted execution is provided at: http://pastebin.com/5us0GAMP. (Yes, I did double check that I used the same name as the plugin alias). Perhaps this could be a problem with the Forge plugin setup process? Note: as a workaround, I had to create a new plugin and copy over source code from the previous 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, 4 months

4
3
0 / 0

[JBoss JIRA] (FORGE-384) Use dependency management and BOMs not direct manipulation of dependencies

by Pete Muir (Created) (JIRA)

Use dependency management and BOMs not direct manipulation of dependencies -------------------------------------------------------------------------- Key: FORGE-384 URL: https://issues.jboss.org/browse/FORGE-384 Project: Forge Issue Type: Bug Affects Versions: 1.0.0.Beta3 Reporter: Pete Muir Assignee: Lincoln Baxter III The recommended practice we have for archetypes and quickstarts mandates this, so Forge needs to follow. -- 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, 4 months

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

12 years, 4 months

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

12 years, 4 months

3
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues November 2011