These are chat archives for jruby-gradle/jruby-gradle-plugin

3rd
Jul 2015
R. Tyler Croy
@rtyler
Jul 03 2015 15:46
alrighty, taking a look at the integtest plugin now
@ysb33r this plugin doesn't appear to provide any of the runtime needs that I would have
Schalk W. Cronjé
@ysb33r
Jul 03 2015 15:49
what do you want to do?
R. Tyler Croy
@rtyler
Jul 03 2015 15:49
to actually write the tests
it's handy enough to where I could remove some crap in my project's build.gradle, but this doesn't change the work I think I have to do to write the tests
something more complex than ProjectBuilder I suppose
in the context of a single spock-based integration test I need to create a project (got that), and then execute tasks in the temp project dir and inspect the artifacts that have been output
Schalk W. Cronjé
@ysb33r
Jul 03 2015 15:51
well you can set the projectDir when you create the project via ProjectBuilder. You can then also set the buildDir on that project
R. Tyler Croy
@rtyler
Jul 03 2015 15:52
yeah, that's no big deal
Schalk W. Cronjé
@ysb33r
Jul 03 2015 15:53
maybe you need to create Spock base class that does some of the work for you?
R. Tyler Croy
@rtyler
Jul 03 2015 15:54
it's the task execution part I'm unclear on
man the inline javadocs in intellij are complete shit
I still have to go open a web browser to get something useful
Schalk W. Cronjé
@ysb33r
Jul 03 2015 15:58
I am missing something in your question… the integration spec stuff I did for base, wouldn;t that just suffice?
R. Tyler Croy
@rtyler
Jul 03 2015 15:58
I suppose I can just go copy that :)
rtyler @rtyler frownies
R. Tyler Croy
@rtyler
Jul 03 2015 17:14
@ysb33r modelling after the integTests in base, I'm not seeing a means to execute a task that isn't an Exec, e.g. assemble
rtyler @rtyler digs deep into org.gradle.* internals
R. Tyler Croy
@rtyler
Jul 03 2015 17:17
I wonder if I can grab the testkit folks are talking about on the dev list for 2.x
hm the nebula test plugin might be what I need here
R. Tyler Croy
@rtyler
Jul 03 2015 17:31
@ysb33r this code got merged for Travis->Bintray CI/CD
@ysb33r any objections to getting continuous with the plugins? :D
Schalk W. Cronjé
@ysb33r
Jul 03 2015 17:33
I saw it mentioned on twitter. Would be interesting.
R. Tyler Croy
@rtyler
Jul 03 2015 17:37
if I can get good integration tests working for this other plugin I might use that as a guinea pig since it's a bit smaller
I'm also planning on adding better GH pages/docs support here
while I'm fucking around
Schalk W. Cronjé
@ysb33r
Jul 03 2015 17:44
I've changed groovy-vfs, so that all of the docs are built off the project and then copied to the website. No more editing the gh-pages branch, just commits.
Even included the gh-pages branch via a git submodule.not sure if that is a good approach, but so far it works.
Schalk W. Cronjé
@ysb33r
Jul 03 2015 18:34
without it. I started with it, but it did not quite do what I wanted.
R. Tyler Croy
@rtyler
Jul 03 2015 19:33
well hot dog! integration test running and producing the artifacts I need to inspect
huzzah
Schalk W. Cronjé
@ysb33r
Jul 03 2015 19:34
did you try nebula-test?
R. Tyler Croy
@rtyler
Jul 03 2015 19:36
that's what I'm using
poorly documented but who am I to talk :)
Schalk W. Cronjé
@ysb33r
Jul 03 2015 21:16
looking forward to see what the outcome is