The following comment has been added to this issue:

     Author: Ate Douma
    Created: Fri, 11 Jun 2004 4:03 AM
       Body:
portal/maven.xml goal fullDeploy now uses the maven plugin for deployment.
For this, it needs access to the plugin which isn't defined as a dependency.
So, I added the plugin to the portal dependency list and it worked fine.

Once!

Now maven complains with a cycle dependency on jetspeed2:jetspeed.
The maven-plugin depends on jetspeed and jetspeed depends on the plugin.

I already committed the new dependency but removed it again because of this.

How are we going to resolve this? As it is now J2 cannot be deployed anymore!
---------------------------------------------------------------------
View this comment:
  http://issues.apache.org/jira/browse/JS2-58?page=comments#action_36024

---------------------------------------------------------------------
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 4:03 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]

Reply via email to