Every aspect of CAS can be controlled byĪdding, removing, or modifying files in the overlay it’s also possible and indeed common to customize the behavior ofĬAS by adding third-party components that implement CAS APIs as Java source files or dependency references. Src/main/webapp/WEB-INF/view/jsp/default in the Maven WAR overlay project.
Src/main/webapp/WEB-INF/spring-configuration, the latter by modifying JSP and CSS files under The first two are controlled by modifying Spring XML configuration files under The following list of CAS components are those most often customized by deployers: The output of a Maven WAR overlay build is a cas.war file that can be deployed on a Java servlet container likeĪ simple Maven WAR overlay project is provided for reference and study: The list of bundle locations (mvn, http, file, … URLs) to deploy.CAS installation is a fundamentally source-oriented process, and we recommend aĬustomizations such as component configuration and UI design. Default value: falseĭefine if deploy uses the current Maven project artifact (in the case of the project is a bundle project).
Default value: karaf-rootĭefine if the deployment is done via SSH or via JMX. The delay (in second) to wait before trying to connect to the Karaf instance. The number of attempts to connect to the running Karaf instance. The key file to use to connect to the running Karaf instance.
MAVEN INSTALL PLUGIN SKIP PASSWORD
The password to connect to the running Karaf instance. The username to connect to the running Karaf instance. Hostname or IP address of the running Karaf instance. At least, is does not work on WinXP + NTFS, so do not include them for now.
MAVEN INSTALL PLUGIN SKIP WINDOWS
Symbolic links are not very well supported by windows Platform.
MAVEN INSTALL PLUGIN SKIP ZIP
Use symbolic links in tar.gz or zip archives. If supplied, the classifier for the artifact when attached. Whether to attach the resulting assembly to the project as an artifact.
Switches creation of *.tar.gz artifact on or off. Switches creation of *.zip artifact on or off. Whether to mark transitive dependencies' with dependency="true".īase directory used to overwrite resources in generated assembly after the build (resource directory). Whether to mark dependencies' in the runtime scope with dependency="true". If true, the src/main/history/dependencies.xml file will be overwritten if it has changed. If true, added and removed dependencies are shown in target/history. Whether to fail on changed dependencies (false, default) or warn in the build output (true). Whether to record dependencies in src/main/history/dependencies.xml for change tracking. Whether to follow Maven transitive dependencies. This can be overridden by specifying the bundle in the source feature.xml with the desired startlevel. The start level for the bundles determined from Maven dependencies. If true, all features in these repositories are copied into the generated feature repository. If false, all features in these repositories become dependencies of the generated feature. Specifies processing of feature repositories that are (transitive) Maven dependencies. You can supply a feature descriptor to extend in src/main/feature/feature.xml.