Migrate to dedicated Degraph Gradle plugin

[sbrannen]

Overview

As mentioned by @oehme in #481:

[He's] working on a fix, which is blocked on a DeGraph issue. Feel free to up-vote it :)

Deliverables

• Migrate to a dedicated Gradle plugin for Degraph once such a plugin exists.

[marcphilipp]

@oehme Now that degraph 0.1.4 has been released, do you have time to continue working on the fix?

[oehme]

I will, when I come back from vacation in 2 weeks :)

Am 12.09.2016 04:49 schrieb "Marc Philipp" notifications@github.com:

@oehme https://github.com/oehme Now that degraph 0.1.4 has been
released, do you have time to continue working on the fix?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#483 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABIvdeJy5heiZkqvk3J-xBFkURJV7l43ks5qpQQYgaJpZM4Juroc
.

[schauder]

Minor thing: It's Degraph, not DeGraph

[schauder]

If the plugin in agnostic of JUnit (except for it's own test) It would be cool to have it with the the other Degraph modules. If interested, we can handle it via

1. PR to the Degraph repository
2. I'm willing to grant commit privileges to those doing most of the work
3. Migrate everything to a Degraph organisation and have second repo there

I'm open for alternatives, but would like to avoid the effect of Degraph artifacts coming from two places without an obvious connection.

[marcphilipp]

Minor thing: It's Degraph, not DeGraph

Fixed.

If the plugin in agnostic of JUnit (except for it's own test) It would be cool to have it with the the other Degraph modules.

Agreed! Let's get a first version for use with JUnit and then figure out how to contribute it to Degraph, ok?

[schauder]

Let's get a first version for use with JUnit and then figure out how to contribute it to Degraph, ok?

Sure.

[oehme]

I was initially planning to just write a script for the JUnit team, but
since there is broader interest, I'd be willing to start a real plugin.

You'll need to get an account on plugins.gradle.org so you can publish it.

Am 12.09.2016 12:23 schrieb "Jens Schauder" notifications@github.com:

If the plugin in agnostic of JUnit (except for it's own test) It would be
cool to have it with the the other Degraph modules. If interested, we can
handle it via

1. PR to the Degraph repository
2. I'm willing to grant commit privileges to those doing most of the
   work
3. Migrate everything to a Degraph organisation and have second repo
   there

I'm open for alternatives, but would like to avoid the effect of Degraph
artifacts coming from two places without an obvious connection.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#483 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABIvdbqdi-1Ghsmg0Wxr6FyVJzDqQVZ8ks5qpW3EgaJpZM4Juroc
.

[schauder]

No pressure. There is no point in having a half done plugin (that's why I never started one so far)

If out of this comes a code snippet that I can post somewhere as an example how to have Degraph run separately it would help a lot.

[oehme]

@schauder Why don't we schedule a hangout when I'm back? We could go through possible use cases and design a plugin together.

[marcphilipp]

@schauder @oehme Any news on the dedicated degraph Gradle plugin?

[oehme]

I have added my ideas to the Degraph issue tracker: riy/degraph#69

[schauder]

I'm sorry, no news yet. I just started my xmas vacation, so maybe I find some time.

[sormuras]

https://github.com/obecker/gradle-degraph ?

[sbrannen]

worth a try...