...
Code Block | ||
---|---|---|
| ||
<properties> . . . <CalendarPortlet.version>2.1.0<0-RC1</CalendarPortlet.version> . . . </properties> |
Step 2: Add a new submodule to uportal-portlets-overlay
- Add a new directory to uportal-portlets-overlay to represent your included portlet. This directory name is often the same as the artifact ID of the portlet. For our example, we will use the directory name "CalendarPortlet". Once the directory is created, create a new file named pom.xml at the root of the directory. This pom file should have a parent groupId and version equal to the groupId and version of the uportal-portlets-overlay directory for the portal you're building in. It's often easiest to set the artifactId for the new submodule to the same value as the portlet you're including.
In this example, we're including the Calendar Portlet in uPortal 4.0.4.
...
Info | ||
---|---|---|
| ||
Using the example above, your resulting maven overlay structure would resemble the following:
|
2. Now, include CalendarPortlet in the module list under uportal-portlets-overlay/pom.xml
Code Block | ||||
---|---|---|---|---|
| ||||
....
<name>uPortal Portlets</name>
<description>Parent package for portlets deployed with uPortal.</description>
<modules>
<module>BookmarksPortlet</module>
<module>CalendarPortlet</module>
<module>cas</module>
<module>cas-proxy-test-portlet</module>
<module>email-preview</module>
<module>FunctionalTestsPortlet</module>
<module>jasig-widget-portlets</module>
<module>pluto-testsuite</module>
<module>NewsReaderPortlet</module>
<module>SimpleContentPortlet</module>
<module>WeatherPortlet</module>
<module>WebProxyPortlet</module>
</modules>
<build>
.... |
Step 3: Add the portlet to uportal-ear/pom.xml
...