The following comment has been added to this issue:
Author: Ate Douma
Created: Thu, 10 Jun 2004 5:19 AM
Body:
Scott,
What build.properties settings are you using with the plugin?
I've looked in the jelly script and it looks like you introduced a lot of new/renamed
properties unlike those defined in
http://portals.apache.org/jetspeed-2/getting-started.html and/or
http://portals.apache.org/jetspeed-2/database.html.
I don't mind using different properties but I think we should agree on one common set
so I don't have to define everything 3 or more times.
I didn't have much succes yet with jetspeed2:build.portal or jetspeed2:deploy.portal.
I gave up (for now, I don't have the time today) after I saw I needed too many
changes/fixes to get it running. Were you able to run these and build/deploy a
customized jetspeed?
I certainly would like to see this working soon.
What I need is the following: build/deploy a customized J2 using a project which
*ONLY* contains modified/added resources. The default J2 war and other dependencies
should be retrieved from the maven repository (local).
If this is possible I can use it to quickly setup developement environments for
portlet developers. They don't need and should not need building J2 themselves.
---------------------------------------------------------------------
View this comment:
http://issues.apache.org/jira/browse/JS2-58?page=comments#action_36013
---------------------------------------------------------------------
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: Thu, 10 Jun 2004 5:19 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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
