If moving to Gradle can give us more autonomy +1 Question: Is possible to deploy the final artficat to maven central? Summers Pittman wrote: > Y'all, > > In the last release we had some trouble at the end. People were having > trouble building aerogear-android because the android-sdk-deployer > project had a couple of "small" problems. Mainly there was an issue with > one of the deployers submodules (and it had to be disabled by hand) and > the deployer itself isn't compatible with maven 3.1.0. I don't want to > include in the build instructions for aerogear "download this old > version of Maven and then edit the pom of this third party project". > > The easiest way to remove our dependency on the deployer is to start > using Google's gradle build system. The Android SDK has packages for > deploying the necessary repositories so that our build can consume them > and we can use the gradle wrapper to keep our users from having to > install yet more software. > > So where does this leave maven? Unfortuantely it is still necessary to > build the apklib file (as far as I know), but it won't be necessary to > actually USE the project anymore. > > wdyt? -- abstractj _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev

If moving to Gradle can give us more autonomy +1 Question: Is possible to deploy the final artficat to maven central?

Summers Pittman wrote: > Y'all, > > In the last release we had some trouble at the end. People were having > trouble building aerogear-android because the android-sdk-deployer > project had a couple of "small" problems. Mainly there was an issue with > one of the deployers submodules (and it had to be disabled by hand) and > the deployer itself isn't compatible with maven 3.1.0. I don't want to > include in the build instructions for aerogear "download this old > version of Maven and then edit the pom of this third party project". > > The easiest way to remove our dependency on the deployer is to start > using Google's gradle build system. The Android SDK has packages for > deploying the necessary repositories so that our build can consume them > and we can use the gradle wrapper to keep our users from having to > install yet more software. > > So where does this leave maven? Unfortuantely it is still necessary to > build the apklib file (as far as I know), but it won't be necessary to > actually USE the project anymore. > > wdyt? _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev

Awesome +1 +1

Summers Pittman wrote: > Yes. The proposed release would include aar (for Gradle and Android > Studio), apklib (for maven), and a jar file (headers for ides to link > against, but maven will still compile with the apklib). -- abstractj _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev

Do you know how Gradle stands for IDE support? Does it simplify Android Development for Eclipse/JBDS/IntelliJ?

Karel On Mon, 19 Aug 2013 10:48:25 -0400 Summers Pittman <secondsun(a)gmail.com&gt; wrote: > Y'all, > > In the last release we had some trouble at the end. People were having > trouble building aerogear-android because the android-sdk-deployer > project had a couple of "small" problems. Mainly there was an issue with > one of the deployers submodules (and it had to be disabled by hand) and > the deployer itself isn't compatible with maven 3.1.0. I don't want to > include in the build instructions for aerogear "download this old > version of Maven and then edit the pom of this third party project". > > The easiest way to remove our dependency on the deployer is to start > using Google's gradle build system. The Android SDK has packages for > deploying the necessary repositories so that our build can consume them > and we can use the gradle wrapper to keep our users from having to > install yet more software. > > So where does this leave maven? Unfortuantely it is still necessary to > build the apklib file (as far as I know), but it won't be necessary to > actually USE the project anymore. > > wdyt? > > Summers > > > _______________________________________________ > 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

We already have the side effects, his name is maven-android-sdk-deployer.

So if Gradle will help to get rid off it, still +1

Summers Pittman wrote: > On 08/20/2013 08:35 AM, Karel Piwko wrote: >> Do you know how Gradle stands for IDE support? Does it simplify Android >> Development for Eclipse/JBDS/IntelliJ? > Gradle support is excellent in IntelliJ. Acceptable in NetBeans (by > NetBeans' standards), and I don't know about Eclipse because Eclipse is > a pain in the ass with third part build tools. It looks like Spring STS > is providing a Gradle for Eclipse plugin but I havn't used it. > > Until everyone is using Gradle and Android Studio we still will have to > maintain maven (for apklib) but the golden scenario for starting > out/green field development will be Gradle. > > Now I may get into the woods on this and find out it has a horrible side > effect, but right now it should simplify the life of a developer. > > Summers > > PS One important note is that this would be hitching us harder to > Google's tooling cart and they have been known to dump products in the > ocean with only a few months of notice. >> Karel >> >> On Mon, 19 Aug 2013 10:48:25 -0400 >> Summers Pittman <secondsun(a)gmail.com&gt; wrote: >> >>> Y'all, >>> >>> In the last release we had some trouble at the end. People were having >>> trouble building aerogear-android because the android-sdk-deployer >>> project had a couple of "small" problems. Mainly there was an issue with >>> one of the deployers submodules (and it had to be disabled by hand) and >>> the deployer itself isn't compatible with maven 3.1.0. I don't want to >>> include in the build instructions for aerogear "download this old >>> version of Maven and then edit the pom of this third party project". >>> >>> The easiest way to remove our dependency on the deployer is to start >>> using Google's gradle build system. The Android SDK has packages for >>> deploying the necessary repositories so that our build can consume them >>> and we can use the gradle wrapper to keep our users from having to >>> install yet more software. >>> >>> So where does this leave maven? Unfortuantely it is still necessary to >>> build the apklib file (as far as I know), but it won't be necessary to >>> actually USE the project anymore. >>> >>> wdyt? >>> >>> Summers >>> >>> >>> _______________________________________________ >>> 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 -- abstractj _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev

The easiest way to remove our dependency on the deployer is to start using Google's gradle build system. The Android SDK has packages for deploying the necessary repositories so that our build can consume them and we can use the gradle wrapper to keep our users from having to install yet more software.

-----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (Darwin) Comment: GPGTools - http://gpgtools.org iQEcBAEBAgAGBQJSE33dAAoJEJwHe9ocMKlJwGYIAIxcFBBlTnFAGEXyFOAyNACE zDhlxIVAGQFoqQfGpjBgNqU/XTDAoxn+FsIej11P2fJy3aKkJYs0h4fNg4jalVAu c1Bu1MEPJLGTwA8Jz8WxXEy/SDPIBglyZ9qmupk31hqK0TXfElAMfs29vMnSzspB y7TeyFNGLmsX7GrCJfpQxc9JX1JV3ugSeLzpVGKfqzXZp0C5gYso8pV5JcIPBMD8 qtFtmuDUo8UlJJybG9LookRobSf6dpPshxD1EesBf6fwWRzIQpW2RRu5afvqzJeY 482J2YfbKqhGdvUBc7PnrRO4bNmzBJxxRg0LgPVHbbLnX+5w/CJ5UaZrM/QPRRk= =I9/v -----END PGP SIGNATURE-----