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

Merge yagni-test and yagni repositories #32

Open
venantius opened this issue Aug 27, 2015 · 1 comment
Open

Merge yagni-test and yagni repositories #32

venantius opened this issue Aug 27, 2015 · 1 comment

Comments

@venantius
Copy link
Owner

This has been bothering me for a while, but I'm starting to get to the point where it's really annoying me. Maintaining separate directories for the test project and the main repo screws with the whole point of having CI set up; it would be a much better idea for me to maintain both directory structures in a single project.

Of course, now that I say that I can't find a valid example of the directory structure I want. Hm.

I think a starting point would be to split this project into two root directories with two separate projects: yagni, and lein-yagni. That way I can test the former cleanly without hitting, say, Leiningen errors. Then lein-yagni can run tests against the associated version of yagni. I don't see a lot of good examples of actually testing plugin behavior v. library behavior but at a bare minimum checking to see that leiningen is still capable of running with the plugin on the path is a good start.

@venantius
Copy link
Owner Author

Ref. #20

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

1 participant