Examples

[Dennis Reedy]

Hi,

I was recently thinking that I wanted to add some Gradle examples (as well as some plugins), and wanted to ask if there was a preference on adding the Gradle files along-side of the Maven projects (they will both have the same project structure), or whether you would prefer to have something like:

examples/maven
examples/gradle

Any maybe

examples/ant (that uses Ivy)

Any preference?

Regards

Dennis

[Dawid Loubser]

Hi Dennis,

My personal preference would be to have the same project built with
different build systems (where possible, i.e. where the structure
matches and makes sense) - this way, there is no duplication of example
code, and an easier-to-navigate tree of examples.

Have you yourself taken a liking to Gradle (over Maven)? Or do you just
want to add additional examples?

kind regards,
Dawid

[Jeff Ramsdale]

It's been years since I've used Ant and I don't run into it very much in the wild. I wouldn't bother with it, personally.

Gradle has a growing fanbase and might be worth supporting. I'd just overlay the Gradle and Maven examples and not have duplication.

-j

Dennis

--
You received this message because you are subscribed to the Google Groups "Rio Users Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rio-users+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Wade Chandler]

On 08/27/2014 02:47 AM, Jeff Ramsdale wrote:
> I'd just overlay the Gradle and Maven examples and not have duplication.

I think you should consider tooling versus just being able to build the
examples. Can one quickly open each in an IDE? I haven't tried such a
setup in the various IDEs to know myself how they all behave. I think
from the code perspective the duplication will be mostly copy and paste
if you have to duplicate, so that would be a pretty lightweight problem.

> Gradle has a growing fanbase and might be worth supporting.

I would say Gradle has more than a growing fanbase. It is "the" Android
build system; you'll use it going forward to make new Android projects.
With Pivotal backing Groovy and promoting and using Gradle too, that is
going to keep growing.

Wade

--

=================
Wade Chandler

Software Engineer and Consultant
NetBeans Contributor
NetBeans Dream Team Member

wadechandler.com
netbeans.org

[Zsolt Kúti]

On Tue, 26 Aug 2014 16:17:30 -0400
Dennis Reedy <dennis...@gmail.com> wrote:


> Hi,

>

> I was recently thinking that I wanted to add some Gradle examples
> (as well as some plugins), and wanted to ask if there was a
> preference on adding the Gradle files along-side of the Maven
> projects (they will both have the same project structure), or whether
> you would prefer to have something like:

+1 for adding along-side

[Dennis Reedy]

On Aug 27, 2014, at 731AM, Wade Chandler <con...@wadechandler.com> wrote:

> On 08/27/2014 02:47 AM, Jeff Ramsdale wrote:
>> I'd just overlay the Gradle and Maven examples and not have duplication.
> I think you should consider tooling versus just being able to build the examples. Can one quickly open each in an IDE? I haven't tried such a setup in the various IDEs to know myself how they all behave. I think from the code perspective the duplication will be mostly copy and paste if you have to duplicate, so that would be a pretty lightweight problem.
>
>> Gradle has a growing fanbase and might be worth supporting.
>
> I would say Gradle has more than a growing fanbase. It is "the" Android build system; you'll use it going forward to make new Android projects. With Pivotal backing Groovy and promoting and using Gradle too, that is going to keep growing.

Yeah, Gradle is awesome. I'm converting an Ant (and Ivy) project over to Gradle currently, and have become enamored with it. Personally, if I had to choose Maven or Gradle, I'd go with Gradle for a new project.

Dennis

[Zsolt Kúti]

On Wed, 27 Aug 2014 08:56:25 -0400
Dennis Reedy <dennis...@gmail.com> wrote:


> Yeah, Gradle is awesome. I'm converting an Ant (and Ivy) project
> over to Gradle currently, and have become enamored with it.
> Personally, if I had to choose Maven or Gradle, I'd go with Gradle
> for a new project.

:-)

[Jeff Ramsdale]

On Wed, Aug 27, 2014 at 4:31 AM, Wade Chandler <con...@wadechandler.com> wrote:

On 08/27/2014 02:47 AM, Jeff Ramsdale wrote:

I'd just overlay the Gradle and Maven examples and not have duplication.

I think you should consider tooling versus just being able to build the examples. Can one quickly open each in an IDE? I haven't tried such a setup in the various IDEs to know myself how they all behave. I think from the code perspective the duplication will be mostly copy and paste if you have to duplicate, so that would be a pretty lightweight problem.

Agreed--I think the IDE experience is important. 

Gradle has a growing fanbase and might be worth supporting.

I would say Gradle has more than a growing fanbase. It is "the" Android build system; you'll use it going forward to make new Android projects. With Pivotal backing Groovy and promoting and using Gradle too, that is going to keep growing.

Android's embrace of Ant didn't really make Ant any more relevant outside of that ecosystem. And you can use Maven to build Android projects too. I don't think Android itself will make or break any build system, though Android's use of Gradle is certainly a boost to it.

-j

 

Wade

--

=================
Wade Chandler

Software Engineer and Consultant
NetBeans Contributor
NetBeans Dream Team Member

wadechandler.com
netbeans.org

--
You received this message because you are subscribed to the Google Groups "Rio Users Group" group.

To unsubscribe from this group and stop receiving emails from it, send an email to rio-users+unsubscribe@googlegroups.com.

[Dennis Reedy]

On Aug 27, 2014, at 1123AM, Jeff Ramsdale <jeff.r...@gmail.com> wrote:

On Wed, Aug 27, 2014 at 4:31 AM, Wade Chandler <con...@wadechandler.com> wrote:

On 08/27/2014 02:47 AM, Jeff Ramsdale wrote:

I'd just overlay the Gradle and Maven examples and not have duplication.

I think you should consider tooling versus just being able to build the examples. Can one quickly open each in an IDE? I haven't tried such a setup in the various IDEs to know myself how they all behave. I think from the code perspective the duplication will be mostly copy and paste if you have to duplicate, so that would be a pretty lightweight problem.

Agreed--I think the IDE experience is important. 

Yes & no. Having concrete examples and plugins available in both Maven and Gradle provides needed context on how to structure and build service(s). Support for Maven and Gradle in respective IDEs (IntelliJ, Eclipse, Netbeans,...) is out of scope for Rio. For example, Gradle support in IntelliJ 12 was lacking, however in IntelliJ 13, it's really good. I can't control what IDEs do or do not do. Some love Eclipse's Maven support, some hate it. 

Also, when you point a particular IDE at a mixed examples directory, it's also going to confuse the heck out of the IDE. Is it a Gradle project? Or is it a Maven project? Might be cleaner if examples were broken out.

Dennis

[Dawid Loubser]

On 27/08/2014 18:21, Dennis Reedy wrote:

Also, when you point a particular IDE at a mixed examples directory, it's also going to confuse the heck out of the IDE. Is it a Gradle project? Or is it a Maven project? Might be cleaner if examples were broken out.

I never considered that angle. That is such a compelling point, that I think you should make the examples side-by-side because of this.

It's not like you need to publish all your examples using all the build systems - A single good example of each would suffice, and for the others, use what you prefer (Maven or Gradle).

regards,
Dawid

P.S. Certainly in IntelliJ, it's perfectly happy with mixed-build-system projects - upon import, it asks you which one ("project model") to use.

[Rafał Krupiński]

W dniu środa, 27 sierpnia 2014 18:21:45 UTC+2 użytkownik dennisr napisał:

[...]

Also, when you point a particular IDE at a mixed examples directory, it's also going to confuse the heck out of the IDE. Is it a Gradle project? Or is it a Maven project? Might be cleaner if examples were broken out.

Is one Gradle example insufficient?

Rafał