|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60134791&iu=/4140/ostg.clktrk
_______________________________________________ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
http://mojo.codehaus.org/native2ascii-maven-plugin/index.html
Here's a similar suggestion from a blog post (in French):
https://blog.crafting-labs.fr/?post/2010/09/17/fichiers-.properties-java-en-UTF-8-avec-maven
I have not had a chance to test this out. But, I wonder if it would be possible to run the "build.properties" file through native2ascii (e.g. creating a file "./target/build-converted.properties") and then using that newly generated file to do the actual filtering & fill out the final dspace.cfg file. I'm not sure if this will work, but it may be worth trying, especially since Maven developers have closed the ticket related to this problem (https://jira.codehaus.org/browse/MRESOURCES-175)