You can still keep your own custom version of spock and have it separate
from your project and locally publish your own custom spock artifacts.
On May 23, 2011 1:38 PM, "Jan Ahrens" <[email protected]> wrote:
> Hi Eric, Hi Merlyn,
>
> thanks for your suggestions.
>
>> Can you not depend on the artifacts generated by the subproject instead?
>
> Yes I could do that, but I want to be able to make modifications to the
> sources of Spock along with my own source files. The way I want to use
> gradle is run a single 'gradle test' from the root project.
>
>> Actually, I got it working with the /spock/settings.gradle file as well.
>> You just need to reference the projects from the parent:
>> [code src=/spock/settings.gradle]
>> include 'spock:spock-core', 'spock:spock-specs'
>> [/code]
>
> This works well, but I'm losing the ability to run 'gradle' from inside
> the 'spock' directory.
>
> I thought it would be possible to get gradle setup to run the
> sub-project separately (I have included it as a git-submodule).
> To my understanding gradle just needs to have a notation of a relative
> project-path, which I thought was already there. Maybe I misunderstood
> the multi-project setup.
>
> If there is no other way, I'll stick with this approach.
>
> Thanks for your help :-)
>
> Cheers,
> Jan
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
> http://xircles.codehaus.org/manage_email
>
>
