Ahhh! Interesting solution to your problem ... funky but using tested
features!
On 4/25/19 1:23 AM, Norbert Hartl wrote:
Dale,
looking at my code I really like the idea solving my white label
problem with polymorphism. It makes things much easier IMHO. So ended
up doing something like having
Dale,
looking at my code I really like the idea solving my white label problem with
polymorphism. It makes things much easier IMHO. So ended up doing something
like having something like this
BaselineOfCoreProduct
…
spec group: ‚whiteLabel‘ with: #( ‚BaselineOfWhiteLabelProduct‘ )
…
and do
> Am 25.04.2019 um 01:13 schrieb Dale Henrichs
> :
>
>
> On 4/24/19 3:08 PM, Norbert Hartl wrote:
>> I don‘t have an idea how to achieve this with a group. It is about changing
>> the number of dependencies of one package.
>
> There's load order and there's grouping...
>
> If you are using
On 4/24/19 3:08 PM, Norbert Hartl wrote:
I don‘t have an idea how to achieve this with a group. It is about changing the
number of dependencies of one package.
There's load order and there's grouping...
If you are using #linear loads for a BaselineOf then hard dependencies
(Metacello requi
> Am 24.04.2019 um 19:40 schrieb Dale Henrichs
> :
>
> Do I understand you correctly that the BaselineOfWhiteLabelProduct is a
> subclass of BaselineOfCoreProduct?
>
Yes as I wrote.
> If so, I have no idea what would happen and it certainly has never been
> tested ... and as I think about
Do I understand you correctly that the BaselineOfWhiteLabelProduct is a
subclass of BaselineOfCoreProduct?
If so, I have no idea what would happen and it certainly has never been
tested ... and as I think about this I can see that there would
definitely be problems ... I think you are lucky th
I’m trying to customize our current project with multiple baselines meaning
BaselineOfCoreProduct and BaselineOfWhiteLabelProduct. The latter is a subclass
of the former. My problem is that I don’t know which way to choose for loading
because
Metacello new
baseline: #WhiteLabelProduct
l
