Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Buckminster » Problems materializing using workspace materializer
Problems materializing using workspace materializer [message #544297] Fri, 02 July 2010 09:04 Go to next message
Geejay is currently offline Geejay
Messages: 160
Registered: February 2010
Senior Member
I am trying to import an MSPEC in the Eclipse UI, Buckminter 3.6.

I get an error ERROR [0002] : IU
com.myapp.externalbundles.feature.group/1.0.0.201006291511 has no artifacts

I have three questions:

1) What is the best way to figure out why this is happening? When I look
into the workspace, the folder is there, but it contains no feature.xml...

2) How does Buckminster know, in the MailApp example, to materialize the
org.eclipse.buckminster.tutorial.* projects into the workspace, and the
"target platform" components such as the org.eclipse.rcp feature into the
TP?

3) The "source", e.g com.myapp.* projects are materialized into a sub-dir of
the workspace, in a "plugins" folder. How can I materialize them into the
workspace root? (I have already tried with mspecnode
materializer="workspace" workspaceLocation="${workspace.root}")

Thanks for any help.

Greg
Re: Problems materializing using workspace materializer [message #544440 is a reply to message #544297] Fri, 02 July 2010 16:27 Go to previous message
Henrik Lindberg is currently offline Henrik Lindberg
Messages: 2500
Registered: July 2009
Senior Member
Hi,

On 7/2/10 11:04 AM, geejay wrote:
> I am trying to import an MSPEC in the Eclipse UI, Buckminter 3.6.
>
> I get an error ERROR [0002] : IU
> com.myapp.externalbundles.feature.group/1.0.0.201006291511 has no artifacts
>
> I have three questions:
>
> 1) What is the best way to figure out why this is happening? When I look
> into the workspace, the folder is there, but it contains no feature.xml...
>
Turn on Debug logging (under Buckminster preferences)
Turn off multithreaded operation (to get log entries in understandable
order).

> 2) How does Buckminster know, in the MailApp example, to materialize the
> org.eclipse.buckminster.tutorial.* projects into the workspace, and the
> "target platform" components such as the org.eclipse.rcp feature into
> the TP?
>
In 3.6, Buckminster has defaults - binary stuff to TP, and the rest to
workspace. Before 3.6 an MSPEC had to be used and contain such a rule.

> 3) The "source", e.g com.myapp.* projects are materialized into a
> sub-dir of the workspace, in a "plugins" folder. How can I materialize
> them into the workspace root? (I have already tried with mspecnode
> materializer="workspace" workspaceLocation="${workspace.root}")
>
Are they source projects from a SCM, or source bundles? If they are
source bundles they are not considered "source" in the Buckminster sense
- i.e. they are not source for building. Is that what is happening here?

Regards
- henrik
Previous Topic:Format of target.os, target.ws, target.arch if not *
Next Topic:Setting pack200=true on site.p2 causes missing content.jar and artifacts.jar and binary
Goto Forum:
  


Current Time: Wed Oct 22 22:32:26 GMT 2014

Powered by FUDForum. Page generated in 0.01491 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software