"CMS7-7080: prepare for next development iteration
"CMS7-7080: prepare release hippo-packages-2.25.02-iteration-6
"CMS7-7080: prepare for next development iteration
"CMS7-7080: prepare release hippo-packages-2.25.02-iteration-4
CMS7-7080 bump to new sprint tag versions
"CMS7-7080: prepare for next development iteration
"CMS7-7080: prepare release hippo-packages-2.25.01-iteration-3
REPO-753 remove deprecated updater engine module
CMS7-16: removed wfdropbox repository addon, it no longer exists
"CMS7-7080: prepare for next development iteration
"CMS7-7080: prepare release hippo-packages-2.25.00-alpha
CMS7-6973:prepare for next development iteration
CMS7-6961: prepare for next development iteration
CMS7-6961: prepare release hippo-packages-2.24.01
CMS7-6812: corrected license headers
CMS7-6704: prepare for next development iteration
CMS7-6704: prepare release hippo-packages-2.24.00
CMS7-6554 don't include repository upgrade module by default
CMS7-6531 REPO-496 move faceted date addon into core
CMS7-16: trivial tasks - drop buildnumber-maven-plugin usage
CMS7-6455: publication workflow and brokenlinks have been merged with cms and repository projects
CMS7-6316 - prepare for next development iteration
CMS7-6316 - prepare release hippo-packages-2.23.04-alpha
CMS7-6303 get rid of cms war overlays: xinha and skin are now loaded from the classpath
CMS7-5870: Use the jax-rs channel manager service in the channel manager user interface - hst-api and hst-commons should not be in the shared library anymore
CMS7-5884:prepare for next development iteration
CMS7-5884:prepare release hippo-packages-2.23.01-alpha
CMS7-5786: use the updated cms bundling The package-app-dependencies now also include the cms configuration. While not necessary for running a site against the repository, it does consolidate the 'repository' concept. I.e. it is always the same, whether the cms frontend application is running or not.
CMS7-5821:prepare for next development iteration
CMS7-5821:prepare release hippo-packages-2.23.00-alpha
CMS7-5780: prepare packages trunk for Hippo CMS 7.8 development
CMS7-5780: prepare for next development iteration
CMS7-5780: prepare release hippo-packages-2.22.01
CMS7-5735: prepare for next development iteration
CMS7-5735: prepare release hippo-packages-2.22.00
CMS7-5667:prepare for next development iteration
CMS7-5667:prepare release hippo-packages-2.21.08-alpha
CMS7-5667:prepare for next development iteration
CMS7-5667:prepare release hippo-packages-2.21.07-alpha
CMS7-5622: use new dependencies
CMS7-5573:prepare for next development iteration
CMS7-5573:prepare release hippo-packages-2.21.05-alpha
CMS7-5550:prepare for next development iteration
CMS7-5550:prepare release hippo-packages-2.21.04-alpha
CMS7-5527:prepare for next development iteration
CMS7-5527:prepare release hippo-packages-2.21.03-alpha
CMS7-5483:prepare for next development iteration
CMS7-5483:prepare release hippo-packages-2.21.02-alpha
RDB-70: broken links dependencies as default
CMS7-5361:prepare for next development iteration
CMS7-5361:prepare release hippo-packages-2.21.01
CMS7-5302:prepare for next development iteration
CMS7-5302:prepare release hippo-packages-2.21.00
CMS7-5269: revert previous commit Next release is intended to be 2.22.00, to be part of Hippo CMS 7.6.1.
CMS7-5269: reset version number of packages themselves too
CMS7-5241:prepare for next development iteration
CMS7-5241:prepare release hippo-packages-2.20.00
CMS7-5181:prepare for next development iteration
CMS7-5181:prepare release hippo-packages-2.19.03
CMS7-5137: major poms cleanup - removing all other dependency (re)configurations for those already defined as provided in cms7-project (servlet-api, jcr, jdo2, geronimo-jta)
CMS7-5137: poms cleanup and CMS7-5173: remove hippo-packages quickstart and cms-test modules
CMS7-5102 use version property names that are consistent with release pom
CMS7-5132:prepare for next development iteration
CMS7-5132:prepare release hippo-packages-2.19.02
CMS7-5081:prepare for next development iteration
CMS7-5081:prepare release hippo-packages-2.19.00
CMS7-5079 buildnumber plugin definition and configuration is now in project pom
CMS7-4887: use cms dependencies project
HREPTWO-4856: include cms upgrade module by default
HREPTWO-4795: bump version to 2.19.00-SNAPSHOT
HREPTWO-4795:prepare for next development iteration
HREPTWO-4795:prepare release hippo-packages-2.18.00RC1
HREPTWO-4767:prepare for next development iteration
HREPTWO-4767:prepare release Tag-HREPTWO-v2_17_02
HREPTWO-4753: yet another renaming of the reviewed actions workflow
HREPTWO-4739: Restructure svn, cleanup poms, and HREPTWO-4745: use groupId org.onehippo.cms7 - hippo-packages project
HREPTWO-4739: synchronizing project folder with artifact name (without the hippo- prefix)
HREPTWO-4739: copying hippo-ecm project trunk (based) folders to hippo-cms7
HREPTWO-4744: use correct dependencies
HREPTWO-4716: left over old artifact names
HREPTWO-4716: clean up names, use renamed publication workflow
HREPTWO-4716: rename artifacts publication workflow
HREPTWO-4627: artifacts have been renamed
HREPTWO-4662:prepare for next development iteration
HREPTWO-4653:prepare release Tag-HREPTWO-v2_17_00
HREPTWO-4653:prepare for next development iteration
HREPTWO-4653:prepare release Tag-HREPTWO-v2_17_00
HREPTWO-4653: use properties for cms, repo, addons These are fixated at the tag being set.
HREPTWO-4597: remove dependency to removed project
HREPTWO-4558: move servlets of repository in separate project
HREPTWO-4542: provided pom dependency project and resources-only project
This form allows you to request diffs between any two revisions of this file. For each of the two "sides" of the diff, enter a numeric revision.