Cliff, If you stick to pure JSR168 portlet, then it should deploy fine any JSR168 complaint portal worth its salt. Once you start hooking into portal specific hooks/extensions then you are basically making it non portable.
As far as using Maven2, the portlet-archetype bug appears to have been finally been fixed, so you can generate the portlet archetype and test it in Pluto. Here is the announcement thread with usage: http://www.nabble.com/-ANN--Portlet-Archetype-1.0.1-Released-t3850761s177.ht ml cheers Mohan -----Original Message----- From: Cliff [mailto:[EMAIL PROTECTED] Sent: Sunday, June 03, 2007 9:16 PM To: [email protected] Subject: Portlet newbie wants to use Maven Hello all, I'm working on a new portlet system (based on Liferay) at my new job and I need information on development and testing of portlets. While I'm used to typical Java web-app development (servlets/JSPs) this is my first time with Portlets. From my limited understanding a portlet is similar to a servlet and is deployed in a war. Liferay offers an ext environment which includes a myriad of Ant builds with an Eclipse plugin and other stuff to help development. I want to develop/test our portlets external to this environment and I read about the Pluto portlet container. I'm thinking this would be an ideal tool for executing portlets in isolation of Liferay. My question is this. Can I develop portlets the same way I would a normal JSP/servlet app (using Maven2) and use Pluto to contain them for test and eyeball verification and then later deploy the same war file effortlessly? Is there some material I can look at that would help guide me? I apologize if my question sounds silly in any way as I am just now picking up on the portlet specification. Thanx in advance. Cliff Java/Linux from a hip-hop state of mind http://codeforfun.wordpress.com -- View this message in context: http://www.nabble.com/Portlet-newbie-wants-to-use-Maven-tf3862626.html#a1094 2589 Sent from the Jetspeed - User mailing list archive at Nabble.com. --------------------------------------------------------------------- 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]
