May 2011 - forge-dev - Jboss List Archives

[JBoss JIRA] Created: (SEAMFORGE-175) Arquillian plugin should prompt for Arquillian and junit version

by Paul Bakker (JIRA)

Arquillian plugin should prompt for Arquillian and junit version ---------------------------------------------------------------- Key: SEAMFORGE-175 URL: https://issues.jboss.org/browse/SEAMFORGE-175 Project: Seam Forge Issue Type: Enhancement Components: Blessed Plugins Reporter: Paul Bakker Assignee: Paul Bakker -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

2
3
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-173) Field plugin should work on bean classes

by Dan Allen (JIRA)

Field plugin should work on bean classes ---------------------------------------- Key: SEAMFORGE-173 URL: https://issues.jboss.org/browse/SEAMFORGE-173 Project: Seam Forge Issue Type: Feature Request Components: Blessed Plugins Affects Versions: 1.0.0.Alpha3 Reporter: Dan Allen The field plugin should be available for any Java bean class. Adding the field would add the associated getters and setters (or prompt for which ones to create). It should also be possible to add getters and setters for a field (or all fields) after the fact. We should also support creating a constructor from fields. This feature would drastically speed up prototyping coding (without having an IDE handy). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

2
1
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-179) An XML document parsed with the Forge XMLParser cannot be exported with XMLParser#toXML if it contains comments

by Kevin Pollet (JIRA)

An XML document parsed with the Forge XMLParser cannot be exported with XMLParser#toXML if it contains comments --------------------------------------------------------------------------------------------------------------- Key: SEAMFORGE-179 URL: https://issues.jboss.org/browse/SEAMFORGE-179 Project: Seam Forge Issue Type: Bug Components: Parsers / File Manipulation Affects Versions: 1.0.0.Alpha3 Reporter: Kevin Pollet When the {{XMLParser#parse}} method is called on a stream which contains comments, DOM creates a Node named "#comment" and the corresponding Node is created by Forge parser. After that, when the {{XMLParser#toXML}} method is called on the XML root node an exception is thrown. At serialization Forge parser tries to create a Node with name "#comment" by using the method {{Document#createElement}} (which is illegal and result in a {{DOMException#INVALID_CHARACTER_ERR}}) instead of calling the method {{Document#createComment}}. IMO, the same problem could happen with others specific nodes. Maybe Shrinkwrap descriptor project could have the same problem, but it needs further investigations... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

2
3
0 / 0

creating "pom" projects

by Tim Pedone

As part of implementing the ability to add dependencies based off the dependencyManagement section of a parent pom, it would be helpful for testing purposes (and likely for users as well) to be able to create a project of type "pom". I copied the NewProjectPlugin and used it to create a PomProjectPlugin. I removed the Java facet and set the packaging to "pom"; however, it seems that ProjectFactory.createProject() calls registerFacet() which attempts to add every facet (CDI, JEE, etc.) to the project. The CDI facet fails because the project is not a war or jar. Is that behavior correct (adding the CDI facet to all projects)?

12 years, 11 months

2
10
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-177) Arquillian plugin should support JSFUnit

by Paul Bakker (JIRA)

Arquillian plugin should support JSFUnit ---------------------------------------- Key: SEAMFORGE-177 URL: https://issues.jboss.org/browse/SEAMFORGE-177 Project: Seam Forge Issue Type: Feature Request Reporter: Paul Bakker Assignee: Paul Bakker -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-176) Arquillian plugin should have support different templates for test class generation

by Paul Bakker (JIRA)

Arquillian plugin should have support different templates for test class generation ----------------------------------------------------------------------------------- Key: SEAMFORGE-176 URL: https://issues.jboss.org/browse/SEAMFORGE-176 Project: Seam Forge Issue Type: Feature Request Components: Blessed Plugins Reporter: Paul Bakker In the Arquillian documentation there are several examples of tests: CDI, JPA, EJB, JMS etc. It would be useful to generate the test class according what kind of functionallity is tested. e.g. a JMS test should promt for the queue/connection jndi name and add it @resource annotations for it. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

1
1
0 / 0

Added Component in JIRA for "Blessed Plugins"

by Lincoln Baxter, III

Note: For all JIRAs related to "blessed" plugins located at http://github.com/forge please use the JIRA component "Blessed Plugins" when creating issues. Thanks, -- Lincoln Baxter, III http://ocpsoft.com http://scrumshark.com "Keep it Simple"

12 years, 12 months

1
0
0 / 0

Unit Test failures

by Tim Pedone

First off, I think Forge is totally cool. So much so, that I'd like to contribute in some way. So I've forked the repo in GitHub and am trying to build it but am getting a few unit test failures in RepositoryLookupTest.testResolveVersions() and a few others. In stepping through the code, it seems like the Aether code isn't working properly. I assume this must be something unique to my setup: MacOS 10.6 + JDK 1.6.0_24, Maven 3.0.3, JBoss Dev Studio 4.0. The tests fail on both the command line and in Dev Studio. Any ideas? Thanks, Tim

12 years, 12 months

5
12
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-171) Format code using an Eclipse formatting profile

by Dan Allen (JIRA)

Format code using an Eclipse formatting profile ----------------------------------------------- Key: SEAMFORGE-171 URL: https://issues.jboss.org/browse/SEAMFORGE-171 Project: Seam Forge Issue Type: Feature Request Components: Parsers / File Manipulation Affects Versions: 1.0.0.Alpha3 Reporter: Dan Allen Allow the user to specify an Eclipse formatting profile in the local configuration (~/.forge). When creating (or updating) Java files, use the Eclipse formatter (or alternative) to format the code using the formatting profile. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 12 months

1
0
0 / 0

going further with AST

by Dan Allen

Lincoln (and others interested), You may want to take a peak at the presentation from Google I/O 2011 on the GWT designer. The presenter, who I believe leads the projects, explains how they use the AST to keep the visual editor and code in sync down to inline strings in Java code. For one, it shows what is possible with an AST model. You may also be interested in contact him if you need ideas or hints as to how to do some of this in forge. It just struck me as something you should watch. Google I/O 2011: GWT + UI Designer: Enterprise Web UIs Made Easy! http://www.youtube.com/watch?v=kV5H3rGfqOE -Dan -- Dan Allen Principal Software Engineer, Red Hat | Author of Seam in Action Registered Linux User #231597 http://www.google.com/profiles/dan.j.allen#about http://mojavelinux.com http://mojavelinux.com/seaminaction

12 years, 12 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-dev May 2011