Paul Farnan wrote:
With respect to the windows configuration I had to also add the property:
"org.apache.jetspeed.portal.dir=${org.apache.jetspeed.deploy.war.dir}/jetspeed"
to my build.properties file. When I used the command "maven quickStart" it was putting
the .war files into an unspecified location (D:\jetspeed\WEB-INF\deploy). I had to copy these
files to the correct location to get the jetspeed site up and running. However, once I modified
the build.properties file to include the above definition it worked fine.
Did you have this problem before or after I cleaned up the maven properties configuration and changed the maven
requirement to 1.0-rc3 (yesterday, see: http://nagoya.apache.org/eyebrowse/ReadMsg?listId=22&msgNo=15414).
I certainly don't need this property defined. It is used by the J2 maven-plugin which
defines as default value
for it:
org.apache.jetspeed.portal.dir=${org.apache.jetspeed.deploy.war.dir}/${org.apache.jetspeed.portal.name}
The org.apache.jetspeed.portal.name property is also defined by the plugin:
org.apache.jetspeed.portal.name=jetspeed
This leads to the same definition you used. If you have used the latest cvs head maybe
you should clear/delete
the plugin from your ${MAVEN_HOME}/plugins and ${MAVEN_HOME_LOCAL}/plugins and try
again.
Paul
-----Original Message-----
From: Bob Fleischman [mailto:[EMAIL PROTECTED]
Sent: 18 June 2004 17:37
To: 'Jetspeed Users List'
Subject: RE: Jetspeed 2 - Sample files for Windows, Tomcat 4.1
Thanks. I'm not sure exactly what the tipping point was (adding these
properties or amending the tomcat-users.xml) but now it works.
Some suggestions. It is now clear from the getting started page if Tomcat
should be running at any point. I found it must be stopped before the
quickStart. My friend was a bit confused by the instructions.
Also, I would suggest you include your build.properties file (since it is
Windows based) as an alternative sample on the CVS site.
Again, thanks for the help. Now I'm going to work with my friend trying to
make this work in Tomcat5.
Bob
-----Original Message-----
From: Ate Douma [mailto:[EMAIL PROTECTED]
Sent: Friday, June 18, 2004 12:07 PM
To: Jetspeed Users List
Subject: Re: Jetspeed 2 - Sample files for Windows, Tomcat 4.1
Bob Fleischman wrote:
Should the directory definitions have a trailing slash? The get starting
page shows them, however your example and the build.properties.sample page
do not.
No, they don't need them.
Below properties are directly from my build.properties (I'm on WindowsXP)
-----Original Message-----
From: Ate Douma [mailto:[EMAIL PROTECTED]
Sent: Friday, June 18, 2004 11:29 AM
To: Jetspeed Users List
Subject: Re: Jetspeed 2 - Sample files for Windows, Tomcat 4.1
And, make sure you define the following (yet undocumented) required
properties
in ${USER_HOME}/build.properties:
org.apache.jetspeed.catalina.version = ${catalina.version.major}
org.apache.jetspeed.server.home = ${catalina.home}
org.apache.jetspeed.server.shared =
${org.apache.jetspeed.server.home}/shared/lib
org.apache.jetspeed.deploy.war.dir =
${org.apache.jetspeed.server.home}/webapps
Ate Douma wrote:
Bob Fleischman wrote:
I looked at http://nagoya.apache.org/jira/browse/JS2-74#action_36045
but I
was not sure what I was supposed to do.
That comment addresses the requirement to define a user scott with
password scott
and role manager in tomcat-users.xml:
<?xml version='1.0' encoding='utf-8'?>
<tomcat-users>
<role rolename="manager"/>
<user username="scott" password="scott" roles="manager"/>
</tomcat-users>
I described this also in:
http://nagoya.apache.org/eyebrowse/ReadMsg?listId=22&msgNo=15312
I'm in the process (awaiting a positive vote from the other committers) to
simplify the whole properties configuration (depends on maven-1.0-rc3) and
also addresses the currently hard coded user configuration in
tomcat-users.xml.
If my proposal is accepted expect all this trouble to be over very soon.
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]
---------------------------------------------------------------------
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]
________________________________________________________________________
This email has been scanned for all viruses by MessageLabs Email
Security System.
________________________________________________________________________
________________________________________________________________________
This e-mail and any files transmitted with it are confidential and intended
solely for the use of the individual or entity to whom they are addressed.
If you are not the intended recipient, you are hereby notified that any
use or dissemination of this publication is strictly prohibited. If you
have received this e-mail in error, please notify us immediately,
then destroy this e-mail.
_______________________________________________________________________
This email has been scanned for all viruses by the Message Labs Email
Security System. For more information on a proactive email security
service working around the clock, around the globe, visit
http://www.messagelabs.com
http://www.performixtechnologies.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]
