Sure thing.  I have mule forked too and see the size is huge overall.  Are you ok with updates to the localized build plugin updates?  I assume junit being updated is slightly risky too for same reasons.  What is your opinion on that?  I haven't seen it cause a downstream effect yet but pull builds of mule are slow going.

--- Original Message ---

From: "Mariano Gonzalez" <notifications@github.com>
Sent: December 2, 2013 9:43 AM
To: "mulesoft/mule-common" <mule-common@noreply.github.com>
Cc: "Jeremy Landis" <jeremylandis@hotmail.com>
Subject: Re: [mule-common] Project Cleanup & Dependency Update (#3)

> @@ -7,9 +8,12 @@
>      <description>Shared Interfaces between Studio and ESB for Metadata and Connectivity access</description>
>
>      <properties>
> -        <antlr.version>3.5</antlr.version>
> +        <antlr.version>3.5.1</antlr.version>

The thing with updating is that any change in mule-commin spawns a testing effort in the ESB, Studio, Devkit, Connectors, etc. So, although I'm all for using the latest libraries available, such a change needs to happen with planning and involvement from the development and QA team. If you didn't find a bug that is fixed by this change then rollback this change and open a jira requesting the update

---
Reply to this email directly or view it on GitHub:
https://github.com/mulesoft/mule-common/pull/3/files#r8026290