Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [tycho-user] Creating a Product and then updating via Update Site

2014-03-11 22:49 GMT+01:00 Laurent PETIT <laurent.petit@xxxxxxxxx>:
So we share the symptom building the same product on different machines, that's reassuring.

The product does next to nothing: it gathers classical Eclipse features, adds a feature which just references a branding, and a product definition. No java code, no Eclipse extension.

As you suggest, I will try with a "raw" Kepler SR1, for instance the one for java, and see what happens when trying to update either JDT, either P2.

I tried with a "raw" "Eclipse Keper SR1 for Java Developer" ( eclipse-java-kepler-SR1-macosx-cocoa-x86_64.tar.gz ), and tried updating. Everything worked well.
Seems like we may be comparing oranges and apples, though, because Eclipse for java has only the product as root, and no other root feature...

I also updated the "my-ide" repo because there was a little typo in my-ide.p2.inf ( missing \ at the end of the next-to-last line), but there was no difference in the encountered problem.

I'm really starting to consider whether I'm on a dead-end road trying to get everything as a root feature, since it's a notion I barely understand, and p2 is still an impenetrable black box to me :-( 


2014-03-11 22:42 GMT+01:00 Jeff MAURY <jeffmaury@xxxxxxxxxxxxx>:


I think this is related to the update of P2 related features.
Here is what I did.

From a scratch build:

1) Update JDT -> restart fast -> update P2 -> update long
2) Update P2 -> restart long
3) Update JDT -> restart fast -> update everything else -> restart long

I don't know if this is related to your product, maybe testing the same with from Kepler SR1 fo Java will help.


On Tue, Feb 4, 2014 at 4:24 PM, Laurent PETIT <laurent.petit@xxxxxxxxx> wrote:
Hello Paul, and Mikhail,

seems like setting the right namespace in ccw.p2.inf did the trick !

Thus I was able to skip the "manual" installation of the IU => I now only see the feature under the product's node in the About page, and seems like I am able to update ccw feature.

Should I be able to just extend this knowledge to all other features inside my product (JDT, EGit, Platform, etc.) and expect it to work ?

2014-02-04 Paul Webster <pwebster@xxxxxxxxxxxxxxxxxxx>:
Hi Laurent,

On Thu, Jan 30, 2014 at 4:42 PM, Laurent PETIT <laurent.petit@xxxxxxxxx> wrote:

I'm not sure I understand what you mean by "you need to find its 'inclusion' point [...] and use the p2.inf ...". It's the "inclusion point" that I don't understand, and maybe I'm missing something important ?

Mikail's got it right for inclusion points, namespaces, and upper bounds.
I kind of remember I attempted to both let my feature declared in my .product file and broaden the version range by adding requires in the product's p2.inf file. As a result, I was seing, in the About page of the resulting product, the feature declared 2 times in the graphical tree: once as a child of the product, and once as a separate root in the tree. Is that expected, or is it symptomatic of a mistake?

That's expected.  You can see IUs in root locations as well as under your product.


Paul Webster
Hi floor.  Make me a sammich! - GIR

tycho-user mailing list

tycho-user mailing list


"Legacy code" often differs from its suggested alternative by actually working and scaling.
 - Bjarne Stroustrup

tycho-user mailing list

Back to the top