[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [spaces-dev] some issues from spaces users...
|
I tested Mark Melvins Spaces update site at
http://public.xdrive.com/opc/XDPC-3675niWSqDiuOChpGLlIcv80ROHqooXe/
I made an attempt to import the source but that didn't work. Looking
further, I found that the generated area.rmap has no source entries. I
can see three possible causes for that:
1. Mark published his components before we fixed the bug that sometimes
caused incorrectly generated rmaps (the fix was made Wednesday morning
UTC last week).
2. Mark published his component first and added them to SVN second.
3. We still have have this problem although I'm not able to reproduce it.
I checked out the components from SVN and published them to a new update
site in my own XDrive space. That worked just fine. The result can be
imported from
http://public.xdrive.com/opc/XDPC-5212gD5amKac79vJPVhoXY5P2jWzdVVo/
I think the best course of action would be if Mark could simply
republish his three plug-ins.
With respect to the questions I'm still confused. Where does he see the
names that are sometimes "external" and sometimes not? I only see the
plug-in ID's in the spaces view. When does he encounter the dependency
resolution problem?
Regards,
Thomas Hallgren
Henrik Lindberg wrote:
I got this from Mark Melvin - take a look at what he published (go to
the EclipseCon talk page where he has a link to his update site) and
see what it looks like. I promised we would look into what he
published, but I have too busy to look myself.
The source of his things are published in the
eclipsesvn.cloudsmith.com repository.
Don't have more detail than that at this point - Mark said he would
write issues, but I thought a heads up was good.
Henrik Lindberg
henrik.lindberg@xxxxxxxxxxxxxx
On Mar 19, 2008, at 8:12 PM, Thomas Hallgren wrote:
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
_______________________________________________
spaces-dev mailing list
spaces-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/spaces-dev
_______________________________________________
spaces-dev mailing list
spaces-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/spaces-dev