Jacek,
Please verify that you have these set in your build.properties...
ESPECIALLY the last one:
org.apache.jetspeed.project.home = c:/jetspeed-2
org.apache.jetspeed.portal.name=jetspeed
org.apache.jetspeed.portal.home = ${org.apache.jetspeed.project.home}
I had the same problem after taking my LINUX maven-1 setup that ommitted
the last setting to windows. Took me all day to day to figure out!
Maven-1 plugin strikes again!
HTH,
Randy
Jacek Wiślicki wrote:
Wiadomosc od Randy Watler z 2006-03-08 07:02 brzmiala:
Ok... so check your copy of the jetspeed-2.0.war file in your maven
repo... are the OJB configuration files in the war?
I have:
...
4865 Wed Feb 01 15:53:32 MST 2006
WEB-INF/classes/OJB-logging.properties
24033 Wed Feb 01 15:53:32 MST 2006 WEB-INF/classes/OJB.properties
37098 Wed Feb 01 15:53:32 MST 2006 WEB-INF/classes/repository.dtd
1274 Wed Feb 01 15:53:32 MST 2006 WEB-INF/classes/repository.xml
2115 Wed Feb 01 15:53:32 MST 2006
WEB-INF/classes/repository_database.xml
7286 Wed Feb 01 15:53:32 MST 2006
WEB-INF/classes/repository_internal.xml
...
Let's see if this is a deployment issue or a build issue first.
No, they are not included in my jetspeed.war either. I think that you
might be using the same local directory for SVN checkout for months.
Please, try downloading the current SVN version to an empty directory,
build it and deploy. I guess that some deployment directives for OJB
files were included in older SVN versions, but they are no longer
available (the problems didn't appear until I cleared my local files
and performed a new checkout to the empty dir). Is it possible?
Also, if you get horribly stuck, you can also try the maven2 build...
see the dev list details for information. Would like to know if it
fails as well.
I'll try maven 2 tonight.
Finally... are you sure that '_svn' is not configurable to '.svn'?
That seems like a horrible design decision if not IMHO.
I do not see any configuration options for this. When I upgraded to
version 1.3.x (a month ago or so) all my local SVN checkouts went
useless. I didn't know why, but this was probably because the new
version of TortoiseSVN wouldn't understand the former .svn dirs.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
