它可以使用Git的钩来阻止文件名:
https://github.com/t-b/git-pre-commit-hook-windows-filenames/blob/master/pre-commit
#!/bin/bash
#
# Copyright thomas dot braun aeht virtuell minus zuhause dot de, 2013
#
# A hook script to check that the to-be-commited files are valid
# filenames on a windows platform.
# Sources:
# - http://stackoverflow.com/a/62888
# - http://msdn.microsoft.com/en-us/library/aa365247.aspx
#
# To enable this hook, rename this file to "pre-commit", move it to ".git/hook" and make it executable.
if git rev-parse --verify HEAD >/dev/null 2>&1
then
against=HEAD
else
# Initial commit: diff against an empty tree object
against=
fi
enforcecompatiblefilenames=$(git config hooks.enforcecompatiblefilenames)
# Redirect output to stderr.
exec 1>&2
if test "$enforcecompatiblefilenames" != "true"
then
exit 0
fi
git diff --cached --name-only --diff-filter=A -z $against | while IFS= read -r -d '' filename; do
# Non-printable characters from ASCII range 0-31
nonprintablechars=$(echo -n "$filename" | LC_ALL=C tr -d '[ -~]' | wc -c)
# Illegal characters: < > : "/\ | ? *
# We don't test for/(forward slash) here as that is even on *nix not allowed in *filename*
illegalchars=$(echo -n "$filename" | LC_ALL=C grep -E '(<|>|:|"|\\|\||\?|\*)' | wc -c)
# Reserved names plus possible extension
# CON, PRN, AUX, NUL, COM1, COM2, COM3, COM4, COM5, COM6, COM7, COM8, COM9, LPT1, LPT2, LPT3, LPT4, LPT5, LPT6, LPT7, LPT8, and LPT9
reservednames=$(echo -n "$filename" | LC_ALL=C grep -i -E '(CON|PRN|AUX|NUL|COM1|COM2|COM3|COM4|COM5|COM6|COM7|COM8|COM9|LPT1|LPT2|LPT3|LPT4|LPT5|LPT6|LPT7|LPT8|LPT9).[a-z]{3}' | wc -c)
# No trailing period or space
trailingperiodorspace=$(echo -n "$filename" | LC_ALL=C grep -E '(\.|)$' | wc -c)
# File name is all periods
filenameallperiods=$(echo -n "$filename" | LC_ALL=C grep -E '^\.+$' | wc -c)
# Check complete path length to be smaller than 260 characters
# This test can not be really accurate as we don't know if PWD on the windows filesystem itself is not very long
absolutepathtoolong=0
if test $(echo "$filename" | wc -c) -ge 260
then
absolutepathtoolong=1
fi
# debug output
if test -n "$GIT_TRACE"
then
echo "File: ${filename}"
echo nonprintablechars=$nonprintablechars
echo illegalchars=$illegalchars
echo reservednames=$reservednames
echo trailingperiodorspace=$trailingperiodorspace
echo filenameallperiods=$filenameallperiods
echo absolutepathtoolong=$absolutepathtoolong
fi
if test $nonprintablechars -ne 0 \
|| test $illegalchars -ne 0 \
|| test $reservednames -ne 0 \
|| test $trailingperiodorspace -ne 0 \
|| test $filenameallperiods -ne 0 \
|| test $absolutepathtoolong -ne 0
then
echo "Error: Attempt to add a file name which is incompatible to windows file systems."
echo
echo "If you know what you are doing you can disable this"
echo "check using:"
echo
echo "git config hooks.enforcecompatiblefilenames false"
echo
exit 1
fi
done
这种方法的缺点是在本地安装它为每个开发人员的需要,因为不幸的是并非所有的Git回购服务支持服务器侧钩(看着你,GitHub)。
你用什么来检查AEM的内容并将其序列化?我从来没有遇到这个问题,我是一个Windows用户。当我使用[Vault](https://docs.adobe.com/docs/en/aem/6-2/develop/dev-tools/ht-vlttool.html)时,它只是重命名所有相关文件以在下面使用下划线前缀('_cq_dialog.xml','_cq_editConfig.xml'等)。另外,Vault倾向于将'jcr:content'节点序列化为XML元素,而不是文件夹。 – toniedzwiedz
至于Maven插件,请查看['content-package-maven-plugin'](https://docs.adobe.com/docs/en/aem/6-2/develop/dev-tools/vlt-mavenplugin .html)或['maven-crx-plugin'](https://github.com/Cognifide/Maven-CRX-Plugin),它们都在内部使用'vlt'。 – toniedzwiedz
已从内容包中提取AEM内容并将其放入src/test/resources/SLING-INF中,以便与Prosper测试一起使用。它看起来像包管理器的行为与'vlt' – antonyh