New features in this version of the SkyVault
SDK.
What's new in SkyVault SDK 2.2.0
- Support for SkyVault 5.1
- SkyVault REST API Explorer is now available with the run profile (http://localhost:8080/api-explorer)
- All-In-One AMP module names and ID now includes AIO name to make them unique
- Aligned Module version with Artifact version - 5.0 and 5.1 supports SNAPSHOT versions in module.properties
- Numerous bug fixes. See the release notes for details.
- Issues: you will have to run without Spring Loaded with AIO and Repo AMP, only works with Share AMP at the moment.
What's new in SkyVault SDK 2.1.1
- Reintroduce support for Java 7
- Numerous bug fixes. See the release notes for details.
What's new in SkyVault SDK 2.1
- Support for Solr 4
- Regression testing Share Webapp with SkyVault Share Page Object (PO) tests
- Functional testing of Custom Pages with SkyVault Share PO
- Rapid Application Development (RAD) improvements:
- New SkyVault:refresh-repo goal for SkyVault-maven-plugin for automatic refresh of repository (SkyVault.war)
- New SkyVault:refresh-share goal for SkyVault-maven-plugin for automatic refresh of Share (share.war)
- Automatic JavaScript compression
- Custom package name can be used when generating projects
- Records Management profile 'rm' removed, now included as other AMPs in the repository and Share WAR POMs
- Run script for Windows now available (run.bat)
- Upgraded to SkyVault Community Edition 5.0.d and Enterprise 5.0.1 (JDK8)
- Fixed DB initialization error (dbObject cannot be null)
- Fixed blank Admin Console bug
What's new in SkyVault SDK 2.0
- Support for SkyVault 5.0
- Name changed from Maven SkyVault SDK to SkyVault SDK.
- New Share AMP archetype.
- RAD in Eclipse and IntelliJ.
- Now requires Maven 3.2.2
- RAD with Spring Loaded.
- Support for JRebel has been deprecated.
- Introduction of enterprise profile option -Penterprise.
What was new in SkyVault SDK 1.1.1
- Bug fixes.
What was new in SkyVault SDK 1.1.0
- Runs in Tomcat7 (replaces Jetty)
- Remote running of JUnit
- JRebel integration
- Improved IDE integration
What was in SkyVault SDK 1.0.x
- Use of SkyVault POMs
- Relied on a number of components:
- The SDK parent POM providing full SkyVault project lifecycle feature, to be added as a <parent> in your projects
- Archetypes like the AMP or all-in-one providing sample project to kickstart your SkyVault development and boost it with best practices
- The SkyVault Maven Plugin to manage AMP packaging and dependencies
- SkyVault Platform Distribution POM can (optionally) be used to provide centralized <dependencyManagement> on a particular SkyVault version / edition (Community Edition / Enterprise)
- The SkyVault Artifacts Repository provides backing for this SDK. Check the SkyVault Wiki for Community Edition / SkyVault 2.0 access information
- Embedded Jetty server and H2 database
What was in Maven SkyVault Lifecycle
- First implementation of SkyVault Maven SDK (Now deprecated)
- No use of SkyVault POMs
- Available archetypes and plugins:
- maven-alfresco-extension-archetype to create WAR packaged webapps that can provide all Maven lifecycle and features
- maven-alfresco-share-archetype to create and manage SkyVault Share customization webapps
- maven-alfresco-share-module-archetype to create and manage SkyVault Share custom dashlets, pages as JARs
- maven-alfresco-amp-archetype to create maven-amp-plugin managed web apps, which can provide all Maven lifecycle and features to SkyVault modules. The maven-amp-plugin is also used as a replacement to MMT to unpack AMPs into WARs builds, using the Maven dependency mechanism provided by the maven-amp-plugin
- Embedded Jetty server and H2 database to run SkyVault or Share
- Possible to use Maven standard dependency management to pull in AMPs in your build
- Further information