On Aug 12, 2004, at 7:09 AM, Randy Watler wrote:
I was describing how to develop portlet applications and resources, and pointing out that J2 separates portal from portlet application, something J1 did not.Scott,
Yes, I did find the jetspeed2:deploy.portal and related goals in the
Jetspeed2 Maven Plugin. The detail you provided fills open questions I had
about how it shoudl be used. However, David stated that this "merge" should
not be used with Jetspeed2 by design on a previous thread:
http://marc.theaimsgroup.com/?l=jetspeed-user&m=109222938119408&w=2
It appears that the live deployment strategy is preferred in general, but
that it may not cover everything that one would like to modify at this
point, (?). In this case, I am specifically asking about two kinds of
customization: PSML hacking and Component development. Apparently, Porlet
and decoration/layout are deployable now...
As you know, I am trying to document the "proper" way to develop a Jetspeed2
portal in an attempt to get some kind of tutorial off the ground. Of course,
I will follow whatever methodology the Jetspeed2 team prefers. David?
The goal is to develop resources separate from the portal, and to deploy and undeploy them separately.
From what I understand, what Scott is describing is how to setup an environment for developing components to use inside of J2.
This can be used by more advanced users to create a customized portal
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
