It works fine. thanks Christian.
-----Original Message-----
From: Christian Voelker [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 19, 2007 6:30 PM
To: Jayan Chirayath Kurian
Cc: DSpace
Subject: Re: [Dspace-tech] Expose DSpace as Tomcat ROOT application (was
Re:First name, family name order)
> Hello,
>
> what I did is simply rename the the dspace.war in the
> build_wars target in the build.xml to ROOT.war (with
> uppercase letters). You can even edit this manually
> after doing your "ant update" and before copying the
> .war file to webapps. It gets unpacked to the right
> directory.
Am 19.07.2007 um 11:55 schrieb Jayan Chirayath Kurian:
> I mean
>
> <!--
> ============================================================= -->
> <!-- Build the .war
> files -->
> <!--
> ============================================================= -->
>
> <target name="build_wars"
> depends="compile"
> description="Build the .war files">
>
> could you please suggest.
Yes, go on, down the line. There is some clearly readable
structure in an ant file just as in any XML file. That is
what XML was designed for in the first place. The comments
are also a great help for understanding what is going on.
You are searching for the <war>-tag inside the <target>:
<!-- Build the .war files
-->
...
<target name="build_wars"
...
<!-- Build DSpace UI .war -->
...
<!-- Make sure jsp/local exists -->
...
<!-- Copy original JSPs, then copy localised versions on top -->
...
<!-- Build DSpace Web UI .war -->
<war destfile="build/dspace.war"
webxml="build/dspace-web.xml">
...
</war>
<!-- Build DSpace OAI-PMH .war -->
<copy file="etc/oai-web.xml"
...
<war destfile="build/dspace-oai.war"
webxml="build/oai-web.xml">
...
</war>
</target>
There are two of them, just as the two .war files created
for the frontend and the harvester, the first of them being
of interest here. The <war>-tag encloses other tags and
carries two attributes. The second attribute specifies
the webxml file to use and is named as such, but the
first one is called destfile for "destination file name".
This is the one you are looking for. You could have come
there just as easy by using your editors search function
searching for "dspace.war". Now do the following change:
old: <war destfile="build/dspace.war"
new: <war destfile="build/ROOT.war"
Thats all.
> Using a symbolic link is also fine but I doubt that
> it will work with Windows shortcuts. At least on
> MacOS X which is a full-fledged Unix system, Java makes
> a distinction between symbolic links created the Unix
> way (which are followed as intended) and so called Aliases
> which are the MacOS kind of shortcuts created from the
> Finder and which dont work with Java apps although they
> look completely the same from a Finder perspective
> (translate Finder to Windows Explorer for your under-
> standing).
>
> I believe my solution is kind of "dirty" if you are very
> nitty gritty, but it is simple and serves me well. I try
> not make many changes to configurations all over the
> system because I dont have them all under version control
> locally and want to stay able to move my installation
> to another machine quickly. This is why I prefer to
> make changes to build.xml (which is in my svn) as to
> changes in tomcats server.xml.
>
> Bye, Christian
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech
