This project contains various Asset Factory Plugins that can be used within Cascade CMS. The project is organized with tags that correspond to specific Cascade CMS versions; if a plugin is present under a specific tag, it is compatible with that version of Cascade CMS. For example, the tag 7.4.x means that each plugin listed will work with Cascade CMS 7.4.1.
This project also utilizes Github Releases that correspond to specific Cascade CMS versions. Each release will contain a compiled JARs for each available plugin, a JAR containing all available plugins and a Zip file containing each individially compiled plugin.
To install compiled Asset Factory plugins:
- Shut down Cascade CMS
- Place the compiled JAR file(s) in
<Tomcat_Installation_Directory>/webapps/ROOT/WEB-INF/lib
within the Cascade CMS installation directory. - Restart Cascade CMS
- Navigate to Administration->Asset Factory Plugins
- In the Add a Plugin field, enter the fullet qualified Java class name of each plugin
- E.g.
com.hannonhill.cascade.plugin.assetfactory.AssetFieldsPlugin
- E.g.
- Click the Add Plugin button
To remove a custom plugin:
- Navigate to Administration->Asset Factory Plugins
- Click on the red X to remove the custom plugin
Prerequisites: Because this is an Maven-Eclipse project, both Eclipse and Maven must be installed.
- Create your new plugin class within the
com.hannonhill.cascade.plugin.assetfactory
package - Add any required dependencies to the Maven pom.xml file. If you need to install local .jar files, see the section below.
- Building:
- Within Eclipse
- Right-click the Project and go to Run As->Maven->Maven build...
- Type
clean package
in the Goals field and click Run
- Note: After building at least once, you can then use Run As->Maven->Maven build and choose the previous build setting from the configuration menu.
- From command line
- Navigate to the project
- Type
mvn clean package
- Within Eclipse
- Locate the compiled JAR file within the target directory
Recent versions of Maven no longer allow linking to internal dependencies via scope and systemPath.
Using the information provided in this article, we can avoid this issue by using the maven-installer-plugin to install the .jar into a local repository within the lib
directory.
Repeat the following for each .jar:
- Change into the
lib
directory - Install the .jar into the local repository using the maven-installer-plugin:
mvn install:install-file -Dfile=PATH_TO_FILE -DgroupId=GROUP_ID -DartifactId=ARTIFACT_ID -Dversion=VERSION -Dpackaging=jar -DgeneratePom=true -DlocalRepositoryPath=.
- Add the new dependency to the
pom.xml
file using the information from the previous step:
<dependency>
<groupId>GROUP_ID</groupId>
<artifactId>ARTIFACT_ID</artifactId>
<version>VERSION</version>
</dependency>