I looked at http://nagoya.apache.org/jira/browse/JS2-74#action_36045 but I was not sure what I was supposed to do.
Where should I add these properties and what should I set them to for the generic out of the box J2. Bob -----Original Message----- From: Ate Douma [mailto:[EMAIL PROTECTED] Sent: Friday, June 18, 2004 10:59 AM To: Jetspeed Users List Subject: Re: Jetspeed 2 - Sample files for Windows, Tomcat 4.1 Bob Fleischman wrote: > Here is the body of the build.properties file in my > c:\eclipse\workspace\jakarta-jetspeed-2 > > catalina.home=c:\\Program Files\\Apache Group\\Tomcat 4.1 > catalina.version.major=4 > catalina.shared.lib=c:\\Program Files\\Apache Group\\Tomcat 4.1\\shared\\lib > deploy.war.dir=c:\\Program Files\\Apache Group\\Tomcat 4.1\\webapps > maven.repo.remote=http://www.bluesunrise.com/maven,http://www.ibiblio.org/ma > ven > > Also, I needed to modify the project.properties in the J2/portal directory > to change > deploy.war.dir=c:\\Program Files\\Apache Group\\Tomcat 4.1\\webapps > You should define those properties in ${USER_HOME}/build.properties as described on: http://portals.apache.org/jetspeed-2/getting-started.html On WindowsXP if thats what you are using it would be in: C:\Documents and Settings\<username>\build.properties Those properties override all others you define. You won't need to change the J2/portal/project.properties then anymore. > Everything works up through quickStart, however when I go to > localhost:8080/Jetspeed all I get is a blank screen. Did you read http://nagoya.apache.org/jira/browse/JS2-74#action_36045 ? Check your Tomcat console. There must be errors otherwise you wouldn't have a blank screen. Please try to be more explicit, I can't be much of help on "blank screen" reports... If its the deployment manager see also: http://nagoya.apache.org/eyebrowse/ReadMsg?listId=22&msgNo=15312 > > Bob > > Ps. A friend tried this today on a clean machine using Tomcat5 and got the > same blank screen. > > -----Original Message----- > From: Ate Douma [mailto:[EMAIL PROTECTED] > Sent: Friday, June 18, 2004 7:46 AM > To: Jetspeed Users List > Subject: Re: Jetspeed 2 - Sample files for Windows, Tomcat 4.1 > > > > LOMBART Christophe wrote: > > >>It seems the paramater "org.apache.jetspeed.portal.dir" is not mentionned > > into the getting-started.html which is used in the J2 plugin. > org.apache.jetspeed.portal.dir actually is derived from required property > org.apache.jetspeed.server.home which should point to ${tomcat.home}. > > Other undocumented properties I already know of are: > org.apache.jetspeed.catalina.version > org.apache.jetspeed.server.shared > org.apache.jetspeed.deploy.war.dir > > > >>I just added this parameter which point to the > > TOMCAT_HOME/webapps/jetspeed. Now, everything is ok when I deploy jetspeed > application into Tomcat. > >>I'm not sure if other parameters are still used. >> >> >>Christophe >> >> >>-----Original Message----- >>From: Ate Douma [mailto:[EMAIL PROTECTED] >>Sent: Fri 6/18/2004 1:21 PM >>To: Jetspeed Users List >>Cc: >>Subject: Re: Jetspeed 2 - Sample files for Windows, Tomcat 4.1 >>I've updated the logic for the J2 maven-plugin installation. >>Now, if the plugin hasn't been installed yet (or an older version) >>it will be installed instead of deployed. >>Checkout the new maven-plugin/maven.xml deploy-plugin goal. >> >>Note: their are a few new, yet undocumented, properties you have to >>provide in your ${USER_HOME}/build.properties to get portlets >>in the current version of J2 properly deployed. >>You can read about it here: >> http://nagoya.apache.org/jira/browse/JS2-74#action_36045 >> >>I will see if I can properly update/fix today the build.properties >>definitions and the instructions in >> http://portals.apache.org/jetspeed-2/getting-started.html >> >>Ate Douma wrote: >> >> >>>David Sean Taylor wrote: >>> >>> >>> >>>>On Jun 17, 2004, at 4:33 PM, Bob Fleischman wrote: >>>> >>>> >>>> >>>>>I am trying to build Jetspeed 2 from source using the steps in >>>>>http://portals.apache.org/jetspeed-2/getting-started.html on a Window >>>>>XP PC. >>>>> >>>>>However it seems that the instructions differ slightly from the current >>>>>files. For example, they point at apache/tomcat5 in the >>>>>project.properties >>>>>files; the paths are in 'Linux Speak' ${USER_HOME}/build.properties, >>>>>which >>>>>turns out to be the build.properties file in the Jetspeed2 home dir; the >>>>>instructions say that catalina.home should point to $(CATALINA_HOME}/ >>>>>and in >>>>>the existing properties file it points to tomcat/Jetspeed; and >>>>>finally, the >>>>>build.properties files has references to Oracle. I found that I had to >>>>>remove those to get the project to build. >>>>> >>>>>When I try to deploy I am being stopped with >>>>> >>>>>BUILD FAILED >>>>>File...... C:\eclipse\workspace\jakarta-jetspeed-2\maven.xml >>>>>Element... maven:reactor >>>>>Line...... 485 >>>>>Column.... 40 >>>>>Unable to obtain goal [fullDeploy] -- >>>>>C:\eclipse\workspace\jakarta-jetspeed-2\portal\maven.xml:250:41: >>>>><attainGoal> No goal [jetspeed2:deploy] >>>>>Total time: 33 seconds >>>>>Finished at: Thu Jun 17 19:32:25 EDT 2004 >>>>> >>>>>I would be glad to write the Windows version if I could get >>>>>everything to >>>>>work. >>>> >>>> >>>> >>>>The document is not specific to any operating system >>>>You can always specify forward slashes in your paths in property >>>>files, and they will be interpreted correctly >>>>Make sure to edit your build.properties in your home directory >>>>These props will override the settings in the J2 project >>>>On Windows that can be found somewhere like c:\Documents and Settings\bob >>>> >>>>The error you are getting means that the plugin didn't get installed >>>>That was fixed recently. I built J2 yesterday on a clean system (empty >>>>local repo) and I didn't get that error >>>> >>> >>>I did a new build on a clean system yesterday and I can confirm this > > error. > >>>To solve this go to the J2/maven-plugin directory after the allBuild and >>>issue: >>> >>> maven plugin:install >>> >>>Then navigate back to J2/ and run fullDeploy. >>> >>>The plugin:install only has to be done once and it installs the plugin >>>in the >>>$MAVEN_HOME/plugins folder. It has *nothing* to do with the local >>>repository. >>> >>>I'll see if I can get this be done automatically after allBuild (but >>>only when >>>needed). It has been discussed last week but not fixed by anyone yet. >>> >>>Regards, >>> >>>Ate >>> >>> >>> >>>>--------------------------------------------------------------------- >>>>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] > > > > --------------------------------------------------------------------- > 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]
