Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Groovy Extensions for RxJava and Reactive Streams #595

Closed
danveloper opened this issue Mar 3, 2015 · 11 comments
Closed

Groovy Extensions for RxJava and Reactive Streams #595

danveloper opened this issue Mar 3, 2015 · 11 comments
Assignees

Comments

@danveloper
Copy link
Member

Groovy extensions provide the ability to add instance-level "helper" methods to different types. We can use this to make the translation from Observable and Publisher to Promise (and vice-versa) a more-seamless integration for Groovy-based applications.

@danveloper
Copy link
Member Author

resolved via fb9286e

@ldaley
Copy link
Member

ldaley commented Mar 4, 2015

Where did we land on the version attribute?

@ldaley ldaley reopened this Mar 4, 2015
@ldaley
Copy link
Member

ldaley commented Mar 4, 2015

Also, needs a milestone set before closing.

@ldaley ldaley assigned ldaley and danveloper and unassigned ldaley Mar 4, 2015
@danveloper
Copy link
Member Author

@melix informs that the moduleVersion field is simply used for reporting purposes. In our case, it seems rather unlikely that an application would pull in two of the same ratpack-core/rx jars, so I'm not convinced that we really need it at all. (It works fine without it defined.)

@danveloper danveloper added this to the release-0.9.15 milestone Mar 4, 2015
@davidmc24
Copy link
Contributor

@melix
Copy link
Contributor

melix commented Mar 4, 2015

Yes, sorry @danveloper if it wasn't clear: the descriptor and version is required. Groovy will complain if it finds two versions of the same module on classpath.

@danveloper
Copy link
Member Author

@danveloper
Copy link
Member Author

Good point -- I should have noted that the field is present, but not assigned. We can assign a dummy value if it makes it easier to understand. Thoughts?

@johnrengelman
Copy link
Member

Might as well call it 1.0.0 since it's our first version. Then if we ever change it, we can up the number.

@ldaley
Copy link
Member

ldaley commented Mar 4, 2015

I'm not as across the details as you guys, but just hardcoding 1.0.0 seems reasonable to me.

@ldaley ldaley closed this as completed Mar 30, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants