This is an automated email from the ASF dual-hosted git repository. danhaywood pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/isis.git
commit 774ab1be711042fe4513a8bf1c3a9e53335bbb65 Author: Dan Haywood <[email protected]> AuthorDate: Sun Oct 23 12:38:25 2022 +0100 ISIS-3260: renames 'ISIS' -> 'CAUSEWAY' in all .adoc files (excluding mignotes and relnotes) --- README.adoc | 2 +- .../ROOT/pages/antora-publish-procedure.adoc | 4 ++-- .../modules/ROOT/pages/applying-patches.adoc | 8 ++++---- .../modules/ROOT/pages/cutting-a-release.adoc | 4 ++-- .../modules/ROOT/pages/merging-a-pull-request.adoc | 22 +++++++++++----------- .../modules/ROOT/pages/policies/git-policy.adoc | 18 +++++++++--------- .../ROOT/pages/post-release-successful.adoc | 10 +++++----- .../conguide/modules/ROOT/pages/contributing.adoc | 16 ++++++++-------- .../conguide/modules/git/pages/about.adoc | 10 +++++----- .../docs/modules/support/pages/about.adoc | 2 +- .../ExceptionRecognizer_010-implementation.adoc | 2 +- .../WrapperFactory_020-examples-and-usage.adoc | 2 +- .../relnotes/modules/ROOT/pages/about.adoc | 2 +- .../modules/fun/pages/ui/object-layout.adoc | 2 +- .../ROOT/pages/hints-and-tips/svg-support.adoc | 4 ++-- 15 files changed, 54 insertions(+), 54 deletions(-) diff --git a/README.adoc b/README.adoc index 999085d159..600481f44f 100644 --- a/README.adoc +++ b/README.adoc @@ -302,6 +302,6 @@ The Apache Causeway http://causeway.apache.org[website] has lots of useful infor Or, you can just start coding using the https://github.com/apache/causeway-app-simpleapp[SimpleApp] starter app. -And if you need help or support, join our https://cwiki.apache.org/confluence/display/ISIS/Signing+up+to+Slack[ASF Slack channel] or our http://causeway.apache.org/support.html[mailing list]. +And if you need help or support, join our https://cwiki.apache.org/confluence/display/CAUSEWAY/Signing+up+to+Slack[ASF Slack channel] or our http://causeway.apache.org/support.html[mailing list]. diff --git a/antora/components/comguide/modules/ROOT/pages/antora-publish-procedure.adoc b/antora/components/comguide/modules/ROOT/pages/antora-publish-procedure.adoc index 5d2e601f32..6ea06198e8 100644 --- a/antora/components/comguide/modules/ROOT/pages/antora-publish-procedure.adoc +++ b/antora/components/comguide/modules/ROOT/pages/antora-publish-procedure.adoc @@ -114,7 +114,7 @@ Then run: [source,bash] ---- -sh publish.sh "ISIS-nnnn: a custom commit message" +sh publish.sh "CAUSEWAY-nnnn: a custom commit message" ---- This does the following: @@ -162,7 +162,7 @@ When ready, then stage, commit and push the changes (in the `causeway-site.git` [source,bash] ---- -git commit -am "ISIS-nnnn: updating docs" +git commit -am "CAUSEWAY-nnnn: updating docs" git push ---- diff --git a/antora/components/comguide/modules/ROOT/pages/applying-patches.adoc b/antora/components/comguide/modules/ROOT/pages/applying-patches.adoc index e9f7feb548..562ac1cb69 100644 --- a/antora/components/comguide/modules/ROOT/pages/applying-patches.adoc +++ b/antora/components/comguide/modules/ROOT/pages/applying-patches.adoc @@ -14,7 +14,7 @@ You can do this easily with `git apply` [source,bash] ---- -git apply --stat ISIS-xxx.patch +git apply --stat CAUSEWAY-xxx.patch ---- Note that this command does not apply the patch, but only shows you the stats about what it’ll do. @@ -25,7 +25,7 @@ Git allows you to test the patch before you actually apply it. [source,bash] ---- -git apply --check ISIS-xxx.patch +git apply --check CAUSEWAY-xxx.patch ---- If you don't get any errors, the patch has no conflicts. @@ -37,7 +37,7 @@ To apply a clean patch (adding the items and commit/signoff in a single step), u [source,bash] ---- -git am --signoff < ISIS-xxx.patch +git am --signoff < CAUSEWAY-xxx.patch ---- This preserves the original author's commit message. @@ -59,7 +59,7 @@ This sequence in this case is: [source,bash] ---- -git apply ISIS-xxx.patch +git apply CAUSEWAY-xxx.patch ---- Fix up any issues. diff --git a/antora/components/comguide/modules/ROOT/pages/cutting-a-release.adoc b/antora/components/comguide/modules/ROOT/pages/cutting-a-release.adoc index 0ee050a800..66c6f091ae 100644 --- a/antora/components/comguide/modules/ROOT/pages/cutting-a-release.adoc +++ b/antora/components/comguide/modules/ROOT/pages/cutting-a-release.adoc @@ -196,13 +196,13 @@ For example: [source,bash,subs="attributes+"] ---- -export ISISJIRA=ISIS-9999 # <.> +export ISISJIRA=CAUSEWAY-9999 # <.> export ISISTMP=/c/tmp # <.> export ISISREL={page-isisrel} # <.> export ISISRC=RC1 # <.> export ISISBRANCH=release-$ISISREL-$ISISRC export ISISART=causeway -env | grep ISIS | sort +env | grep CAUSEWAY | sort ---- <.> set to an "umbrella" ticket for all release activities. (One should exist already, xref:comguide:ROOT:post-release-successful.adoc#create-new-jira[created at] the beginning of the development cycle now completing). diff --git a/antora/components/comguide/modules/ROOT/pages/merging-a-pull-request.adoc b/antora/components/comguide/modules/ROOT/pages/merging-a-pull-request.adoc index 960f6d0012..0b59647c5a 100644 --- a/antora/components/comguide/modules/ROOT/pages/merging-a-pull-request.adoc +++ b/antora/components/comguide/modules/ROOT/pages/merging-a-pull-request.adoc @@ -17,7 +17,7 @@ Once you are happy, you can commit. The overall process is as follows: -* locate/raise corresponding JIRA ticket, eg ISIS-1162 +* locate/raise corresponding JIRA ticket, eg CAUSEWAY-1162 * checkout branch from which PR was forked (usually just 'master') * merge PR into temporary branch using the `github-pr.sh` script * test the change locally (run the app, rebuild, manual regression tests etc) @@ -54,7 +54,7 @@ The syntax is: [source,bash] ---- -github-pr.sh -j 1162 -g 31 [-s] [-p ISIS] +github-pr.sh -j 1162 -g 31 [-s] [-p CAUSEWAY] ---- where: @@ -71,9 +71,9 @@ is the github PR issue number + will optionally skip the build and auto-merge -* `-p ISIS` +* `-p CAUSEWAY` + -optionally overrids the JIRA project (defaults to 'ISIS') +optionally overrids the JIRA project (defaults to 'CAUSEWAY') == Example transcript @@ -91,12 +91,12 @@ repo_full_name : sebadiaz/causeway repo_clone_url : https://github.com/sebadiaz/causeway.git branch_name_fork : master -merging into: ISIS-1162_pr-31 +merging into: CAUSEWAY-1162_pr-31 -Deleting branch 'ISIS-1162_pr-31' -Deleted branch ISIS-1162_pr-31 (was bd2e3c2). -Creating the branch ISIS-1162_pr-31 -Switched to a new branch 'ISIS-1162_pr-31' +Deleting branch 'CAUSEWAY-1162_pr-31' +Deleted branch CAUSEWAY-1162_pr-31 (was bd2e3c2). +Creating the branch CAUSEWAY-1162_pr-31 +Switched to a new branch 'CAUSEWAY-1162_pr-31' Pulling the changes from https://github.com/sebadiaz/causeway.git master From https://github.com/sebadiaz/causeway * branch master -> FETCH_HEAD @@ -116,14 +116,14 @@ Once done, the script continues: ---- If build successful and happy to merge, execute: -git checkout master && git merge --no-ff ISIS-1162_pr-31 && git branch -d ISIS-1162_pr-31 +git checkout master && git merge --no-ff CAUSEWAY-1162_pr-31 && git branch -d CAUSEWAY-1162_pr-31 ---- The screenshot belows shows the history we end up with: image::committers/github-pr-history.png[] -This shows the fork being merged into the temporary branch ("ISIS-1162_pr-31"), then some further tidy-up, and finally the merging of the temporary branch into mainline. +This shows the fork being merged into the temporary branch ("CAUSEWAY-1162_pr-31"), then some further tidy-up, and finally the merging of the temporary branch into mainline. Note that there is no rebasing in this model. This is intentional: when the merged branch is pushed, github will automatically close the original pull request. diff --git a/antora/components/comguide/modules/ROOT/pages/policies/git-policy.adoc b/antora/components/comguide/modules/ROOT/pages/policies/git-policy.adoc index 914acfc3f0..dc8f7d3cd9 100644 --- a/antora/components/comguide/modules/ROOT/pages/policies/git-policy.adoc +++ b/antora/components/comguide/modules/ROOT/pages/policies/git-policy.adoc @@ -31,14 +31,14 @@ There are many ways of using Git, but the Apache Causeway committers have adopte + [source,bash] ---- -git checkout -b ISIS-999 +git checkout -b CAUSEWAY-999 ---- * periodically, push the branch to origin (for safekeeping): + + [source,bash] ---- -git push origin ISIS-999 +git push origin CAUSEWAY-999 ---- * `rebase` the topic branch periodically on master. @@ -50,9 +50,9 @@ You need to ensure that your co-worker has no outstanding work before you do thi ---- git checkout master git pull -git checkout ISIS-999 +git checkout CAUSEWAY-999 git rebase master -git push origin ISIS-999 --force +git push origin CAUSEWAY-999 --force ---- * when feature is complete, rebase once more (as above), then switch to master and perform a `merge --no-ff`: + @@ -60,15 +60,15 @@ git push origin ISIS-999 --force [source,bash] ---- git checkout master -git merge --no-ff ISIS-999 +git merge --no-ff CAUSEWAY-999 ---- * finally, remove the branch + + [source,bash] ---- -git branch -d ISIS-999 -git push origin --delete ISIS-999 +git branch -d CAUSEWAY-999 +git push origin --delete CAUSEWAY-999 ---- This way of working gives us the full history on the branch as to what the thought processes were for the feature, but only a single commit on to `master` to see the ultimate impact of the changes (acting a bit like a summary). @@ -79,13 +79,13 @@ The minimum we expect in a commit messages is: [source,bash] ---- -ISIS-nnn: brief summary here +CAUSEWAY-nnn: brief summary here - optionally, longer details - should be written here - in bullet points ---- -where `ISIS-nnn` is a ticket raised in our https://issues.apache.org/jira/browse/ISIS[JIRA issue tracker]. +where `CAUSEWAY-nnn` is a ticket raised in our https://issues.apache.org/jira/browse/CAUSEWAY[JIRA issue tracker]. For non-committers we typically expect more detail again; see the xref:conguide:ROOT:contributing.adoc[contributing] page for the longer format recommended for contributors to use. diff --git a/antora/components/comguide/modules/ROOT/pages/post-release-successful.adoc b/antora/components/comguide/modules/ROOT/pages/post-release-successful.adoc index 0c9c8ccdc4..45941929ad 100644 --- a/antora/components/comguide/modules/ROOT/pages/post-release-successful.adoc +++ b/antora/components/comguide/modules/ROOT/pages/post-release-successful.adoc @@ -58,14 +58,14 @@ As we did for the cutting of the release, we set environment variables to parame [source,bash,subs="attributes+"] ---- -export ISISJIRA=ISIS-9999 # <.> +export ISISJIRA=CAUSEWAY-9999 # <.> export ISISTMP=/c/tmp # <.> export ISISREL={page-isisrel} # <.> export ISISRC=RC1 # <.> export ISISBRANCH=release-$ISISREL-$ISISRC export ISISART=causeway -env | grep ISIS | sort +env | grep CAUSEWAY | sort ---- <.> set to an "umbrella" ticket for all release activities. (One should exist already, xref:comguide:ROOT:post-release-successful.adoc#create-new-jira[created at] the beginning of the development cycle now completing). @@ -103,14 +103,14 @@ Any tickets that were partially implemented should be closed, and new tickets cr === Mark the version as released -In JIRA, go to the link:https://issues.apache.org/jira/plugins/servlet/project-config/ISIS/versions[administration section] for the Apache Causeway project and update the version as being released. +In JIRA, go to the link:https://issues.apache.org/jira/plugins/servlet/project-config/CAUSEWAY/versions[administration section] for the Apache Causeway project and update the version as being released. In the link:https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=87[Kanban view] this will have the effect of marking all tickets as released (clearing the "done" column). [#close-all-released-tickets] === Close all released tickets -From the link:https://issues.apache.org/jira/projects/ISIS?selectedItem=com.atlassian.jira.jira-projects-plugin%3Arelease-page&status=released-unreleased[Releases page], review the status of all work items in the release to check that they are closed. +From the link:https://issues.apache.org/jira/projects/CAUSEWAY?selectedItem=com.atlassian.jira.jira-projects-plugin%3Arelease-page&status=released-unreleased[Releases page], review the status of all work items in the release to check that they are closed. If any are not, open the tickets in the issue navigator (from the release page): @@ -135,7 +135,7 @@ From the root directory, generate the release notes for the current release, in + [source,bash,subs="attributes+"] ---- -sh scripts/jira-release-notes.sh ISIS $ISISREL > /tmp/$ISISREL.adoc +sh scripts/jira-release-notes.sh CAUSEWAY $ISISREL > /tmp/$ISISREL.adoc ---- + [NOTE] diff --git a/antora/components/conguide/modules/ROOT/pages/contributing.adoc b/antora/components/conguide/modules/ROOT/pages/contributing.adoc index 3ae3d3a4fa..419cc6e697 100644 --- a/antora/components/conguide/modules/ROOT/pages/contributing.adoc +++ b/antora/components/conguide/modules/ROOT/pages/contributing.adoc @@ -31,7 +31,7 @@ That is: . you set the https://github.com/apache/causeway.git[github.com/apache/causeway] as your upstream branch; this will allow you to keep your local clone up-to-date with new commits * note the asymmetry here: the `upstream` repo (the Apache GitHub repo) is *not* the same as the `origin` repo (your fork). . you work on your changes locally; when done, you push them to your GitHub fork -. to contribute back a change, raise a https://issues.apache.org/jira/browse/ISIS[JIRA] ticket (you will need to log in or create a new account first), and ensure your commit message is in the form: `ISIS-nnnn: ...` so that changes can be tracked (more discussion on this point below). +. to contribute back a change, raise a https://issues.apache.org/jira/browse/CAUSEWAY[JIRA] ticket (you will need to log in or create a new account first), and ensure your commit message is in the form: `CAUSEWAY-nnnn: ...` so that changes can be tracked (more discussion on this point below). In any case, before you decide to start hacking with Apache Causeway, it's always worth creating a ticket in JIRA and then have a discussion about it on the xref:docs:support:mailing-list.adoc[mailing lists]. . Use GitHub to raise a https://help.github.com/articles/using-pull-requests/[pull request] for your feature . An Apache Causeway committer will review your change, and apply it if suitable. @@ -84,7 +84,7 @@ We therefore recommend that your commit messages are as follows:footnote:[Inspir [source,other] ---- -ISIS-999: Makes the example in CONTRIBUTING imperative and concrete +CAUSEWAY-999: Makes the example in CONTRIBUTING imperative and concrete Without this patch applied, the example commit message in the CONTRIBUTING document is not a concrete example. This is a problem because the @@ -125,15 +125,15 @@ If this fails, see our xref:conguide:git:about.adoc#git-cookbook[git cookbook] p === Create a topic branch -We recommend you name topic branches by the JIRA ticket, ie <tt>ISIS-nnn-description</tt>. -So let's create a new branch based off `master` and call it "ISIS-123-blobs" +We recommend you name topic branches by the JIRA ticket, ie <tt>CAUSEWAY-nnn-description</tt>. +So let's create a new branch based off `master` and call it "CAUSEWAY-123-blobs" You can confirm the branch is there and is your new `HEAD` using either `gitk --all`. Alternatively, use the command line: [source,bash] ---- -$ git checkout -b ISIS-123-blobs +$ git checkout -b CAUSEWAY-123-blobs ---- The command line prompt should also indicate you are on a branch, isolated from any changes that might happen on the `master` branch. @@ -166,7 +166,7 @@ Next, we reintegrate our topic branch by rebasing onto `master`: [source,bash] ---- -git checkout ISIS-123-blobs +git checkout CAUSEWAY-123-blobs git rebase master ---- @@ -184,7 +184,7 @@ Once the rebase has completed, re-run your tests to confirm that everything is s If you have your own fork, you can now simply push the changes you've made locally to your fork: This will create a corresponding branch in the remote GitHub repo. -If you use `gitk --all`, you'll also see a `remotes/origin/ISIS-123-blobs` branch. +If you use `gitk --all`, you'll also see a `remotes/origin/CAUSEWAY-123-blobs` branch. Then, use GitHub to raise a https://help.github.com/articles/using-pull-requests/[pull request]. Pull requests sent to the Apache GitHub repositories will forward a pull request e-mail to the xref:docs:support:mailing-list.adoc[dev mailing list]. @@ -216,7 +216,7 @@ You'll probably also want to remove the remote branch on github: [source,bash] ---- -git push origin --delete ISIS-123-blobs +git push origin --delete CAUSEWAY-123-blobs ---- \... and continue as before until you are ready to resubmit your change. diff --git a/antora/components/conguide/modules/git/pages/about.adoc b/antora/components/conguide/modules/git/pages/about.adoc index 71e97d6ab4..2b6f49878e 100644 --- a/antora/components/conguide/modules/git/pages/about.adoc +++ b/antora/components/conguide/modules/git/pages/about.adoc @@ -18,7 +18,7 @@ To modify existing files: [source,bash] ---- git add filename -git commit -m "ISIS-nnn: yada yada" +git commit -m "CAUSEWAY-nnn: yada yada" ---- The `git add` command adds the changes to the file(s) to the git index (aka staging area). @@ -31,7 +31,7 @@ You can combine these two commands using `-am` flag to git commit: [source,bash] ---- -git commit -am "ISIS-nnn: yada yada" +git commit -am "CAUSEWAY-nnn: yada yada" ---- == Adding new files @@ -41,7 +41,7 @@ To add a new file: [source,bash] ---- git add . -git commit -m "ISIS-nnn: yada yada" +git commit -m "CAUSEWAY-nnn: yada yada" ---- Note that this sequence of commands is identical to modifying an existing file. @@ -54,7 +54,7 @@ To delete a file: [source,bash] ---- git rm filename -git commit -m "ISIS-nnn: yada yada" +git commit -m "CAUSEWAY-nnn: yada yada" ---- == Renaming or moving files @@ -64,7 +64,7 @@ To rename or move a file: [source,bash,subs=+quotes] ---- git mv _filename_ _newfilename_ -git commit -m "ISIS-nnn: yada yada" +git commit -m "CAUSEWAY-nnn: yada yada" ---- == Common Workflows diff --git a/antora/components/docs/modules/support/pages/about.adoc b/antora/components/docs/modules/support/pages/about.adoc index 5f8847f7b2..81d1c8182e 100644 --- a/antora/components/docs/modules/support/pages/about.adoc +++ b/antora/components/docs/modules/support/pages/about.adoc @@ -20,6 +20,6 @@ If you think you've found a bug or want to raise an enhancement request, go to: Some other places that might be useful are: -* link:https://cwiki.apache.org/confluence/display/ISIS/Index[ASF Wiki] +* link:https://cwiki.apache.org/confluence/display/CAUSEWAY/Index[ASF Wiki] * link:https://twitter.com/ApacheIsis[Twitter] diff --git a/antora/components/refguide-index/modules/applib/pages/index/services/exceprecog/hooks/ExceptionRecognizer_010-implementation.adoc b/antora/components/refguide-index/modules/applib/pages/index/services/exceprecog/hooks/ExceptionRecognizer_010-implementation.adoc index c27b23b2be..9055ced361 100644 --- a/antora/components/refguide-index/modules/applib/pages/index/services/exceprecog/hooks/ExceptionRecognizer_010-implementation.adoc +++ b/antora/components/refguide-index/modules/applib/pages/index/services/exceprecog/hooks/ExceptionRecognizer_010-implementation.adoc @@ -14,7 +14,7 @@ The framework provides a number of default implementations for JPA and JDO, to r * other data access problem. -// TODO: v2 - flesh this out once ISIS-2502 is complete. +// TODO: v2 - flesh this out once CAUSEWAY-2502 is complete. //=== Configuration Properties // diff --git a/antora/components/refguide-index/modules/applib/pages/index/services/wrapper/hooks/WrapperFactory_020-examples-and-usage.adoc b/antora/components/refguide-index/modules/applib/pages/index/services/wrapper/hooks/WrapperFactory_020-examples-and-usage.adoc index c49842aafd..6013636d8b 100644 --- a/antora/components/refguide-index/modules/applib/pages/index/services/wrapper/hooks/WrapperFactory_020-examples-and-usage.adoc +++ b/antora/components/refguide-index/modules/applib/pages/index/services/wrapper/hooks/WrapperFactory_020-examples-and-usage.adoc @@ -42,7 +42,7 @@ For domain objects (not mixins), the wrapper can be interacted with as follows: * a `set...()` method for properties * any action -NOTE: with ISIS-3084, `addTo...()` and `removeFrom...()` methods for collections were removed; +NOTE: with CAUSEWAY-3084, `addTo...()` and `removeFrom...()` methods for collections were removed; the notion (direct) collection modification was deprecated as any specific business logic should by handled via actions instead; diff --git a/antora/components/relnotes/modules/ROOT/pages/about.adoc b/antora/components/relnotes/modules/ROOT/pages/about.adoc index f865d39d73..212f58b14d 100644 --- a/antora/components/relnotes/modules/ROOT/pages/about.adoc +++ b/antora/components/relnotes/modules/ROOT/pages/about.adoc @@ -90,7 +90,7 @@ Fixes CVE-2022-42467. | * xref:relnotes:ROOT:2020/2.0.0-M4/relnotes.adoc[Release Notes] * xref:relnotes:ROOT:2020/2.0.0-M4/mignotes.adoc[Migration Notes] -* link:https://issues.apache.org/jira/projects/ISIS/versions/12347808[JIRA Rel Notes] +* link:https://issues.apache.org/jira/projects/CAUSEWAY/versions/12347808[JIRA Rel Notes] | 2.0.0-M3 | 27-Mar-2020 diff --git a/antora/components/userguide/modules/fun/pages/ui/object-layout.adoc b/antora/components/userguide/modules/fun/pages/ui/object-layout.adoc index 231c272fd2..b56992006d 100644 --- a/antora/components/userguide/modules/fun/pages/ui/object-layout.adoc +++ b/antora/components/userguide/modules/fun/pages/ui/object-layout.adoc @@ -264,7 +264,7 @@ When downloading the layout files, there are four "styles" available: * complete * minimal -// TODO: ISIS-3087: let's simplify and get rid of these +// TODO: CAUSEWAY-3087: let's simplify and get rid of these //* current //* normalized diff --git a/viewers/wicket/adoc/modules/ROOT/pages/hints-and-tips/svg-support.adoc b/viewers/wicket/adoc/modules/ROOT/pages/hints-and-tips/svg-support.adoc index 4d26abfe93..df0ce45c0a 100644 --- a/viewers/wicket/adoc/modules/ROOT/pages/hints-and-tips/svg-support.adoc +++ b/viewers/wicket/adoc/modules/ROOT/pages/hints-and-tips/svg-support.adoc @@ -4,11 +4,11 @@ :Notice: Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to you under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at. http://www.apache.org/licenses/LICENSE-2.0 . Unless required by applicable law or ag [...] -(As per link:https://issues.apache.org/jira/browse/ISIS-1604[ISIS-1604]), SVG images can be used: +(As per link:https://issues.apache.org/jira/browse/CAUSEWAY-1604[CAUSEWAY-1604]), SVG images can be used: * as Logo in the upper left corner (Wicket Menubar) * on the Login Page (`login.html`) -* as favicon (`image/svg+xml`, cf. link:https://issues.apache.org/jira/browse/ISIS-1115[ISIS-1115]) +* as favicon (`image/svg+xml`, cf. link:https://issues.apache.org/jira/browse/CAUSEWAY-1115[CAUSEWAY-1115]) However, SVGs are not, by default, displayed on the welcome page. SVGs can be attached as ``Blob``s, but they are displayed as bitmaps (by means of the Batik rasterizer) and do not scale.
