Jeremy Ford wrote:
Anyone mind if I refactor some of the pam.deploy/undeploy goals to reduce copy/paste of the java forking?
+1
No. Did use it a lot when I was developing the Struts portlet Demo (doing undeploy/deploy in sequence all the time).
Also, I tried to do a pam.undeploy and got this:
[java] PAM Lifecycle Error: Lifecycle interface not supported by implementat ion: org.apache.jetspeed.tools.pamanager.FileSystemPAM [java] ERROR: PAM Lifecycle Error: Lifecycle interface not supported by impl ementation: org.apache.jetspeed.tools.pamanager.FileSystemPAM
Anyone see this?
It's been a more than month ago though so maybe the changes since then are the cause of it. Seems strange though because I don't remember seeing changes of that kind lately.
Jeremy Ford [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
