Modify local.runtime.properties to use Pluto (uncomment the Pluto lines) and use 'ant install-runtime' to install Pluto as test environment. Modify project.xml to install ccm into an other context as ROOT! libreccm may be a nice choice. Deploy and load-bundle as usual. Invoke http://localhost:8080/libreccm to operate CCM as usual. Invoke http://localhost:8080/pluto to operate Pluto, login as admin and use Pluto admin tool to add ContentItemJSRPortlet to the Pluto Portal page (displays currently a simple HelloWorld Text). git-svn-id: https://svn.libreccm.org/ccm/trunk@2652 8810af33-2d31-482b-a856-94f89814c4df |
||
|---|---|---|
| .. | ||
| AntelopeTasks_3.5.1.jar | ||
| README | ||
| ant-contrib.jar | ||
| ant-trax-1.7.1.jar | ||
| commons-lang-2.1.jar | ||
| jakarta-oro-2.0.4.jar | ||
| jsp-api.jar | ||
| servlet-api.jar | ||
| xalan.jar | ||
| xerces.jar | ||
| xercesImpl.jar | ||
| xercesSamples.jar | ||
| xml-apis.jar | ||
README
dev-lib/ set of files requirred by CCM build tools, and the ECDC tools chain (e.g. assembling the web.xml file or setting up the environment). e.g. ant, and probably in the test environment. Those files which are actually used are included in ccm.tools.lib.dir