On a more serious note, I would probably say #1 as well
On May 24, 2013, at 1:57 PM, Sebastien Blanc <scm.blanc(a)gmail.com> wrote:
I would say #1
On Fri, May 24, 2013 at 8:53 PM, Kris Borchers <kris(a)redhat.com> wrote:
I would vote #5 which would be to just
http://wil.to/_/problem-solving.gif
On May 24, 2013, at 1:44 PM, Summers Pittman <supittma(a)redhat.com> wrote:
>
https://code.google.com/p/maven-android-plugin/issues/detail?id=377&s...
>
> So right now if you have the latest SDK maven can't build the project. Worse,
the fixed version isn't in maven central yet.
>
> I'm sure it will be fixed sooner rather than later (given how many people must
use it), and there is a workaround in the bug report.
>
> Do we want to
> 1) Put the workaround in the project's README until it isn't necessary
> 2) Host a patched version of the plugin on jboss nexus and configure the pom to run
against it
> 3) Post instructions for how developers can patch/update their local install of the
plug-in
> 4) Wait patiently until the fix makes it into central
> 5) Something else I overlooked.
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/aerogear-dev
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev