Re: [spaces-dev] some issues from spaces users...

[Thomas Hallgren <thomas@xxxxxxx>]

Henrik Lindberg wrote:
> Hi,
> I got the following questions and problems reported to me:
>
> - Can I publish a feature to a space?
Presently no, you can't. This was somewhat intentional for the first 
release since we wanted to show simplicity and hide the complexity 
introduced by features etc. from the users. One-click publishing and all 
that.

The good news is that we have anticipated this demand and the UpdateSite 
publisher underneath has the capabilities needed already. It knows about 
bundle groups (i.e. features) and the intention is to enhance the 
publisher so that it can manage features as well as plug-ins in the future.

> - When publishing, some plugins got the specified "external name", but 
> others are named after the plugin ID even when they have an external 
> name.
This should not be the case. Is there a difference in how the external 
name is expressed? I.e. could it be that in one case it's entered 
verbatim into the manifest but in another case it uses parameter 
substitution, i.e. %bundleName or similar?

> - When publishing two bundles A and B, and where A depends on B to the 
> same spaces update site, the dependency is not resolved when importing.
Not sure what you mean here. There is no way to import just 'A'. The 
importer will always import the site as a whole so dependency or not, 
both A and B should be imported. I'm probably misunderstanding 
something. Can you please elaborate?

- thomas