June 2011 - forge-dev - Jboss List Archives

[JBoss JIRA] Created: (SEAMFORGE-197) Running git-plugin on Windows executes Maven on a different drive letter

by George Gastaldi (JIRA)

Running git-plugin on Windows executes Maven on a different drive letter ------------------------------------------------------------------------ Key: SEAMFORGE-197 URL: https://issues.jboss.org/browse/SEAMFORGE-197 Project: Seam Forge Issue Type: Bug Affects Versions: 1.0.0.Alpha3 Environment: Windows 7 Reporter: George Gastaldi To reproduce this bug, Forge is installed on D:\Forge 1) Run "D:\Forge\bin\Forge.bat" 2) Run "forge git-plugin git://github.com/forge/plugin-arquillian.git" It will fail the build, looking for D:\Users\... when it should be using C:\Users\... Output is here: http://pastie.org/2001178 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
4
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-233) Beans plugin adds invalid jboss-javaee-6 spec dependency

by Lincoln Baxter III (JIRA)

Beans plugin adds invalid jboss-javaee-6 spec dependency -------------------------------------------------------- Key: SEAMFORGE-233 URL: https://issues.jboss.org/browse/SEAMFORGE-233 Project: Seam Forge Issue Type: Bug Reporter: Lincoln Baxter III Plugin omits the <type>pom</type>, which causes dependency resolution failure. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

3
4
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-228) Typos in the docs

by Jozef Hartinger (JIRA)

Typos in the docs ----------------- Key: SEAMFORGE-228 URL: https://issues.jboss.org/browse/SEAMFORGE-228 Project: Seam Forge Issue Type: Bug Components: Documentation Affects Versions: 1.0.0.Alpha4 Reporter: Jozef Hartinger Priority: Minor Fix For: 1.0.0.Beta1 forge-creating-basic-webapp.xml: spell check failed on 'Thusly' forge-plugin-dev.xml: spell check failed on 'likelty' forge-plugin-dev.xml: spell check failed on 'ugprade' -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

4
5
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-209) ***ERROR*** [scaffold from-entity] promptChoice() Cannot ask user to select from a list of nothing. Ensure you have values in your options list.

by Esteve Aviles (JIRA)

***ERROR*** [scaffold from-entity] promptChoice() Cannot ask user to select from a list of nothing. Ensure you have values in your options list. ------------------------------------------------------------------------------------------------------------------------------------------------ Key: SEAMFORGE-209 URL: https://issues.jboss.org/browse/SEAMFORGE-209 Project: Seam Forge Issue Type: Feature Request Components: Shell Affects Versions: 1.0.0.Alpha3 Environment: Windows 7 32 bit Jdk 6.0 Reporter: Esteve Aviles I get this error while trying: [forge-test] Customer2.java $ scaffold from-entity No scaffold type was provided, use Forge default? [Y/n] y ***ERROR*** [scaffold from-entity] promptChoice() Cannot ask user to select from a list of nothing. Ensure you have values in your options list. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

4
12
0 / 0

add-constraint command

by Ricardo Martinelli Oliveira

Hi, I'd like to know in what context add-constraint command can be used. I tried executing when I "cd" to the Entity attribute, but it didn't work. Thanks in advance, Ricardo

13 years, 6 months

2
1
0 / 0

[JBoss JIRA] Commented: (SEAMFORGE-23) Forge needs a de-centralized plugin distribution and repository system

by Dominik Obermaier (JIRA)

[ https://issues.jboss.org/browse/SEAMFORGE-23?page=com.atlassian.jira.plug... ] Dominik Obermaier commented on SEAMFORGE-23: -------------------------------------------- I think a good idea for this could be the Homebrew appraoch (https://github.com/mxcl/homebrew). They have a so called "formula" directory in their github project. Essentially they just are instructions how to download and build things. My idea for a Seamforge Plugin Directory would be the following: 1. Create a Github Project with Seamforge Plugin "Formula" 2. Every known Seamforge Plugin gets an own formula file. In this formula file, there is information about the plugin like name, description, download URL, authors,.... 3. When searching for plugins, seamforge checks out the github project and scans for formulas. (I do not know how the Homebrew guys implemented their mechanism, but we could check that out) Then the can display all the plugin information. 4. When a user wants to install a plugin, the installation instructions in the formula file will be followed by seamforge and it installs the plugin. This has several advantages: - We could provide information in the formula, which Maven artifact has to be downloaded and in which repository this plugin is located - We are not locked in to Maven, because a Plugin Developer could just release binaries of his/her plugin and Seamforge could download it via normal http download. - If there are snapshot versions of a plugin, then this could be described in the formula, too and the user can instruct seamforge to utilize maven and build the plugin from source. - We have a stable hoster for the index of the plugins. - Literally everyone can contribute plugin formulas via pull-requests. So if a plugin author wants to make his/her plugin public, he/she just writes the formula file and makes a pull request. And if this is just an alpha plugin, then the author does not have to care about releasing the plugin to a Maven repository, because seamforge could build the plugin (via maven) from source and install it. > Forge needs a de-centralized plugin distribution and repository system > ---------------------------------------------------------------------- > > Key: SEAMFORGE-23 > URL: https://issues.jboss.org/browse/SEAMFORGE-23 > Project: Seam Forge > Issue Type: Feature Request > Components: Brainstorming, Plugin API > Affects Versions: 1.0.0.Alpha1 > Environment: All > Reporter: Lincoln Baxter III > Priority: Critical > Labels: Maven > > There is no disputing the value of this type of feature, as has been shown with App-stores of all kinds. This would be relatively simple to implement as a Maven-based system, delegating all of the artifact resolution and dependency management to Maven. > Features Forge would need to provide: > 1) Built-in plugins and native APIs to search/install/remove/update plug-ins (easy using forge Resource APIs + Aether to add/remove JARs.) This internal plugin/commands could be called "forge" for simplicity > ------------------------------------------------------------------------------------------ > $ forge plugin-find prettyfaces > Forge found the following plugins in specified repositories: <--- notice the 'forgeplugin' classifier used to identify forge plugins from other artifacts. > * http://ocpsoft.com/repository ...... [prettyfaces] com.ocpsoft.pretty.faces:prettyfaces-forgeplugin:[... 3.1.0, 3.2.0, 3.2.1] > * http://repo1.maven.org/ .............. [prettyfaces] com.ocpsoft.pretty.faces:prettyfaces-forgeplugin:3.1.0 > $ forge plugin-install prettyfaces --version 3.1.0 > ***SUCCESS*** [prettyfaces] plugin was successfully installed. You will need to restart forge to see these changes. > $ forge plugin-list > Listing installed plugins: > * prettyfaces [3.1.0] > * forge-scaffold [1.0.0.Alpha1] > * forge-javaee6 [1.0.0.Alpha1] > * home-control [1.0.0.Alpha1] > $ forge plugin-remove prettyfaces > Are you sure you you want to remove the plugin(s) [prettyfaces] [Y,n]? Y > ***SUCCESS*** [prettyfaces] plugin was successfully removed. You will need to restart forge to see these changes. > ------------------------------------------------------------------------------------------ > 2) Plugin repository management (add/remove/edit/list current plugin repository targets.) > ------------------------------------------------------------------------------------------ > $ forge repo-list > Currently using the following plugin repositories: > * 1. https://repository.jboss.org/nexus/content/groups/public/ > * 2. http://ocpsoft.com/repository > * 3. http://example.com/forge/plugin-repository > $ forge repo-add http://jboss.org/forge/repository/ <-- These two will be KEY, we NEED THESE to happen > $ forge repo-add http://javaee.org/forge/repository/ > $ forge repo-list > Currently using the following plugin repositories: > * 1. https://repository.jboss.org/nexus/content/groups/public/ > * 2. http://ocpsoft.com/repository > * 3. http://example.com/forge/plugin-repository > * 4. http://jboss.org/forge/repository/ > * 5. http://javaee.org/forge/repository/ > $ forge repo-del 5 > ***SUCCESS*** removed repository [http://javaee.org/forge/repository/]. Plugins installed from this repository will no longer be auto-updated, and can be removed using [forge plugin-remove {plugin-id}] > ------------------------------------------------------------------------------------------ > 3) Auto-update functionality > Periodically search for updates to existing plugins (or search on request) - ask users if they would like to see a list of updates or perform an automated update / update individual plugins. > 4) A meta-data system of identifying compatible versions of plugins w/running version of forge. > Possibly need to create a maven packaging type and build plugin in order to facilitate this type of additional metadata and artifact resolution. (Or could require a <classifier>forgeplugin</classifier>. We already have the maven GAV (GroupId : ArtifactId : Version) information. Supplemented with this classifier, we could easily identify forge plugins from other artifacts in maven. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-238) Spring MVC Project

by Burr Sutter (JIRA)

Spring MVC Project ------------------ Key: SEAMFORGE-238 URL: https://issues.jboss.org/browse/SEAMFORGE-238 Project: Seam Forge Issue Type: Feature Request Reporter: Burr Sutter For those folks who prefer Spring proprietary APIs to Java EE spring-context spring-webmvc aspectjrt slf4j javax.inject servlet-api jsp-api jstl Maven Spring MVC controllers are also use for being endpoints for RESTful HTML5 clients - the Jackson library needs to be included for auto-JSON serialization. JAX-RS via RESTEasy is the other approach and works "out of the box" since JBoss AS6. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-237) Java EE6 Full Project (follows the EE6 full profile)

by Burr Sutter (JIRA)

Java EE6 Full Project (follows the EE6 full profile) ---------------------------------------------------- Key: SEAMFORGE-237 URL: https://issues.jboss.org/browse/SEAMFORGE-237 Project: Seam Forge Issue Type: Feature Request Reporter: Burr Sutter * Java EE6 Full (follows the EE6 full profile) HTML JavaScript Servlet 3.0 JSP 2.2 JSTL 1.2 JTA 1.1 JSF 2.0 - easy to add RichFaces4 CDI 1.0 JPA 2.0 Bean Validation 1.0 + EJB 3.1 JAX-RS 1.1 JAX-WS 2.2 JMS 1.1 Maven -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-236) Java EE 6 Web Project

by Burr Sutter (JIRA)

Java EE 6 Web Project --------------------- Key: SEAMFORGE-236 URL: https://issues.jboss.org/browse/SEAMFORGE-236 Project: Seam Forge Issue Type: Feature Request Reporter: Burr Sutter * Java EE6 Web (follows the EE6 web profile) HTML JavaScript Servlet 3.0 JSP 2.2 JSTL 1.2 JTA 1.1 JSF 2.0 - easy to add RichFaces4 CDI 1.0 JPA 2.0 Bean Validation 1.0 Maven -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-235) Basic Web Project

by Burr Sutter (JIRA)

Basic Web Project ----------------- Key: SEAMFORGE-235 URL: https://issues.jboss.org/browse/SEAMFORGE-235 Project: Seam Forge Issue Type: Feature Request Reporter: Burr Sutter * Basic Web Project HTML JavaScript CSS Servlet 3.0 JSP 2.2 JSTL 1.2 - easy to add RESTEasy and JPA Maven build support Easy to add jQuery/jQuery Mobile -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-dev June 2011