Pull request #15: BLOSSOM-278 Filter out jcr:system eventsMerge in BLOSSOM/blossom from BLOSSOM-278 to master
* commit '832e02475d4d213dff06bcaa9cff8d5e325e3be7':
BLOSSOM-278 Filter out jcr:system events
Pull request #14: BLOSSOM-274 Rely on ContentAppDescriptor nature to trigger DialogFactoriesMerge in BLOSSOM/blossom from bugfix/BLOSSOM-274-create-dialogs-custom-content-apps to master
* commit 'dbdb5c521923eb9e7f463d7d3ed6db5102297663':
BLOSSOM-274 Rely on ContentAppDescriptor nature to trigger DialogFactories
BLOSSOM-274 Rely on ContentAppDescriptor nature to trigger DialogFactoriesso that blossom dialogs keep working on custom M5 apps, not just old/new Pages apps.
* Use newly introduced AppController#getCurrentAppContext instead of relying on current app-name
* Type-check against DefinitionsAppDescriptor (loosely), and both old/new ContentAppDescriptors
* Log on warning level about support yet-to-come for injection of context objects when in M6 content-apps.
* Fix used/...
Pull request #13: BLOSSOM-272 Skip dialog-decorator in all other apps except old/new Pages appsMerge in BLOSSOM/blossom from bugfix/BLOSSOM-271-disable-decorator-in-all-other-apps to master
* commit '7160183d517a3e7d3d4d0b822d313bd2ca52b90e':
Fix minor definition problem with Blossom's renderer
Infer 'blossom' module name when it cannot be split from @Template id value
BLOSSOM-272 Skip dialog-decorator in all other apps except old/new Pages apps
Infer 'blossom' module name when it cannot be split from @Template id valuei.e. when the id doesn't contain a colon.
Blossom uses a "fixed reference-id" strategy for both templates & dialogs, so this doesn't have impact on existing content (template ids) or config (dialog ids).
This rather comes in handy when introspecting definitions. In particuler the Definitions app's module filter data-provider requires non-null entries.
BLOSSOM-272 Skip dialog-decorator in all other apps except old/new Pages apps* This makes sure we don't invoke dialog/tab-factories e.g. in Definitions app
Pull request #12: BLOSSOM-269 Skip dialog factories invocations when DialogCreationContext is incompleteMerge in BLOSSOM/blossom from bugfix/BLOSSOM-269-skip-double-factory-invocation-old-pages-app to master
* commit '206ca03a13c22853fc00c4aaa756b0c7984063ad':
BLOSSOM-269 Adjust TemplateExporterTest pre-condition to have dialogs generated
BLOSSOM-269 Skip dialog factories invocations when DialogCreationContext is incomplete
BLOSSOM-269 Skip dialog factories invocations when DialogCreationContext is incomplete* Catch MgnlInstantiationException if AppController can't be fetched from given invocation context
* Don't let decorator fail with a dramatic NPE if dialog-factories were skipped, then actions should be skipped too
* Implement compatibility checks for pages app as a standalone predicate; easy to remove later on.
* Test decorator usage in old vs. new Pages apps (and out of app context too)
* Te...
Pull request #11: BLOSSOM-267: debug changed to infoMerge in BLOSSOM/blossom from BLOSSOM-267 to master
* commit 'a65a0e0308ae91cbba9c8726aea59df54f543e1a':
BLOSSOM-267: revised code for suggestions
BLOSSOM-267: debug changed to info
Pull request #10: BLOSSOM-261 Use site-aware renderer wrapper and adjust for Magnolia 6.2 compatibilityMerge in BLOSSOM/blossom from bugfix/BLOSSOM-261-use-site-aware-renderer-wrapper to master
* commit 'a7983bc04e1c8fa20fc5ec5207484a3e23341d37':
Bump Blossom version to 3.4
BLOSSOM-261 Implement a FactoryBean for simple FreemarkerTemplateViewRenderer
Log dialog and URI mapping registrations on info level
BLOSSOM-257 Make dialog factories forward-compatible with Magnolia 6.2
BLOSSOM-25...
BLOSSOM-261 Implement a FactoryBean for simple FreemarkerTemplateViewRenderer* since its constructor now injects Magnolia's FreemarkerHelper and RenderingEngine, which are otherwise not exposed to Spring by default
* Make the SiteAware factory extend it with only the SiteAwareRendererWrapper facility
BLOSSOM-257 Make dialog factories forward-compatible with Magnolia 6.2* Make BlossomDialogDefinitionProvider#get idempotent
* Extract definition generation (invoking factories) to a DefinitionDecorator
* Register the decorator along with definitions by code
* Add test case for field generation via TemplateExporter
Note: this provides support for simple dialogs configured by code, however there are still certain objects that the old BlossomFormDialogPresenter use...
BLOSSOM-257 Naively port template and dialog exporters to use the new DialogDefinitionRegistry* migrate to newer interfaces from UI Framework (non-compatibility)
* but keep registering old-style compatibility dialogs for good measure
BLOSSOM-261 Replace usage of deprecated SiteAwareFreemarkerRenderer extension with site-aware wrapper* Deprecate `SiteAwareFreemarkerTemplateViewRenderer`, now equivalent to the `FreemarkerTemplateViewRenderer` and kept only for backward compatibility.
* Let the FactoryBean do the wrapping of `FreemarkerTemplateViewRenderer` with `SiteAwareRendererWrapper` and generalize generic typing to the `Renderer` interface
* Make use of newly introduced wrapping by passing an explicit renderer instance ...
Merge pull request #9 in BLOSSOM/blossom from task/BLOSSOM-259 to master* commit '51b4ee8ea6b5980aff57637c314ce11cef0eeeea':
BLOSSOM-259 Upgrade to magnolia 6.1
Revert "BLOSSOM-246 Bump Magnolia version to 6.2 and module version to next major 3.4"* No reason to create a new major version. Removal of Content API doesn't rely on some 6.2 specific classes
This reverts commit 133506bb03d2bf5ed7b581519d92bf96e4a3281a.
Merge pull request #8 in BLOSSOM/blossom from BLOSSOM-246 to master* commit '20cf071a51f4c3c15c341482aa45503542145e12':
QA add Clover threshold
BLOSSOM-246 Remove deprecated classes and leftovers of Content API
BLOSSOM-246 Bump Magnolia version to 6.2 and module version to next major 3.4
BLOSSOM-246 Remove deprecated classes and leftovers of Content API* deprecated since 2013 and replaced with javax.jcr.Node support
* adapt tests where needed
