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

Cleanup references to spray in Scaladocs and tests #16113

Closed
jrudolph opened this issue Oct 21, 2014 · 1 comment
Closed

Cleanup references to spray in Scaladocs and tests #16113

jrudolph opened this issue Oct 21, 2014 · 1 comment

Comments

@jrudolph
Copy link
Member

Currently, there seem to be still some reference to "spray" classes in Scaladocs that need to be cleaned up. Less importantly, some tests are still spray-themed.

@jrudolph jrudolph added this to the streams-1.0 milestone Oct 21, 2014
@patriknw patriknw removed this from the streams-1.0 milestone Oct 24, 2014
@patriknw patriknw added the 1 - triaged Tickets that are safe to pick up for contributing in terms of likeliness of being accepted label Oct 24, 2014
@rkuhn rkuhn modified the milestone: stream-http-master Jan 11, 2016
@rkuhn rkuhn modified the milestones: stream-http-master, 2.4.2 Jan 19, 2016
@rkuhn rkuhn removed the 2 - pick next Used to mark issues which are next up in the queue to be worked on. The tag is non-binding label Jan 22, 2016
@rkuhn rkuhn added 3 - in progress Someone is working on this ticket and removed 1 - triaged Tickets that are safe to pick up for contributing in terms of likeliness of being accepted labels Feb 11, 2016
@rkuhn rkuhn assigned rkuhn and unassigned rkuhn Feb 11, 2016
@rkuhn
Copy link
Contributor

rkuhn commented Feb 12, 2016

We’ll leave the tests as they are, makes for nice trivia questions :-)

@rkuhn rkuhn closed this as completed in 5c205f7 Feb 12, 2016
@ktoso ktoso removed the 3 - in progress Someone is working on this ticket label Feb 17, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants