Die MacRoman, DIE!!

OSX defaults to MacRoman for an encoding, so if you're using Maven, you might see messages like:

[WARNING] Using platform encoding (MacRoman actually) to copy
filtered resources, i.e. build is platform dependent

Simple enough, but it can cause you headaches. To change to UTF-8, just add the following properties to your pom.xml:

<properties>
 ...
 <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
 <project.reporting.outputEncoding>UTF-8</project.reporting.outputEncoding>
 ...
</properties>

(edit: had a couple typos, encoding in the property name needs to start with a capital E - camelCase)

Extremely useful maven placeholder based on profile

Someone just showed me this example which solves one of the annoying parts of multiple devs working with multiple resource configurations (databases, mailservers, etc) for different environments (dev,test,prod,etc)

(in project pom)

<properties>
...
        <project.build.sourceEncoding>ISO-8859-1</project.build.sourceEncoding>
        <log4j.priority>DEBUG</log4j.priority>
        <project.build.listener-resources-context>staging-listener-resources.xml</project.build.listener-resources-context>
    </properties>
    <profiles>
        <profile>
            <id>production</id>
            <properties>
                <log4j.priority>INFO</log4j.priority>
                <project.build.listener-resources-context>prod-listener-resources.xml</project.build.listener-resources-context>
                <maven.test.skip>true</maven.test.skip>
            </properties>
        </profile>
    </profiles>
...

Then this goes in the build section:

<resources>
   <resource>
      <directory>src/main/resources</directory>
      <filtering>true</filtering>
   </resource>
</resources>

Then in your spring context, you can import just like normal, but using a placeholder now:

<import resource="${project.build.listener-resources-context}"/>

So now a normal build uses the staging resources, and something like
mvn install -Pproduction
now uses the production resources.

Removing chars from files in a directory

Some files got generated with symbols like the 'tm' symbol and the system consuming those files can't handle those characters... so we had to remove them.

To identify them:
find . | xargs perl -ne 'print if /[\176-\512]/' | perl -ne 'print "$1\n" if /(\d+),.*/'

To remove the "special" characters:
find . -type f -print0 | xargs -0 perl -p -i -e 's/[\176-\512]//g'

quick and dirty!

Global git config

Just some quick git options when hopping on a new box:

git config --global user.name "Your Name Comes Here"
git config --global user.email you@yourdomain.example.com
git config --global color.branch auto
git config --global color.diff auto
git config --global color.interactive auto
git config --global color.status auto