[jira] Commented: (JS2-58) Jetspeed 2 Maven plugin

[ji...@apache.org]

The following comment has been added to this issue:

     Author: Scott T Weaver
    Created: Thu, 3 Jun 2004 8:01 PM
       Body:
The Jetspeed 2 maven plugin has the current functionallity:

1.  Allows developers to Deploy/Undeploy porlet app under a single project to the portal. jetspeed2:deploy and jetspeed2:undeploy
  3 entries are required in project,props:
   # Name of the portlet app name.  Will be deployed to Tomcat using 
   # this value
   org.apache.jetspeed.portlet.app.name=Tutorial_App
   # path to the war to deploy, file name must match the value of
   # maven.war.final.name
   org.apache.jetspeed.portlet.war= target/tutorial.war
   # You don't have to set this but it does help knowing exactly
   # what the war file name will be
   maven.war.final.name=tutorial.war 

2. Allows developers to easily extend the portal by building a structure that matches the jetspeed 2 webapp structure.  Any files created by the user will overwrite the jetspeed 2 defaults.
   1 entry in project.properties:
   # path to the war to deploy, file name must match the value of
   # maven.war.final.name
   org.apache.jetspeed.portlet.war= target/jetspeed.war

   jetspeed2:build.portal merges default J2 with user defined webapp structure.
   jetspeed2:deploy.portal deploys the portal to tomcat.  This requires the same settings defined in http://portals.apache.org/jetspeed-2/getting-started.html

3. Easy RDBMS initialization via the jetspeed2:db.create goal

You will need to manually build the plugin by 
1. cd maven-plugin
2. maven plugin:deploy

I highly suggest you do an allClean allBuild BEFORE building the plugin.

Now this is really kewl ;)

This plugin is useable WITHOUT having to check out Jetspeed 2 since contains the webapp structure, SQL scripts and retrieves all of the deps to run jetspeed via project dependencies.

There is a caveat to this, that ALL of the jars generated by J2 must be available in the maven repsoitory, either local or remote.  The user must also have access to the pre-built plugin or the plugin is available via a remote repository (like how we get the torque plugin)
---------------------------------------------------------------------
View this comment:
  http://issues.apache.org/jira/browse/JS2-58?page=comments#action_35901

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/JS2-58

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: JS2-58
    Summary: Jetspeed 2 Maven plugin
       Type: New Feature

     Status: Unassigned
   Priority: Major

    Project: Jetspeed 2
 Components: 
             Project Build
   Versions:
             2.0-a1

   Assignee: 
   Reporter: Scott T Weaver

    Created: Wed, 26 May 2004 12:13 PM
    Updated: Thu, 3 Jun 2004 8:01 PM

Description:
I suggest that we start looking into creating a Maven plugin for Jetspeed 2 that will assist people in creating/deploying portlet applications.

The plug in should but not be limited to:

1. Taking a mavenized project and packaging it into war.
2. Deploying that application into a Jetspeed deployment
3. Allow users to extend the Jetspeed framework by allowing them to 
   merge in custom components and/or a custom assembly script.  It   
   should also allow custom deploying of J2 by specifying new component
   jars to include and allowing exclusion of any unused jars that are 
   part of the default J2 install.


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org