The JIRA count is not a reliable indication of anything. Lots of us
use shade in production. The JIRA count can indicate a plethora of
improvement suggestions, or a bunch of uninvestigated complaints.

Don't get me wrong, please do dig in. But you are likely to find that
it works for you as is.

On Thu, Jun 30, 2011 at 6:30 AM, Robert Burrell Donkin
<robertburrelldon...@gmail.com> wrote:
> On Thu, Jun 30, 2011 at 8:52 AM, David Jencks <david_jen...@yahoo.com> wrote:
>> I think the shade plugin does something like this.
>
> Thanks
>
> I've taken a look and this seems the right place to start but I'll
> probably need to do some development...
>
> There are 21 open issues [1] and (by my count) 8 patches (which are
> probably missing test cases).  Perhaps this indicates that some TLC is
> needed.
>
> I'm happy to work with folks who have karma if they have the energy to
> review. I'm happy to fork over at GitHub and then present a sizable
> pull request at the end. But I'm open to other suggestions too.
> Opinions on my best option?
>
> Robert
>
> [1] 
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+MSHADE+AND+status+%3D+Open+ORDER+BY+priority+DESC&mode=hide
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Reply via email to