Blossom
  1. Blossom

blossom

Public
AuthorCommitMessageCommit dateIssues
Federico GrilliFederico Grilli
8668de788d5[maven-release-plugin] prepare for next development iteration
Federico GrilliFederico Grilli
4764b5bb7c7[maven-release-plugin] prepare release magnolia-module-blossom-3.4.3
Federico GrilliFederico Grilli
8eb2d98a276Prepare 3.4.3 release
Federico GrilliFederico Grilli
350cd0e15b6[maven-release-plugin] prepare for next development iteration
Federico GrilliFederico Grilli
7dd10e253be[maven-release-plugin] prepare release magnolia-module-blossom-3.4.3-beta1
Federico GrilliFederico Grilli
f2d099ebdfbMPull 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 DialogFactoriesBLOSSOM-274
Mikaël GeljićMikaël Geljić
dbdb5c52192BLOSSOM-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/...BLOSSOM-274
Federico GrilliFederico Grilli
004eb6e7fec[maven-release-plugin] prepare for next development iteration
Federico GrilliFederico Grilli
5584ae10f3f[maven-release-plugin] prepare release magnolia-module-blossom-3.4.2
Mikaël GeljićMikaël Geljić
340f003bcc2MPull 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 apps2 Jira Issues
Mikaël GeljićMikaël Geljić
7160183d517Fix minor definition problem with Blossom's renderer* Drop the non-existing type property
Mikaël GeljićMikaël Geljić
ea70fe2c5c5Infer '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.
Mikaël GeljićMikaël Geljić
dd24ed4a24fBLOSSOM-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 appBLOSSOM-272
Federico GrilliFederico Grilli
fa0b95f5943[maven-release-plugin] prepare for next development iteration
Federico GrilliFederico Grilli
b515621c893[maven-release-plugin] prepare release magnolia-module-blossom-3.4.1
Federico GrilliFederico Grilli
7e7a3c53b20MPull 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 incompleteBLOSSOM-269
Mikaël GeljićMikaël Geljić
206ca03a13cBLOSSOM-269 Adjust TemplateExporterTest pre-condition to have dialogs generatedBLOSSOM-269
Mikaël GeljićMikaël Geljić
885a839473eBLOSSOM-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...BLOSSOM-269
Mikaël GeljićMikaël Geljić
14ca0ecb9afMPull 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 infoBLOSSOM-267
Richard GangeRichard Gange
a65a0e0308aBLOSSOM-267: revised code for suggestionsBLOSSOM-267
Federico GrilliFederico Grilli
e9bb76595a7[maven-release-plugin] prepare for next development iteration
Federico GrilliFederico Grilli
742f0c82460[maven-release-plugin] prepare release magnolia-module-blossom-3.4
Federico GrilliFederico Grilli
30643a53090Prepare 3.4 release
Federico GrilliFederico Grilli
d7da455661bUpdate to ppom 39
Richard GangeRichard Gange
0c80fdf8209BLOSSOM-267: debug changed to infoBLOSSOM-267
Sang Ngo HuuSang Ngo Huu
5dcd8f28ac8MPull 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...2 Jira Issues
Mikaël GeljićSang Ngo HuuMikaël Geljić
a7983bc04e1Bump Blossom version to 3.4* Align with higher Magnolia and site module baselines
Mikaël GeljićSang Ngo HuuMikaël Geljić
c042e5314c9BLOSSOM-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 facilityBLOSSOM-261
Mikaël GeljićSang Ngo HuuMikaël Geljić
9f2088e1c6cLog dialog and URI mapping registrations on info levelsimilar to template registrations
Mikaël GeljićSang Ngo HuuMikaël Geljić
c0c060027b6BLOSSOM-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
Mikaël GeljićMikaël Geljić
ff388732389BLOSSOM-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 measureBLOSSOM-257
Mikaël GeljićMikaël Geljić
bff67402895Disambiguate SiteFunctions constructor for tests* enters imaging dependency...
Mikaël GeljićMikaël Geljić
7fa7ef01049BLOSSOM-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 ...BLOSSOM-261
Mikaël GeljićMikaël Geljić
2b83e20c958Import Spring Framework BOM* Upgrade site version according to M6.1 version * Reorder oddly-placed dep scope/types
Mikaël GeljićMikaël Geljić
c3d03000840Move POM's build section down
Milan DivilekMilan Divilek
8632a7710dc[maven-release-plugin] prepare for next development iteration
Milan DivilekMilan Divilek
b1739ba867a[maven-release-plugin] prepare release magnolia-module-blossom-3.3.1
Milan DivilekMilan Divilek
9bf5efa1512Update to parent pom 38
Jorge FrancoJorge Franco
99807fa747fMMerge pull request #9 in BLOSSOM/blossom from task/BLOSSOM-259 to master* commit '51b4ee8ea6b5980aff57637c314ce11cef0eeeea': BLOSSOM-259 Upgrade to magnolia 6.1BLOSSOM-259
Jorge FrancoJorge Franco
51b4ee8ea6bBLOSSOM-259 Upgrade to magnolia 6.1BLOSSOM-259
Federico GrilliFederico Grilli
02fe0582008Revert "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.BLOSSOM-246
Federico GrilliFederico Grilli
9fa54e9b22fBLOSSOM-246 QA Remove Content API usage which got away with IntelliJ code inspectionBLOSSOM-246
Federico GrilliFederico Grilli
c4dce4f86c2MMerge 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.4BLOSSOM-246
Federico GrilliFederico Grilli
20cf071a51fQA add Clover threshold
Federico GrilliFederico Grilli
72867b6761aBLOSSOM-246 Remove deprecated classes and leftovers of Content API* deprecated since 2013 and replaced with javax.jcr.Node support * adapt tests where neededBLOSSOM-246
Federico GrilliFederico Grilli
133506bb03dBLOSSOM-246 Bump Magnolia version to 6.2 and module version to next major 3.4BLOSSOM-246
Federico GrilliFederico Grilli
599ed9ac878[maven-release-plugin] prepare for next development iteration
Federico GrilliFederico Grilli
a9851a24c23[maven-release-plugin] prepare release magnolia-module-blossom-3.3
Federico GrilliFederico Grilli
3314c275c68Update to latest ppom v37
Robert ŠiškaRobert Šiška
6c39b30a078MMerge pull request #7 in BLOSSOM/blossom from ~RSISKA/blossom:BLOSSOM-256-blossom-not-working-on-magnolia-6.0 to master* commit 'b043fa4a94a87d890d25093febe80384c42300ed': BLOSSOM-256 remove JSP renderer BLOSSOM-256 Raise dependency to spring 5.1.9, adapt the tests BLOSSOM-256 Raise dependency to main 6.0, adapt the testsBLOSSOM-256