June 2011 - forge-dev - Jboss List Archives

[JBoss JIRA] Created: (SEAMFORGE-156) Update MetaWidget dependencies to not bring in metawidget-all

by Andrew Rubinger (JIRA)

Update MetaWidget dependencies to not bring in metawidget-all ------------------------------------------------------------- Key: SEAMFORGE-156 URL: https://issues.jboss.org/browse/SEAMFORGE-156 Project: Seam Forge Issue Type: Task Reporter: Andrew Rubinger Fix For: 1.0.0.Alpha4 We don't need MetaWidget-all, which will also bring in Spring core classes (breaking in AS7 deployments). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

8
17
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-113) project list-dependencies should resolve property values

by Dan Allen (JIRA)

project list-dependencies should resolve property values -------------------------------------------------------- Key: SEAMFORGE-113 URL: https://issues.jboss.org/browse/SEAMFORGE-113 Project: Seam Forge Issue Type: Enhancement Components: Builtin Plugins Affects Versions: 1.0.0.Alpha3 Reporter: Dan Allen Priority: Minor Currently, when you list dependencies, it shows the property expression rather than the actual version in the case a property expression is used: {code} org.jboss.arquillian : arquillian-junit : ${arquillian.version} : jar : test {code} In this case, both the property and the version should be shown: {code} org.jboss.arquillian : arquillian-junit : ${arquillian.version} = 1.0.0.Alpha5 : jar : test {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

2
1
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-239) Change default plugin checkout location to use the .forge/plugins-sources directory

by Lincoln Baxter III (JIRA)

Change default plugin checkout location to use the .forge/plugins-sources directory ----------------------------------------------------------------------------------- Key: SEAMFORGE-239 URL: https://issues.jboss.org/browse/SEAMFORGE-239 Project: Seam Forge Issue Type: Task Components: Shell Affects Versions: 1.0.0.Alpha4 Reporter: Lincoln Baxter III Fix For: 1.0.0.Beta1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
2
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-215) Message 'JSF2 and Metawidget currently require Partial State Saving to be disabled' is Mojarra only

by Richard Kennard (JIRA)

Message 'JSF2 and Metawidget currently require Partial State Saving to be disabled' is Mojarra only --------------------------------------------------------------------------------------------------- Key: SEAMFORGE-215 URL: https://issues.jboss.org/browse/SEAMFORGE-215 Project: Seam Forge Issue Type: Feature Request Affects Versions: 1.0.0.Alpha4 Reporter: Richard Kennard Hi guys, Congrats on the latest release (Alpha4) of Seam Forge! When I try it, I see: [TestApp] TestApp $ scaffold setup ? No scaffold type was selected, use default (Metawidget & JSF)? [Y/n] y ? Scaffold provider [metawidget] is not installed. Install it? [Y/n] y ? Facet [forge.maven.WebResourceFacet] requires packaging type(s) [war], but is currently [jar]. Update packaging? plugins in your project.) [Y/n] y ...other output... **INFO*** JSF2 and Metawidget currently require Partial State Saving to be disabled. It's great to see this info message. It relates to this bug in Mojarra (http://java.net/jira/browse/JAVASERVERFACES-1826). However the equivalent bug in MyFaces (https://issues.apache.org/jira/browse/MYFACES-2935) has been fixed for a while. Does SeamForge allow choosing Mojarra/MyFaces? If so, this info shouldn't appear for MyFaces. If not, could we just clarify it applies only to Mojarra? Perhaps by displaying the version number? **INFO*** JSF2 (Mojarra 2.0.3) and Metawidget currently require Partial State Saving to be disabled. Thanks! In the meantime I'm pushing as hard as I can to get 1826 resolved! Richard. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

2
1
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-190) Integration test mechanism for external plugins

by Paul Bakker (JIRA)

Integration test mechanism for external plugins ----------------------------------------------- Key: SEAMFORGE-190 URL: https://issues.jboss.org/browse/SEAMFORGE-190 Project: Seam Forge Issue Type: Feature Request Components: Test Harness Reporter: Paul Bakker Formalize and document how integration tests for external plugins should be written. This should answer at least the following questions: -What should I add to the plugin's maven config -How do I write a test for a plugin using the input queue -How do I test a Facet directly (without using the input queue) -How do I setup a test project from my test -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-184) Injected EntityManager not work in servlet

by Liu Jianhong (JIRA)

Injected EntityManager not work in servlet ------------------------------------------ Key: SEAMFORGE-184 URL: https://issues.jboss.org/browse/SEAMFORGE-184 Project: Seam Forge Issue Type: Bug Environment: Jboss AS7,weld 1.1.1,forge snapshot Reporter: Liu Jianhong Injected EntityManager not work in servlet. Because @ConversationScoped used in org.jboss.forge.persistence.DatasourceProducer,when invoke create(artifact) then produce the this error "WELD-001303 No active contexts for scope type javax.enterprise.context.ConversationScoped". -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

2
1
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-158) Create a Seam Catch Plugin

by Jason Porter (JIRA)

Create a Seam Catch Plugin -------------------------- Key: SEAMFORGE-158 URL: https://issues.jboss.org/browse/SEAMFORGE-158 Project: Seam Forge Issue Type: Feature Request Reporter: Jason Porter -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

2
5
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-137) Should validate plugin API names to ensure no duplicates occur

by Lincoln Baxter III (JIRA)

Should validate plugin API names to ensure no duplicates occur -------------------------------------------------------------- Key: SEAMFORGE-137 URL: https://issues.jboss.org/browse/SEAMFORGE-137 Project: Seam Forge Issue Type: Feature Request Components: Plugin API, Shell Affects Versions: 1.0.0.Alpha3 Reporter: Lincoln Baxter III Fix For: 1.0.0.Beta1 Should be invalid for same resource scopes @Alias("whee") @Alias("whee") Should be invalid in same command: @Option(name="named") @Option(name="named") And so on... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-136) Should use the JBoss Modules project for plugin packaging/loading/isolation.

by Lincoln Baxter III (JIRA)

Should use the JBoss Modules project for plugin packaging/loading/isolation. ---------------------------------------------------------------------------- Key: SEAMFORGE-136 URL: https://issues.jboss.org/browse/SEAMFORGE-136 Project: Seam Forge Issue Type: Enhancement Components: Plugin API Affects Versions: 1.0.0.Alpha3 Reporter: Lincoln Baxter III Fix For: 1.0.0.Beta1 Investigate use of the JBoss Modules system for plugin packaging, loading, and dependency management. http://relation.to/16904.lace https://github.com/jbossas/jboss-modules http://docs.jboss.org/jbossmodules/latest/ -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-85) Forge should support dynamic loading of plugin library dependencies

by Lincoln Baxter III (JIRA)

Forge should support dynamic loading of plugin library dependencies ------------------------------------------------------------------- Key: SEAMFORGE-85 URL: https://issues.jboss.org/browse/SEAMFORGE-85 Project: Seam Forge Issue Type: Feature Request Components: Plugin API Affects Versions: 1.0.0.Alpha2 Reporter: Lincoln Baxter III Right now, Forge extensions must use the maven shade-plugin to package referenced dependencies of plugins. It would greatly enhance developer experience if referenced plugins or libraries could be dynamically loaded from the local maven repository, even if built with Git. A META-INF/dependencies file could be used to list runtime dependencies of the plugin. Or the POM files of each plugin (META-INF/pom...) could be scanned and parsed to determine required libs. A third option, programmatic declaration of runtime dependencies might also be an option if it can be worked into Java from Groovy: http://groovy.codehaus.org/Grape Benefits of these approaches are: * Reduced size deliverable ZIPfile * ... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-dev June 2011