On July 28, 2017 3:41:37 PM GMT+02:00, Denis Kudriashov
wrote:
>And if you really have Towergame-Tests package then you will probably
>define it as
>
> spec package: 'Towergame-Tests' with: [ spec requires: #('Towergame'
>'Mocketry') ].
>
>And then Tests group can include only Towergame-Tests
On July 28, 2017 3:41:37 PM GMT+02:00, Denis Kudriashov
wrote:
>And if you really have Towergame-Tests package then you will probably
>define it as
>
> spec package: 'Towergame-Tests' with: [ spec requires: #('Towergame'
>'Mocketry') ].
>
>And then Tests group can include only Towergame-Tests
And if you really have Towergame-Tests package then you will probably
define it as
spec package: 'Towergame-Tests' with: [ spec requires: #('Towergame'
'Mocketry') ].
And then Tests group can include only Towergame-Tests package because
Mocketry will be loaded as dependency.
2017-07-28 15:39
You need to specify groups for your project:
spec
group: 'default' with: #('Core' 'Tests' );
group: 'Core' with: #('Towergame' );
group: 'Tests' with: #('Towergame-Tests' 'Mocketry')
Then your script will load default group with everything. And to load Core
group use "load: #(Core)" instread of
Hello!
I'd like to ask what is the equivalent of devDependencies (dependencies
to be loaded only when developing, but not when in profuction / used as
a dependency) of a baseline.
My baseline method looks like:
baseline: spec
spec for: #common do: [
spec package: 'Towergame' wi
