You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-dev@portals.apache.org by "Ate Douma (JIRA)" <je...@portals.apache.org> on 2007/10/24 02:38:50 UTC
[jira] Resolved: (JS2-793) Support deployment of jetspeed under a
custom context name (e.g. ROOT) with the maven 1 jetspeed plugin
[ https://issues.apache.org/jira/browse/JS2-793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ate Douma resolved JS2-793.
---------------------------
Resolution: Fixed
Implemented supporting both Tomcat 5.0.x and 5.5.x.
Note: the template tomcat context deployment descriptors (under src tree etc/conf/tomcat) have been adapted to support this too.
> Support deployment of jetspeed under a custom context name (e.g. ROOT) with the maven 1 jetspeed plugin
> -------------------------------------------------------------------------------------------------------
>
> Key: JS2-793
> URL: https://issues.apache.org/jira/browse/JS2-793
> Project: Jetspeed 2
> Issue Type: Improvement
> Components: Deployment
> Affects Versions: 2.1.3
> Reporter: Ate Douma
> Assignee: Ate Douma
> Priority: Minor
> Fix For: 2.1.3
>
>
> 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 build.properties 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".
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
Re: Jetspeed 2.2 Admin
Posted by David Sean Taylor <da...@bluesunrise.com>.
On Oct 23, 2007, at 6:22 PM, Suresh Kuppusamy wrote:
> Folks,
> There was a thread earlier with a list of enhancements for 2.2 and
> notably a rewrite of j2admin. Is there a preview site or a mockup
> of what the new admin would look like and a list of features.
> Appreciate any input.
>
We are just putting together some mockups. We are writing the j2-
admin portlets with Wicket components. Our goal is to make them more
extensible
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
Jetspeed 2.2 Admin
Posted by Suresh Kuppusamy <su...@bluenog.com>.
Folks,
There was a thread earlier with a list of enhancements for 2.2 and notably a rewrite of j2admin. Is there a preview site or a mockup of what the new admin would look like and a list of features. Appreciate any input.
Regards,
Suresh
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org