Actually, I had to change both uportal-ear/pom.xml and
uportal-war/pom.xml for both methods to work correctly. Maybe we should
introduce a common variable for this one.
In uportal-ear/pom.xml:
<finalName>portal</finalName>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-ear-plugin</artifactId>
<version>${maven-ear-plugin.version}</version>
<configuration>
<modules>
<webModule>
<groupId>org.jasig.portal</groupId>
<artifactId>uportal-war</artifactId>
<bundleFileName>portal.war</bundleFileName>
<contextRoot>/portal</contextRoot>
</webModule>
...
In uportal-war/pom.xml:
<build>
<finalName>portal</finalName>
<filters>
<filter>${basedir}/../build.properties</filter>
</filters>
Eric Dalquist wrote:
> You should be able to change the context path in the context.xml file
> so it is /portal regardless of what the .WAR is named. I haven't
> completely tested this functionality out with the new build though so
> if that doesn't work for you we may have to look at other options.
> Part of the issue is there are two ways to deploy the uPortal WAR now.
> 'ant deploy-war' deploys the Maven generated WAR directly and 'ant
> deploy-ear' deploys the WAR from the packaged EAR. We have to make
> sure anything that changes the final name of the .war file is
> consistent for both methods.
>
> -Eric
>
> Tuyhang Ly wrote:
>>
>> Thanks Eric!
>>
>> If I wanted to change the context path from /uPortal to /portal, I
>> only have to change uportal-ear/pom.xml as below:
>>
>> <configuration>
>> <modules>
>> <webModule>
>> <groupId>org.jasig.portal</groupId>
>> <artifactId>uportal-war</artifactId>
>> <bundleFileName>uPortal.war</bundleFileName>
>> <contextRoot>/portal</contextRoot>
>> </webModule>
>>
>> Is this correct?
>>
>> Tuy.
>>
>> Eric Dalquist wrote:
>>> As of Tomcat 5.5 (maybe 5.0 actually) Tomcat support specifying the
>>> context specific config file in
>>> $TOMCAT_HOME/webapps/uPortal/META-INF/context.xml The format of the
>>> file internally is the same but this reduces the information the
>>> uPortal deployer needs about the destination Tomcat instance.
>>>
>>> -Eric
>>>
>>> Tuyhang Ly wrote:
>>>> Hi,
>>>>
>>>> I've updated my environment from up3 trunk and noticed that the
>>>> context file uPortal.xml is no longer being deployed to
>>>> $TOMCAT_HOME/conf/Catalina/localhost with either "ant deploy-ear"
>>>> or "ant initportal". Am I missing something here?
>>>>
>>>> Thanks,
>>>> Tuy.
>>>>
>>
>> --
>> You are currently subscribed to [email protected] as: [EMAIL
>> PROTECTED]
>> To unsubscribe, change settings or access archives, see
>> http://www.ja-sig.org/wiki/display/JSG/uportal-dev
--
Join your friends and colleagues at JA-SIG 2008 - "Higher Education Solutions:
The Community Source Way!"
April 27th - 30th, 2008 in St. Paul, Minnesota USA
Featuring CAS, DSpace, Fedora, Fluid, Internet2, Kuali, Sakai, uPortal, and
more!
Information/Registration at:
http://www.ja-sig.org/conferences/08spring/index.html
You are currently subscribed to [email protected] as: [EMAIL
PROTECTED]
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/uportal-dev
