+1 on this...
But I also think we can limit the filtration process to just those files it
is required for. Which I think are primarily just dspace/config/*.* and
web.xml
On Tue, Oct 6, 2009 at 2:35 PM, Larry Stone <[email protected]> wrote:
> I've noticed a stream of warning messages from Maven during builds, of
> the form:
>
> [WARNING] Using platform encoding (MacRoman actually) to copy
> filtered resources, i.e. build is platform dependent!
>
> What this really means, near as I've been able to determine, is that
> text files in the src/main/resources subdirectory of a project get
> translated from Maven's presumed UTF-8 native format to its idea of
> the platform default character set. On MacOS 10.5, that's apparently
> MacRoman, although the platform supports Unicode just as well.
>
> I find it alarming because many of the files it's translating are XML
> (XSL, XMAP) files whose headers promise they are in UTF-8.
> Fortunately we still aren't really exploring outside of the familiar
> old ASCII character set in these files so it isn't actually an issue,
> yet, but a bug is waiting to happen.
>
> Adding this properties element to the top-level POM fixes it - the
> files are written in UTF-8:
>
> <properties>
> <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
> </properties>
>
> I'll append a list of the files that seem to be affected. Note that
> all but Messages.properties are XML in UTF-8. The Messages file is
> tricky, though, since we might actually want it translated to the
> platform native character set -- but that could be arranged within its
> POM.
>
> Has anyone got experiences, ideas about this?
>
> thanks,
>
> -- Larry
>
> dspace-api/src/main/resources/Messages.properties
> dspace-api/src/main/resources/org/dspace/license/CreativeCommons.xsl
> dspace-api/src/main/resources/org/dspace/license/LicenseCleanup.xsl
> dspace-lni/dspace-lni-client/src/main/resources/dspace-lni.wsdl
> dspace-xmlui/dspace-xmlui-api/src/main/resources/aspects/
> Administrative/administrative.js
> dspace-xmlui/dspace-xmlui-api/src/main/resources/aspects/
> Administrative/sitemap.xmap
> dspace-xmlui/dspace-xmlui-api/src/main/resources/aspects/
> ArtifactBrowser/sitemap.xmap
> dspace-xmlui/dspace-xmlui-api/src/main/resources/aspects/EPerson/
> eperson.js
> dspace-xmlui/dspace-xmlui-api/src/main/resources/aspects/EPerson/
> noAuthMethod.xml
> dspace-xmlui/dspace-xmlui-api/src/main/resources/aspects/EPerson/
> shibbLoginFailure.xml
> dspace-xmlui/dspace-xmlui-api/src/main/resources/aspects/EPerson/
> sitemap.xmap
> dspace-xmlui/dspace-xmlui-api/src/main/resources/aspects/Submission/
> sitemap.xmap
> dspace-xmlui/dspace-xmlui-api/src/main/resources/aspects/Submission/
> submission.js
> dspace-xmlui/dspace-xmlui-api/src/main/resources/aspects/XMLTest/
> sitemap.xmap
>
>
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________
> Dspace-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/dspace-devel
>
------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
