Eclipse Community Forums: Buckminster » The installable unit xxx has not been found.

Home » Archived » Buckminster » The installable unit xxx has not been found.

The installable unit xxx has not been found. [message #487746]

Thu, 24 September 2009 06:27

Eclipse User

I tried to adapt the mailapp product export.

I was able to build a p2 site.

When invoking action "create.product", ant will complain about the iu not been found.

What am I missing?

I could not understand what the build.properties in releng is good for. Could you please explain this:

category.id.mailapp=Mailapp Demo
category.members.mailapp=org.eclipse.buckminster.tutorial.ma ilapp.product.feature,\
org.eclipse.buckminster.tutorial.rcpp2.feature
category.description.mailapp=Demo build of RCP mailapp with p2 managment

What are those keys good for? There is nothing referencing them...

Re: The installable unit xxx has not been found. [message #487771 is a reply to message #487746]

Thu, 24 September 2009 07:24

Eclipse User

Hi Erdal,
Those properites describe how the categorization is made in the repository. This is described in more detail in Chapter
13, "Building a p2 Update Site" in the Buckminster book:

http://www.eclipse.org/downloads/download.php?file=/tools/bu ckminster/doc/BuckyBook.pdf

I need more info about the IU not being found. Can you provide a log? Running with Buckminster console debug level set
to DEBUG will print a fair amount of output.

Regards,
Thomas Hallgren

On 09/24/2009 12:27 PM, Erdal Karaca wrote:
> I tried to adapt the mailapp product export.
>
> I was able to build a p2 site.
>
> When invoking action "create.product", ant will complain about the iu
> not been found.
>
> What am I missing?
>
> I could not understand what the build.properties in releng is good for.
> Could you please explain this:
>
> category.id.mailapp=Mailapp Demo
> category.members.mailapp=org.eclipse.buckminster.tutorial.ma
> ilapp.product.feature,\
> org.eclipse.buckminster.tutorial.rcpp2.feature
> category.description.mailapp=Demo build of RCP mailapp with p2 managment
>
>
> What are those keys good for? There is nothing referencing them...
>

Re: The installable unit xxx has not been found. [message #487772 is a reply to message #487746]

Thu, 24 September 2009 07:29

Eclipse User

Erdal Karaca wrote:
> I tried to adapt the mailapp product export.
>
> I was able to build a p2 site.
>
> When invoking action "create.product", ant will complain about the iu
> not been found.
>
> What am I missing?
>
Did you by any chance specify '*' for platforms values?

From the Buckminster Book:
"To use create.product, and create.product.zip, you must supply a set of
properties for the platform you want to create the install for — i.e.
the target.* properties. The properties we used for the site.p2 build
itself can not be used as they specify all values as ‘*’ (any). This can
not be used for a install — the install is always for a particular
platform. You must also first run the site.p2 action to create the
repository or the repository will only contain content for the platform
you are running on and it will not be possible to generate zips for
other platforms."

Could that be the issue you are seeing?

> I could not understand what the build.properties in releng is good for.
> Could you please explain this:
>
> category.id.mailapp=Mailapp Demo
> category.members.mailapp=org.eclipse.buckminster.tutorial.ma
> ilapp.product.feature,\
> org.eclipse.buckminster.tutorial.rcpp2.feature
> category.description.mailapp=Demo build of RCP mailapp with p2 managment
>
>
> What are those keys good for? There is nothing referencing them...
>
These properties are used by the buckminster site.p2 action generated on
features. It is an alternative way to get categories into your p2
repository. If you do not have categories, the items in the repository
do not show up as being installable in the standard p2 UI (it only lists
things that are categorized).

You can read more about this in the Buckminster Book. (Available from
Buckminster Downloads).

Regards
- henrik

Re: The installable unit xxx has not been found. [message #489061 is a reply to message #487772]

Thu, 01 October 2009 08:15

Eclipse User

Thank you both!

I found the error:

I confused the product ID (in .product file) with the product definition ID (plugin.xml).

Previous Topic:	3.5.1 roll out causes many problems
Next Topic:	{fs:action.requirements} not found

Goto Forum:

-=] Back to Top [=-

Current Time: Fri Jul 18 13:55:47 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter