[forge-issues] [JBoss JIRA] (FORGE-2107) [ Introduction ] JBoss Forge

Daniel Cunha (JIRA) issues at jboss.org
Wed Oct 29 11:51:35 EDT 2014


    [ https://issues.jboss.org/browse/FORGE-2107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13015886#comment-13015886 ] 

Daniel Cunha edited comment on FORGE-2107 at 10/29/14 11:51 AM:
----------------------------------------------------------------

That's a quote of the "Continuous Enterprise Development in Java" Book. 
I added this part on text: and integration with some IDE
I think that a good initial proposal.

{code}
JBoss Forge
 
If you’ve spent any time developing Java EE–based projects (or any nontrivial application,
for that matter!), you’ve likely invested a good amount of energy in creating the
project layout, defining dependencies, and informing the build system of the relevant
class paths to be used in compilation and execution. Although Maven enables us to
reduce that load as compared with undertaking project setup manually, there’s typically
quite a bit of boilerplate involved in the pom.xml defining your requirements.

JBoss Forge offers “incremental project enhancement for Java EE.” Implemented as a
command shell and integration with some IDE, Forge gives us the ability to alter project files and folders. 

- Some concrete tasks we might use Forge to handle are:
  * Adding Java Persistence API (JPA) entities and describing their model
  * Configuring Maven dependencies
  * Setting up project scaffolding
  * Generating a view layer, reverse-engineered from a domain model
  * Deploying to an application server

Because Forge is built atop a modular, plug-in-based architecture, it’s extensible to additional
tasks that may be specific to your application.
Overall, the goal of Forge is to ease project setup at all stages of development, so we’ll
be employing it in this text to speed along the construction of our example
{code}


was (Author: danielcunha):
That's a quote of the "Continuous Enterprise Development in Java" Book. 
I added this part on text: and integration with some IDE
I think that a good initial proposal.

{code}
JBoss Forge
 
If you’ve spent any time developing Java EE–based projects (or any nontrivial application,
for that matter!), you’ve likely invested a good amount of energy in creating the
project layout, defining dependencies, and informing the build system of the relevant
class paths to be used in compilation and execution. Although Maven enables us to
reduce that load as compared with undertaking project setup manually, there’s typically
quite a bit of boilerplate involved in the pom.xml defining your requirements.

JBoss Forge offers “incremental project enhancement for Java EE.” Implemented as a
command shell and integration with some IDE, Forge gives us the ability to alter project files and folders. 

- Some concrete tasks we might use Forge to handle are:
  * Adding Java Persistence API (JPA) entities and describing their model
  * Configuring Maven dependencies
  * Setting up project scaffolding
  * Generating a view layer, reverse-engineered from a domain model
  * Deploying to an application server

Because Forge is built atop a modular, plug-in-based architecture, it’s extensible to additional
tasks that may be specific to your application.
Overall, the goal of Forge is to ease project setup at all stages of development, so we’ll
be employing it in this text to speed along the construction of our 
{code}

> [ Introduction ] JBoss Forge
> ----------------------------
>
>                 Key: FORGE-2107
>                 URL: https://issues.jboss.org/browse/FORGE-2107
>             Project: Forge
>          Issue Type: Sub-task
>          Components: Documentation
>            Reporter: Daniel Cunha
>            Assignee: Daniel Cunha
>




--
This message was sent by Atlassian JIRA
(v6.3.1#6329)



More information about the forge-issues mailing list