Hello Peter,
looks like you have stumbled into a bug, I also tracked this internally for improvement in one of the next versions.
Unfortunately there is no out-of-box workaround, however, you can apply a custom value resolver [1] (requires minimal coding, possibly as groovy script).
The following snippet shows exactly what you want for the “config” repo, you can replace the repository ID in the code to your application configuration.
static class DefaultWithConfigRepoValueResolver extends ValueResolver
{
public DefaultWithConfigRepoValueResolver()
{
super(DEFAULT_CONFIGREPOSITORY);
}
@Override
public String handle(Value value)
{
final String configRepoId = PlatformRepositoryResolver.getConfigRepositoryName();
return LinkBuilder.createDefault(value).withLabelRepository(configRepoId).withRepository(configRepoId).build();
}
}
Hope this helps,
Andreas
[1] http://help.fluidops.com/resource/Help:ValueResolverExtensions#Value_resolver_extensions
--
You received this message because you are subscribed to the Google Groups "Information Workbench Discussions" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
iwb-discussio...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.