[JBoss JIRA] Created: (SEAMFORGE-263) Add the possibility to register TriggeredActions on the ConsoleReader
by Koen Aers (JIRA)
Add the possibility to register TriggeredActions on the ConsoleReader
---------------------------------------------------------------------
Key: SEAMFORGE-263
URL: https://issues.jboss.org/browse/SEAMFORGE-263
Project: Seam Forge
Issue Type: Feature Request
Reporter: Koen Aers
This issue is related to SEAMFORGE-253. Using the CommandInterceptor does not give me the wanted result as it relies on the ConsoleReader mechanism to read entire lines. I have had better results with using the ConsoleReader ability to register so-called TriggeredActions.
These TriggeredActions are simple ActionListeners that get performed when a particular character is read. The Forge API needs to include a new interface in the SPI package and the ShellImpl needs to register the beans implementing this interface during the setup of the ConsoleReader.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[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
[JBoss JIRA] Created: (SEAMFORGE-259) Forge distribution crashes on startup
by Martin Borgman (JIRA)
Forge distribution crashes on startup
-------------------------------------
Key: SEAMFORGE-259
URL: https://issues.jboss.org/browse/SEAMFORGE-259
Project: Seam Forge
Issue Type: Bug
Components: Shell
Affects Versions: 1.0.0.Alpha4
Environment: Java version: 1.6.0_26, vendor: Apple Inc.
Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
Default locale: en_US, platform encoding: MacRoman
OS name: "mac os x", version: "10.6.8", arch: "x86_64", family: "mac"
FORGE_HOME=/Users/martinborgman/tools/forge
PATH=/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/opt/X11/bin:/usr/texbin:/usr/X11/bin:/usr/local/CrossPack-AVR/bin:/Users/martinborgman/tools/forge/bin
Reporter: Martin Borgman
The forge command from the forge distribution crashes on startup
$ forge
Exception in thread "Thread-1" org.jboss.weld.exceptions.DeploymentException: WELD-001408 Unsatisfied dependencies for type [ProfileBuilder] with qualifiers [@Default] at injection point [[field] @Inject org.jboss.seam.forge.arquillian.container.GlassFish3Remote.builder]
at org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:270)
at org.jboss.weld.bootstrap.Validator.validateBean(Validator.java:106)
at org.jboss.weld.bootstrap.Validator.validateRIBean(Validator.java:129)
at org.jboss.weld.bootstrap.Validator.validateBeans(Validator.java:351)
at org.jboss.weld.bootstrap.Validator.validateDeployment(Validator.java:336)
at org.jboss.weld.bootstrap.WeldBootstrap.validateBeans(WeldBootstrap.java:396)
at org.jboss.weld.environment.se.Weld.initialize(Weld.java:88)
at org.jboss.forge.shell.Bootstrap$2.run(Bootstrap.java:92)
at java.lang.Thread.run(Thread.java:680)
$
Because Alpha4 crashed this way I tried to build the distribution myself from the githup head release. After installing this version, same error
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[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
[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