Jetspeed 2
  1. Jetspeed 2
  2. JS2-793

Support deployment of jetspeed under a custom context name (e.g. ROOT) with the maven 1 jetspeed plugin


    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: 2.1.3
    • Fix Version/s: 2.1.3
    • Component/s: Deployment
    • Labels:


      The maven-1 jetspeed plugin currently uses the "org.apache.jetspeed.portal.artifactId" property both for generating a custom portal project artifactId and
      as the context Name under which the portal is deployed (logically, as maven uses the artifactId for naming the war file itself too).
      For deploying to the Tomcat ROOT context though this is not very optimal as naming the artifactId as such is not very informative and usually not desired.

      I'll provide a new optional plugin property, "org.apache.jetspeed.portal.contextName" which will still default to the value of the "org.apache.jetspeed.portal.artifactId" property,
      but which you can override in the to support using a different context name like ROOT (note: for Tomcat this needs to be specified in full capitals).

      The created artifact then can be named as desired for deploying to the (local or a remote) maven repository, but during deployment (e.g. j2:portal.deploy) the plugin will using the provided "org.apache.jetspeed.portal.contextName".


        Ate Douma created issue -
        Ate Douma made changes -
        Field Original Value New Value
        Resolution Fixed [ 1 ]
        Status Open [ 1 ] Resolved [ 5 ]
        Ate Douma made changes -
        Status Resolved [ 5 ] Closed [ 6 ]


          • Assignee:
            Ate Douma
            Ate Douma
          • Votes:
            0 Vote for this issue
            0 Start watching this issue


            • Created: