portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From j...@apache.org
Subject [jira] Commented: (JS2-58) Jetspeed 2 Maven plugin
Date Fri, 11 Jun 2004 17:10:10 GMT
The following comment has been added to this issue:

     Author: Scott T Weaver
    Created: Fri, 11 Jun 2004 10:09 AM
       Body:
Now the only dependency the plugin has now is on HSQL.  I have made so that when the plugin
is built, portal/project.xml is copied to plugin-resources as portal_plugin.xml.

In in plugin.jelly we now use the <maven:pom> tag to create pom of the portal_project.xml
and then iterate through that when building the jar list for build.portal and for deploy.shared.

also, when building the plugin copyDb and copyPortalWebApp now copy straight into target/classes/plugin-resources
instead of into src/plugin-resources.

I am removing the dependency on plugin from portal as well.
---------------------------------------------------------------------
View this comment:
  http://issues.apache.org/jira/browse/JS2-58?page=comments#action_36042

---------------------------------------------------------------------
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: Open
   Priority: Major

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

   Assignee: Scott T Weaver
   Reporter: Scott T Weaver

    Created: Wed, 26 May 2004 12:13 PM
    Updated: Fri, 11 Jun 2004 10:09 AM

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


Mime
View raw message