I dont know if you are already aware but maven usually has three files that describe a project ---
1. Maven.xml file
======================== Start Maven.xml file ===================
<project default="tag:buildDev" xmlns:j="jelly:core" xmlns:deploy="deploy"
xmlns:ant="jelly:ant">
<goal name="deploy.portlet"
description="Builds the war file, and deploys it under jetspeed deploy directory.">
<attainGoal name="war"/>
<ant:echo>Deploying the war file to Jetspeed ...</ant:echo>
<ant:copy
file="${maven.build.dir}/${maven.war.final.name}"
tofile="${portlet.deploy.dir}/${maven.war.final.name}"
overwrite="true"/>
</goal>
<goal name="deploy.decorators"
description="Deploys TAG specific decorators to jetspeed">
<attainGoal name="create.decorator.variables"/>
<attainGoal name="deploy.layout.decorator"/>
<attainGoal name="deploy.portlet.decorator"/>
</goal><goal name="create.decorator.variables"
description="Create variables required by the deploy.decorators goal">
<j:set var="com.tagaudit.tagportal.layout.decorator.directory" value="${maven.src.dir}/webapp/WEB-INF/decorations/layout/html/tag"/>
<j:set var="com.tagaudit.tagportal.portlet.decorator.directory" value="${maven.src.dir}/webapp/WEB-INF/decorations/portlet/html/tag"/>
<j:set var="com.tagaudit.tagportal.layoutdecorator.filename" value="taglayoutdecorator.jar"/>
<j:set var="com.tagaudit.tagportal.portletdecorator.filename" value="tagportletdecorator.jar"/>
</goal>
<goal name="deploy.portlet.decorator"
description="Deploy the portlet decorator">
<ant:jar
basedir="${com.tagaudit.tagportal.portlet.decorator.directory}"
destfile="${portlet.deploy.dir}/${com.tagaudit.tagportal.portletdecorator.filename}"
overwrite="true"/>
</goal> <goal name="deploy.layout.decorator"
description="Deploy the layout decorator">
<ant:jar
basedir="${com.tagaudit.tagportal.layout.decorator.directory}"
destfile="${portlet.deploy.dir}/${com.tagaudit.tagportal.layoutdecorator.filename}"
overwrite="true"/>
</goal><goal name="deploy.psml"
description="Deploy the pAgEs directory into jetspeed. Unfortunately we will have to keep doing this till jetspeed can pick it up from the portlet war file.">
<ant:delete quiet="true" dir="${jetspeed.webinf.dir}/pages"/>
<ant:mkdir dir="${jetspeed.webinf.dir}/pages"/>
<ant:copy
todir="${jetspeed.webinf.dir}/pages"
overwrite="true">
<fileset dir="${maven.src.dir}/webapp/WEB-INF/pages" casesensitive="yes"/>
</ant:copy>
</goal>
<goal name="deploy.all"
description="Deployes the portal, decorators and the psml pages to appropriate directories">
<attainGoal name="deploy.portlet"/>
<attainGoal name="deploy.decorators"/>
<attainGoal name="deploy.psml"/>
</goal>
</project>
================= end maven.xml file ===================
2. project.properties
=============== start project.properties ==================
#Set tomcat home to deploy war file tomcat.home=C:/jakarta-tomcat-5.0.28
#Deploy portlet
jetspeed.webinf.dir=${tomcat.home}/webapps/jetspeed/WEB-INF/
portlet.deploy.dir=${jetspeed.webinf.dir}/deploy# Set up eclipse for the project maven.eclipse.output.dir=target/tagportal/WEB-INF/classes
==================== end project.properties ================
3. project.xml
This file doesnot have much specific to my project. you can pick up anyone from jetspeed and customize it
Of all the files that I have pasted here, the most important is maven.xml file. Take a look at all the "goals" defined in that file. And then the "tomcat.home" property in the project.properties file.
I would strongly suggest that read a little bit about maven and the way it works. That would greatly help.
Amit ----Original Message Follows---- From: "Geoff Hollingworth" <[EMAIL PROTECTED]> Reply-To: "Jetspeed Users List" <jetspeed-user@jakarta.apache.org> To: jetspeed-user@jakarta.apache.org Subject: RE: Best Way to start developing a portal Date: Fri, 25 Mar 2005 10:15:37 -0600
thank you so much.
i am new to this maven thing and the jetspeed deploy mechanisms.
is it possible for you to share with me your maven build.properties file that you have created to deploy your myportal files. if you could share anything else that you think would help me then that is also appreciated.
i would like to steal with pride if that's ok.
cheers
/geoff
From: "Shah Amit" <[EMAIL PROTECTED]> Reply-To: "Jetspeed Users List" <jetspeed-user@jakarta.apache.org> To: jetspeed-user@jakarta.apache.org Subject: RE: Best Way to start developing a portal Date: Fri, 25 Mar 2005 10:51:50 -0500
Hi Geoff,
I got this advise from David Sean Taylor, and it has really worked great for me.
I have a seperate directory where I have all my source for my portlet, decorators and stuff like that. And then I have my own maven goals in my project files which deploy these portlets, decorators and pages in jetspeed deploy directory.
c:\MyProjects\MyPortlet\src\xxxx etc. is where my source is.
And it gets deployed to c:\tomcat\webapps\jetspeed\deploy
And I always download jetspeed distribution to c:\jetspeed2\
This way whenever I want, I update my jetspeed distribution and deploy it. And then use my maven goals to deploy my psmls, portlets etc.
Hope this helps, Amit
----Original Message Follows---- From: "Geoff Hollingworth" <[EMAIL PROTECTED]> Reply-To: "Jetspeed Users List" <jetspeed-user@jakarta.apache.org> To: jetspeed-user@jakarta.apache.org Subject: Best Way to start developing a portal Date: Fri, 25 Mar 2005 09:44:53 -0600
Hi
I now have a succesful environment running on linux using the source from CVS.
I now will start to develop my own portal (skins, layout, portlets). I want to continue to take down the latest source code as I am doing this.
Can anyone recommend the best way i do this so i can easily download the new cvs updates while i am developing my own portal based on it?
thanks in advance
/geoff
--------------------------------------------------------------------- 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]
--------------------------------------------------------------------- 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]
