Discussion:
Creating a Product and then updating via Update Site
(too old to reply)
Laurent PETIT
2014-01-16 13:48:20 UTC
Permalink
Hello,

I was able to create a standalone Product embedding my Clojure plugin
Counterclockwise ( https://github.com/laurentpetit/ccw ).

There's something not working yet: once the product is installed, users are
unable to update the counterclockwise plugin via the counterclockwise
update site, meaning that they need to download and install a new version
of the Product everytime they want to upgrade ..

I must be missing something, obviously. If anyone has suggestions (you can
also quick check Counterclockwise's github repo :
https://github.com/laurentpetit/ccw ) ...

I have already done the following things:

- declared "ccw.feature" in the features of the product :
https://github.com/laurentpetit/ccw/blob/master/ccw.product/ccw.product#L255

- additional step in maven to install the ccw.feature :
https://github.com/laurentpetit/ccw/blob/master/ccw.product/pom.xml#L80

There must be also some fundamental knowledge that I don't have right now
...

Regards,
--
Laurent Petit
S***@de.rhenus.com
2014-01-16 14:10:06 UTC
Permalink
Hi Laurent,

maybe the following link can help you

http://wiki.eclipse.org/Equinox/p2/Adding_Self-Update_to_an_RCP_Application

It describes how to add self update mechanismn to a RCP application.

Best regards,

Sandra


IT Solutions / Software Development
Rhenus Freight Network GmbH, Rhenus-Platz 1, 59439 Holzwickede,
Deutschland
Tel: +49 (0)2301 29-2236, Fax: +49 (0)2301 29-17253
***@de.rhenus.com, www.rhenus.com;

Sitz: Rhenus-Platz 1, 59439 Holzwickede; AG Hamm, HRB 7788;
GeschÀftsfÌhrerin: Petra Finke, St.-Nr. 316/5950/1308;UST-ID-Nr.: DE 288
342 692

Wir arbeiten ausschließlich auf Grundlage der Allgemeinen Deutschen
Spediteursbedingungen (ADSp), jeweils neueste Fassung. Diese beschrÀnken
in Ziffer 23 ADSp die gesetzliche Haftung fÌr GÌterschÀden nach § 431 HGB
fÌr SchÀden im speditionellen Gewahrsam auf EUR 5,00/kg; bei multimodalen
Transporten unter Einschluss einer Seebeförderung auf 2 SZR/kg sowie
ferner je Schadenfall bzw. –ereignis auf EUR 1 Mio. bzw. EUR 2 Mio. oder 2
SZR/kg je nachdem, welcher Betrag höher ist. ErgÀnzend wird vereinbart,
dass (1) Ziffer 27 ADSp weder die Haftung des Spediteurs noch die
Zurechnung des Verschuldens von Leuten und sonstigen Dritten abweichend
von gesetzlichen Vorschriften wie § 507 HGB, Art. 25 MÜ, Art. 36 CIM, Art
20, 21 CMNI zu Gunsten des Auftraggebers erweitert, (2) der Spediteur als
Verfrachter in den in § 512 Abs. 2 Nr. 1 HGB aufgefÌhrten FÀllen des
nautischen Verschulden oder Feuer an Bord nur fÃŒr eigenes Verschulden
haftet und (3) der Spediteur als FrachtfÃŒhrer im Sinne der CMNI unter den
in Art. 25 Abs. 2 CMNI genannten Voraussetzungen nicht fÃŒr nautisches
Verschulden, Feuer an Bord oder MÀngel des Schiffes haftet. ErfÌllungsort
und Gerichtstand fÃŒr beide Teile ist Unna.



Von: Laurent PETIT <***@gmail.com>
An: Tycho user list <tycho-***@eclipse.org>,
Datum: 16.01.2014 14:49
Betreff: [tycho-user] Creating a Product and then updating via
Update Site
Gesendet von: tycho-user-***@eclipse.org



Hello,

I was able to create a standalone Product embedding my Clojure plugin
Counterclockwise ( https://github.com/laurentpetit/ccw ).

There's something not working yet: once the product is installed, users
are unable to update the counterclockwise plugin via the counterclockwise
update site, meaning that they need to download and install a new version
of the Product everytime they want to upgrade ..

I must be missing something, obviously. If anyone has suggestions (you can
also quick check Counterclockwise's github repo :
https://github.com/laurentpetit/ccw ) ...

I have already done the following things:

- declared "ccw.feature" in the features of the product :
https://github.com/laurentpetit/ccw/blob/master/ccw.product/ccw.product#L255


- additional step in maven to install the ccw.feature :
https://github.com/laurentpetit/ccw/blob/master/ccw.product/pom.xml#L80

There must be also some fundamental knowledge that I don't have right now
...

Regards,

--
Laurent Petit_______________________________________________
tycho-user mailing list
tycho-***@eclipse.org
https://dev.eclipse.org/mailman/listinfo/tycho-user
Paul Webster
2014-01-16 14:14:30 UTC
Permalink
Post by Laurent PETIT
There's something not working yet: once the product is installed, users
are unable to update the counterclockwise plugin via the counterclockwise
update site, meaning that they need to download and install a new version
of the Product everytime they want to upgrade ..
See
http://aniefer.blogspot.ca/2009/07/composing-and-updating-custom-eclipse.htmlwhich
has a section on upgrading components without upgrading the entire
product.

If I'm reading it correctly, you need your product p2.inf to open up the
ranges on the features the product include.

Later,
Paul
--
Paul Webster
Hi floor. Make me a sammich! - GIR
Laurent PETIT
2014-01-16 14:23:18 UTC
Permalink
Thank you both, Paul and Sandra, I will take a look at these links and try
things ASAP.
Post by Laurent PETIT
There's something not working yet: once the product is installed, users
are unable to update the counterclockwise plugin via the counterclockwise
update site, meaning that they need to download and install a new version
of the Product everytime they want to upgrade ..
See
http://aniefer.blogspot.ca/2009/07/composing-and-updating-custom-eclipse.htmlwhich has a section on upgrading components without upgrading the entire
product.
If I'm reading it correctly, you need your product p2.inf to open up the
ranges on the features the product include.
Later,
Paul
--
Paul Webster
Hi floor. Make me a sammich! - GIR
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
Laurent PETIT
2014-01-16 21:49:04 UTC
Permalink
Hi Paul,

So thanks to you and the link, I've been able to fix my problem. I had to
remove the ccw feature definition from the product features list, and
instead add a requires.x.name to my product's ccw.p2.inf file.

And the final step is to manually invoke the Director to install
ccw.feature.feature.group to the product after the fact.

This is why I'm coming back to you. Since I've removed ccw.feature from the
product features list, I don't find feature artifacts in my product's
target/repository repository anymore. Before that, it was easy to point the
Director to this directory.
So Ive pointed instead the directory to a relative path like
../ccw.updatesite/target/repository.

And it is working for ccw.feature, great !

BUT

I'd also like to make other features updatable independently by the user:
egit, eclipse-colorthemes for instance.
And then starts the redundancy : I have already declared where to find
these feature in my ccw.target.e47 target definition, but I don't know how
to reuse this.
Instead, I find myself repeating tycho-eclipserun-plugin calls, an for each
call, pasting the location of external p2 repositories ...

There must be a better way with tycho, right ? I'm sure I'm not using it to
its full potential ....

thanks in advance for any guidance,
--
Laurent
Post by Laurent PETIT
Thank you both, Paul and Sandra, I will take a look at these links and try
things ASAP.
Post by Laurent PETIT
There's something not working yet: once the product is installed, users
are unable to update the counterclockwise plugin via the counterclockwise
update site, meaning that they need to download and install a new version
of the Product everytime they want to upgrade ..
See
http://aniefer.blogspot.ca/2009/07/composing-and-updating-custom-eclipse.htmlwhich has a section on upgrading components without upgrading the entire
product.
If I'm reading it correctly, you need your product p2.inf to open up the
ranges on the features the product include.
Later,
Paul
--
Paul Webster
Hi floor. Make me a sammich! - GIR
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
Jeff MAURY
2014-01-18 07:51:14 UTC
Permalink
Laurent,

is it still relevant ? I thought you've fixed it ?

Jeff
Post by Laurent PETIT
Hi Paul,
So thanks to you and the link, I've been able to fix my problem. I had to
remove the ccw feature definition from the product features list, and
instead add a requires.x.name to my product's ccw.p2.inf file.
And the final step is to manually invoke the Director to install
ccw.feature.feature.group to the product after the fact.
This is why I'm coming back to you. Since I've removed ccw.feature from
the product features list, I don't find feature artifacts in my product's
target/repository repository anymore. Before that, it was easy to point the
Director to this directory.
So Ive pointed instead the directory to a relative path like
../ccw.updatesite/target/repository.
And it is working for ccw.feature, great !
BUT
egit, eclipse-colorthemes for instance.
And then starts the redundancy : I have already declared where to find
these feature in my ccw.target.e47 target definition, but I don't know how
to reuse this.
Instead, I find myself repeating tycho-eclipserun-plugin calls, an for
each call, pasting the location of external p2 repositories ...
There must be a better way with tycho, right ? I'm sure I'm not using it
to its full potential ....
thanks in advance for any guidance,
--
Laurent
Post by Laurent PETIT
Thank you both, Paul and Sandra, I will take a look at these links and
try things ASAP.
Post by Laurent PETIT
There's something not working yet: once the product is installed, users
are unable to update the counterclockwise plugin via the counterclockwise
update site, meaning that they need to download and install a new version
of the Product everytime they want to upgrade ..
See
http://aniefer.blogspot.ca/2009/07/composing-and-updating-custom-eclipse.htmlwhich has a section on upgrading components without upgrading the entire
product.
If I'm reading it correctly, you need your product p2.inf to open up the
ranges on the features the product include.
Later,
Paul
--
Paul Webster
Hi floor. Make me a sammich! - GIR
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
--
Jeff MAURY


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

http://www.jeffmaury.com
http://riadiscuss.jeffmaury.com
http://www.twitter.com/jeffmaury
Laurent PETIT
2014-01-18 08:02:25 UTC
Permalink
Hi Jeff,
Post by S***@de.rhenus.com
Laurent,
is it still relevant ? I thought you've fixed it ?
Actually, I have since thursday been able to do a lot of trials and errors,
thanks to the links, thanks to you ...

I haven't had the time to inform you, but I haven't been able to make the
"intermediate product feature" solution work.
Maybe I have misunderstood some explanation:

- I have created a ccw.product.feature feature, and now my ccw product
includes only this feature in ccw.product
- I have a new tycho module for ccw.product.feature, and it basically
declares all the features which were included directly in the product (Rcp,
Application, JDT, CCW, EclipsecolorTheme, EGit, ...)

The Tycho builds a product, but I'm still unable to update eg CCW via the
update site.

You were talking about a possible remaining issue with "root feature(s)"
with this solution, I didn't at the time understand what you meant, maybe
it's the missing piece ... ?
Post by S***@de.rhenus.com
Jeff
Post by Laurent PETIT
Hi Paul,
So thanks to you and the link, I've been able to fix my problem. I had to
remove the ccw feature definition from the product features list, and
instead add a requires.x.name to my product's ccw.p2.inf file.
And the final step is to manually invoke the Director to install
ccw.feature.feature.group to the product after the fact.
This is why I'm coming back to you. Since I've removed ccw.feature from
the product features list, I don't find feature artifacts in my product's
target/repository repository anymore. Before that, it was easy to point the
Director to this directory.
So Ive pointed instead the directory to a relative path like
../ccw.updatesite/target/repository.
And it is working for ccw.feature, great !
BUT
I'd also like to make other features updatable independently by the
user: egit, eclipse-colorthemes for instance.
And then starts the redundancy : I have already declared where to find
these feature in my ccw.target.e47 target definition, but I don't know how
to reuse this.
Instead, I find myself repeating tycho-eclipserun-plugin calls, an for
each call, pasting the location of external p2 repositories ...
There must be a better way with tycho, right ? I'm sure I'm not using it
to its full potential ....
thanks in advance for any guidance,
--
Laurent
Post by Laurent PETIT
Thank you both, Paul and Sandra, I will take a look at these links and
try things ASAP.
Post by Laurent PETIT
There's something not working yet: once the product is installed,
users are unable to update the counterclockwise plugin via the
counterclockwise update site, meaning that they need to download and
install a new version of the Product everytime they want to upgrade ..
See
http://aniefer.blogspot.ca/2009/07/composing-and-updating-custom-eclipse.htmlwhich has a section on upgrading components without upgrading the entire
product.
If I'm reading it correctly, you need your product p2.inf to open up
the ranges on the features the product include.
Later,
Paul
--
Paul Webster
Hi floor. Make me a sammich! - GIR
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
--
Jeff MAURY
"Legacy code" often differs from its suggested alternative by actually
working and scaling.
- Bjarne Stroustrup
http://www.jeffmaury.com
http://riadiscuss.jeffmaury.com
http://www.twitter.com/jeffmaury
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
Lars Vogel
2014-01-23 13:27:53 UTC
Permalink
Hi Laurent,

AFAIK you want the feature what is hopefully delivered with the next Tycho
release, install root level features into product install.

See https://bugs.eclipse.org/bugs/show_bug.cgi?id=361722.

Best regards, Lars
Post by Laurent PETIT
Hi Jeff,
Post by S***@de.rhenus.com
Laurent,
is it still relevant ? I thought you've fixed it ?
Actually, I have since thursday been able to do a lot of trials and
errors, thanks to the links, thanks to you ...
I haven't had the time to inform you, but I haven't been able to make the
"intermediate product feature" solution work.
- I have created a ccw.product.feature feature, and now my ccw product
includes only this feature in ccw.product
- I have a new tycho module for ccw.product.feature, and it basically
declares all the features which were included directly in the product (Rcp,
Application, JDT, CCW, EclipsecolorTheme, EGit, ...)
The Tycho builds a product, but I'm still unable to update eg CCW via the
update site.
You were talking about a possible remaining issue with "root feature(s)"
with this solution, I didn't at the time understand what you meant, maybe
it's the missing piece ... ?
Post by S***@de.rhenus.com
Jeff
Post by Laurent PETIT
Hi Paul,
So thanks to you and the link, I've been able to fix my problem. I had
to remove the ccw feature definition from the product features list, and
instead add a requires.x.name to my product's ccw.p2.inf file.
And the final step is to manually invoke the Director to install
ccw.feature.feature.group to the product after the fact.
This is why I'm coming back to you. Since I've removed ccw.feature from
the product features list, I don't find feature artifacts in my product's
target/repository repository anymore. Before that, it was easy to point the
Director to this directory.
So Ive pointed instead the directory to a relative path like
../ccw.updatesite/target/repository.
And it is working for ccw.feature, great !
BUT
I'd also like to make other features updatable independently by the
user: egit, eclipse-colorthemes for instance.
And then starts the redundancy : I have already declared where to find
these feature in my ccw.target.e47 target definition, but I don't know how
to reuse this.
Instead, I find myself repeating tycho-eclipserun-plugin calls, an for
each call, pasting the location of external p2 repositories ...
There must be a better way with tycho, right ? I'm sure I'm not using it
to its full potential ....
thanks in advance for any guidance,
--
Laurent
Post by Laurent PETIT
Thank you both, Paul and Sandra, I will take a look at these links and
try things ASAP.
On Thu, Jan 16, 2014 at 8:48 AM, Laurent PETIT <
Post by Laurent PETIT
There's something not working yet: once the product is installed,
users are unable to update the counterclockwise plugin via the
counterclockwise update site, meaning that they need to download and
install a new version of the Product everytime they want to upgrade ..
See
http://aniefer.blogspot.ca/2009/07/composing-and-updating-custom-eclipse.htmlwhich has a section on upgrading components without upgrading the entire
product.
If I'm reading it correctly, you need your product p2.inf to open up
the ranges on the features the product include.
Later,
Paul
--
Paul Webster
Hi floor. Make me a sammich! - GIR
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
--
Jeff MAURY
"Legacy code" often differs from its suggested alternative by actually
working and scaling.
- Bjarne Stroustrup
http://www.jeffmaury.com
http://riadiscuss.jeffmaury.com
http://www.twitter.com/jeffmaury
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
Laurent PETIT
2014-01-23 13:52:43 UTC
Permalink
Thanks for the information, Lars !

Do I understand right that when the bug 361722 is solved in Tycho, this
will be a way to automate what is described here:
http://aniefer.blogspot.fr/2009/07/composing-and-updating-custom-eclipse.html?

If so, then it's great. I have currently made appropriate changes to my
build to do what is described in the blog post. But since it leads to lots
of configuration in my product's pom.xml, as well as duplications of
information (duplicating what's in the target platform for the root
features repositories, for instance), I have currently only done that for 1
feature, my own plugin's feature. Far from ideal, then, because lots (if
not all) of the other features included ( Eclipse default features, Eclipse
colortheme, EGit, m2e, etc., etc. ) could use the same treatment.

Cheers,
--
Laurent
Post by S***@de.rhenus.com
Hi Laurent,
AFAIK you want the feature what is hopefully delivered with the next Tycho
release, install root level features into product install.
See https://bugs.eclipse.org/bugs/show_bug.cgi?id=361722.
Best regards, Lars
Post by Laurent PETIT
Hi Jeff,
Post by S***@de.rhenus.com
Laurent,
is it still relevant ? I thought you've fixed it ?
Actually, I have since thursday been able to do a lot of trials and
errors, thanks to the links, thanks to you ...
I haven't had the time to inform you, but I haven't been able to make the
"intermediate product feature" solution work.
- I have created a ccw.product.feature feature, and now my ccw product
includes only this feature in ccw.product
- I have a new tycho module for ccw.product.feature, and it basically
declares all the features which were included directly in the product (Rcp,
Application, JDT, CCW, EclipsecolorTheme, EGit, ...)
The Tycho builds a product, but I'm still unable to update eg CCW via the
update site.
You were talking about a possible remaining issue with "root feature(s)"
with this solution, I didn't at the time understand what you meant, maybe
it's the missing piece ... ?
Post by S***@de.rhenus.com
Jeff
Post by Laurent PETIT
Hi Paul,
So thanks to you and the link, I've been able to fix my problem. I had
to remove the ccw feature definition from the product features list, and
instead add a requires.x.name to my product's ccw.p2.inf file.
And the final step is to manually invoke the Director to install
ccw.feature.feature.group to the product after the fact.
This is why I'm coming back to you. Since I've removed ccw.feature from
the product features list, I don't find feature artifacts in my product's
target/repository repository anymore. Before that, it was easy to point the
Director to this directory.
So Ive pointed instead the directory to a relative path like
../ccw.updatesite/target/repository.
And it is working for ccw.feature, great !
BUT
I'd also like to make other features updatable independently by the
user: egit, eclipse-colorthemes for instance.
And then starts the redundancy : I have already declared where to find
these feature in my ccw.target.e47 target definition, but I don't know how
to reuse this.
Instead, I find myself repeating tycho-eclipserun-plugin calls, an for
each call, pasting the location of external p2 repositories ...
There must be a better way with tycho, right ? I'm sure I'm not using
it to its full potential ....
thanks in advance for any guidance,
--
Laurent
Post by Laurent PETIT
Thank you both, Paul and Sandra, I will take a look at these links and
try things ASAP.
On Thu, Jan 16, 2014 at 8:48 AM, Laurent PETIT <
Post by Laurent PETIT
There's something not working yet: once the product is installed,
users are unable to update the counterclockwise plugin via the
counterclockwise update site, meaning that they need to download and
install a new version of the Product everytime they want to upgrade ..
See
http://aniefer.blogspot.ca/2009/07/composing-and-updating-custom-eclipse.htmlwhich has a section on upgrading components without upgrading the entire
product.
If I'm reading it correctly, you need your product p2.inf to open up
the ranges on the features the product include.
Later,
Paul
--
Paul Webster
Hi floor. Make me a sammich! - GIR
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
--
Jeff MAURY
"Legacy code" often differs from its suggested alternative by actually
working and scaling.
- Bjarne Stroustrup
http://www.jeffmaury.com
http://riadiscuss.jeffmaury.com
http://www.twitter.com/jeffmaury
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
Lars Vogel
2014-01-23 18:08:34 UTC
Permalink
Hi Laurent,

I'm not sure how the Tycho committer are planning to solve this. I
personally hope for a Tycho flag which tells Tycho to install all features
as root level features. I think that is also what EPP would need, but also
I'm not sure here.

Best regards, Lars
Post by Laurent PETIT
Thanks for the information, Lars !
Do I understand right that when the bug 361722 is solved in Tycho, this
http://aniefer.blogspot.fr/2009/07/composing-and-updating-custom-eclipse.html?
If so, then it's great. I have currently made appropriate changes to my
build to do what is described in the blog post. But since it leads to lots
of configuration in my product's pom.xml, as well as duplications of
information (duplicating what's in the target platform for the root
features repositories, for instance), I have currently only done that for 1
feature, my own plugin's feature. Far from ideal, then, because lots (if
not all) of the other features included ( Eclipse default features, Eclipse
colortheme, EGit, m2e, etc., etc. ) could use the same treatment.
Cheers,
--
Laurent
Post by S***@de.rhenus.com
Hi Laurent,
AFAIK you want the feature what is hopefully delivered with the next
Tycho release, install root level features into product install.
See https://bugs.eclipse.org/bugs/show_bug.cgi?id=361722.
Best regards, Lars
Post by Laurent PETIT
Hi Jeff,
Post by S***@de.rhenus.com
Laurent,
is it still relevant ? I thought you've fixed it ?
Actually, I have since thursday been able to do a lot of trials and
errors, thanks to the links, thanks to you ...
I haven't had the time to inform you, but I haven't been able to make
the "intermediate product feature" solution work.
- I have created a ccw.product.feature feature, and now my ccw product
includes only this feature in ccw.product
- I have a new tycho module for ccw.product.feature, and it basically
declares all the features which were included directly in the product (Rcp,
Application, JDT, CCW, EclipsecolorTheme, EGit, ...)
The Tycho builds a product, but I'm still unable to update eg CCW via
the update site.
You were talking about a possible remaining issue with "root feature(s)"
with this solution, I didn't at the time understand what you meant, maybe
it's the missing piece ... ?
Post by S***@de.rhenus.com
Jeff
On Thu, Jan 16, 2014 at 10:49 PM, Laurent PETIT <
Post by Laurent PETIT
Hi Paul,
So thanks to you and the link, I've been able to fix my problem. I had
to remove the ccw feature definition from the product features list, and
instead add a requires.x.name to my product's ccw.p2.inf file.
And the final step is to manually invoke the Director to install
ccw.feature.feature.group to the product after the fact.
This is why I'm coming back to you. Since I've removed ccw.feature
from the product features list, I don't find feature artifacts in my
product's target/repository repository anymore. Before that, it was easy to
point the Director to this directory.
So Ive pointed instead the directory to a relative path like
../ccw.updatesite/target/repository.
And it is working for ccw.feature, great !
BUT
I'd also like to make other features updatable independently by the
user: egit, eclipse-colorthemes for instance.
And then starts the redundancy : I have already declared where to find
these feature in my ccw.target.e47 target definition, but I don't know how
to reuse this.
Instead, I find myself repeating tycho-eclipserun-plugin calls, an for
each call, pasting the location of external p2 repositories ...
There must be a better way with tycho, right ? I'm sure I'm not using
it to its full potential ....
thanks in advance for any guidance,
--
Laurent
Post by Laurent PETIT
Thank you both, Paul and Sandra, I will take a look at these links
and try things ASAP.
On Thu, Jan 16, 2014 at 8:48 AM, Laurent PETIT <
Post by Laurent PETIT
There's something not working yet: once the product is installed,
users are unable to update the counterclockwise plugin via the
counterclockwise update site, meaning that they need to download and
install a new version of the Product everytime they want to upgrade ..
See
http://aniefer.blogspot.ca/2009/07/composing-and-updating-custom-eclipse.htmlwhich has a section on upgrading components without upgrading the entire
product.
If I'm reading it correctly, you need your product p2.inf to open up
the ranges on the features the product include.
Later,
Paul
--
Paul Webster
Hi floor. Make me a sammich! - GIR
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
--
Jeff MAURY
"Legacy code" often differs from its suggested alternative by actually
working and scaling.
- Bjarne Stroustrup
http://www.jeffmaury.com
http://riadiscuss.jeffmaury.com
http://www.twitter.com/jeffmaury
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
Laurent PETIT
2014-01-23 18:55:24 UTC
Permalink
Post by S***@de.rhenus.com
Hi Laurent,
I'm not sure how the Tycho committer are planning to solve this. I
personally hope for a Tycho flag which tells Tycho to install all features
as root level features. I think that is also what EPP would need, but also
I'm not sure here.
Best regards, Lars
What you describe sounds great :)
Post by S***@de.rhenus.com
Thanks for the information, Lars !
Do I understand right that when the bug 361722 is solved in Tycho, this
http://aniefer.blogspot.fr/2009/07/composing-and-updating-custom-eclipse.html?
If so, then it's great. I have currently made appropriate changes to my
build to do what is described in the blog post. But since it leads to lots
of configuration in my product's pom.xml, as well as duplications of
information (duplicating what's in the target platform for the root
features repositories, for instance), I have currently only done that for 1
feature, my own plugin's feature. Far from ideal, then, because lots (if
not all) of the other features included ( Eclipse default features, Eclipse
colortheme, EGit, m2e, etc., etc. ) could use the same treatment.
Cheers,
--
Laurent
Hi Laurent,
AFAIK you want the feature what is hopefully delivered with the next Tycho
release, install root level features into product install.
See https://bugs.eclipse.org/bugs/show_bug.cgi?id=361722.
Best regards, Lars
Hi Jeff,
Laurent,
is it still relevant ? I thought you've fixed it ?
Actually, I have since thursday been able to do a lot of trials and
errors, thanks to the links, thanks to you ...
I haven't had the time to inform you, but I haven't been able to make the
"intermediate product feature" solution work.
- I have created a ccw.product.feature feature, and now my ccw product
includes only this feature in ccw.product
- I have a new tycho module for ccw.product.feature, and it basically
declares all the features which were included directly in the product (Rcp,
Application, JDT, CCW, EclipsecolorTheme, EGit, ...)
The Tycho builds a product, but I'm still unable to update eg CCW via the
update site.
You were talking about a possible remaining issue with "root feature(s)"
with this solution, I didn't at the time understand what you meant, maybe
it's the missing piece ... ?
Jeff
Hi Paul,
So thanks to you and the link, I've been able to fix my problem. I had to
remove the ccw feature definition from the product features list, and
instead add a requires.x.name to my product's ccw.p2.inf file.
<
Lars Vogel
2014-01-23 21:17:49 UTC
Permalink
Can you also comment on Bug
https://bugs.eclipse.org/bugs/show_bug.cgi?id=361722 that you also like to
have that functionality for your Eclipse IDE incarnation? I think it is
important to indicate that in the Bugreports directly, so that it is not
lost in the flow of information.

Best regards, Lars
Post by S***@de.rhenus.com
Hi Laurent,
Post by Lars Vogel
I'm not sure how the Tycho committer are planning to solve this. I
personally hope for a Tycho flag which tells Tycho to install all features
as root level features. I think that is also what EPP would need, but also
I'm not sure here.
Best regards, Lars
What you describe sounds great :)
Post by Lars Vogel
Thanks for the information, Lars !
Do I understand right that when the bug 361722 is solved in Tycho, this
http://aniefer.blogspot.fr/2009/07/composing-and-updating-custom-eclipse.html?
If so, then it's great. I have currently made appropriate changes to my
build to do what is described in the blog post. But since it leads to lots
of configuration in my product's pom.xml, as well as duplications of
information (duplicating what's in the target platform for the root
features repositories, for instance), I have currently only done that for 1
feature, my own plugin's feature. Far from ideal, then, because lots (if
not all) of the other features included ( Eclipse default features, Eclipse
colortheme, EGit, m2e, etc., etc. ) could use the same treatment.
Cheers,
--
Laurent
Hi Laurent,
AFAIK you want the feature what is hopefully delivered with the next
Tycho release, install root level features into product install.
See https://bugs.eclipse.org/bugs/show_bug.cgi?id=361722.
Best regards, Lars
Hi Jeff,
Laurent,
is it still relevant ? I thought you've fixed it ?
Actually, I have since thursday been able to do a lot of trials and
errors, thanks to the links, thanks to you ...
I haven't had the time to inform you, but I haven't been able to make the
"intermediate product feature" solution work.
- I have created a ccw.product.feature feature, and now my ccw product
includes only this feature in ccw.product
- I have a new tycho module for ccw.product.feature, and it basically
declares all the features which were included directly in the product (Rcp,
Application, JDT, CCW, EclipsecolorTheme, EGit, ...)
The Tycho builds a product, but I'm still unable to update eg CCW via the
update site.
You were talking about a possible remaining issue with "root feature(s)"
with this solution, I didn't at the time understand what you meant, maybe
it's the missing piece ... ?
Jeff
Hi Paul,
So thanks to you and the link, I've been able to fix my problem. I had to
remove the ccw feature definition from the product features list, and
instead add a requires.x.name to my product's ccw.p2.inf file.
<
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
Laurent PETIT
2014-01-23 21:22:11 UTC
Permalink
done
Post by Lars Vogel
Can you also comment on Bug
https://bugs.eclipse.org/bugs/show_bug.cgi?id=361722 that you also like
to have that functionality for your Eclipse IDE incarnation? I think it is
important to indicate that in the Bugreports directly, so that it is not
lost in the flow of information.
Best regards, Lars
Post by S***@de.rhenus.com
Hi Laurent,
Post by Lars Vogel
I'm not sure how the Tycho committer are planning to solve this. I
personally hope for a Tycho flag which tells Tycho to install all features
as root level features. I think that is also what EPP would need, but also
I'm not sure here.
Best regards, Lars
What you describe sounds great :)
Post by Lars Vogel
Thanks for the information, Lars !
Do I understand right that when the bug 361722 is solved in Tycho, this
http://aniefer.blogspot.fr/2009/07/composing-and-updating-custom-eclipse.html?
If so, then it's great. I have currently made appropriate changes to my
build to do what is described in the blog post. But since it leads to lots
of configuration in my product's pom.xml, as well as duplications of
information (duplicating what's in the target platform for the root
features repositories, for instance), I have currently only done that for 1
feature, my own plugin's feature. Far from ideal, then, because lots (if
not all) of the other features included ( Eclipse default features, Eclipse
colortheme, EGit, m2e, etc., etc. ) could use the same treatment.
Cheers,
--
Laurent
Hi Laurent,
AFAIK you want the feature what is hopefully delivered with the next
Tycho release, install root level features into product install.
See https://bugs.eclipse.org/bugs/show_bug.cgi?id=361722.
Best regards, Lars
Hi Jeff,
Laurent,
is it still relevant ? I thought you've fixed it ?
Actually, I have since thursday been able to do a lot of trials and
errors, thanks to the links, thanks to you ...
I haven't had the time to inform you, but I haven't been able to make
the "intermediate product feature" solution work.
- I have created a ccw.product.feature feature, and now my ccw product
includes only this feature in ccw.product
- I have a new tycho module for ccw.product.feature, and it basically
declares all the features which were included directly in the product (Rcp,
Application, JDT, CCW, EclipsecolorTheme, EGit, ...)
The Tycho builds a product, but I'm still unable to update eg CCW via
the update site.
You were talking about a possible remaining issue with "root feature(s)"
with this solution, I didn't at the time understand what you meant, maybe
it's the missing piece ... ?
Jeff
Hi Paul,
So thanks to you and the link, I've been able to fix my problem. I had
to remove the ccw feature definition from the product features list, and
instead add a requires.x.name to my product's ccw.p2.inf file.
<
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
Paul Webster
2014-01-29 16:30:31 UTC
Permalink
Hi Laurent,
Post by Laurent PETIT
Hi Paul,
So thanks to you and the link, I've been able to fix my problem. I had to
remove the ccw feature definition from the product features list, and
instead add a requires.x.name to my product's ccw.p2.inf file.
And the final step is to manually invoke the Director to install
ccw.feature.feature.group to the product after the fact.
This is why I'm coming back to you. Since I've removed ccw.feature from
the product features list, I don't find feature artifacts in my product's
target/repository repository anymore. Before that, it was easy to point the
Director to this directory.
So Ive pointed instead the directory to a relative path like
../ccw.updatesite/target/repository.
I think others have answered this already, but you don't need to remove
your ccw feature from your product to update the require range using the
ccw.p2.inf. The p2.inf will override the defaults generated by the product
require. That will also still allow it to show up in your build p2 repo.


It's the same for any other feature you'd like to allow independent
updating in your product. You need to find it's "inclusion" point (either
in your .product file, or in a feature) and use the p2.inf to broaden the
requirement range.

Later,
PW
--
Paul Webster
Hi floor. Make me a sammich! - GIR
Laurent PETIT
2014-01-30 21:42:57 UTC
Permalink
Hello Paul,
Post by S***@de.rhenus.com
Hi Laurent,
Post by Laurent PETIT
Hi Paul,
So thanks to you and the link, I've been able to fix my problem. I had to
remove the ccw feature definition from the product features list, and
instead add a requires.x.name to my product's ccw.p2.inf file.
And the final step is to manually invoke the Director to install
ccw.feature.feature.group to the product after the fact.
This is why I'm coming back to you. Since I've removed ccw.feature from
the product features list, I don't find feature artifacts in my product's
target/repository repository anymore. Before that, it was easy to point the
Director to this directory.
So Ive pointed instead the directory to a relative path like
../ccw.updatesite/target/repository.
I think others have answered this already, but you don't need to remove
your ccw feature from your product to update the require range using the
ccw.p2.inf. The p2.inf will override the defaults generated by the product
require. That will also still allow it to show up in your build p2 repo.
Thanks for the information. I wasn't really aware of that. And doing
"experiment tests" takes so much time that I hadn't discovered that by
myself.
Post by S***@de.rhenus.com
It's the same for any other feature you'd like to allow independent
updating in your product. You need to find it's "inclusion" point (either
in your .product file, or in a feature) and use the p2.inf to broaden the
requirement range.
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 ?

Also, I have been unable to understand by myself / find an explanation
somewhere about the "namespace" part of the p2.inf example here :
http://aniefer.blogspot.ca/2009/07/composing-and-updating-custom-eclipse.html

requires.1.namespace = org.eclipse.equinox.p2.iurequires.1.name =
org.eclipse.cvs.feature.group
requires.1.range = [1.1.100, 1.2.0)

- Where does the namespace's value come from? What is it used for? Where
can I find it for the several features I would like to broaden ?

Additional question:

- What if I want to use an open upper bound for the features ? Do I need to
use some very large value such as defining [1.1.100, 9999.0.0.0), or is
there a cleaner way to achieve the goal?

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?

Thanks in advance for your answers,
--
Laurent
Post by S***@de.rhenus.com
Later,
PW
--
Paul Webster
Hi floor. Make me a sammich! - GIR
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
Mikhail Kalkov
2014-01-31 15:02:03 UTC
Permalink
Hi Laurent,

With "inclusion points", Paul must have meant places where you include a
feature into the end product. Naturally, this can be a product file, a
p2.inf or a parent feature's feature.xml

As for the p2 IU namespaces, afaik all features belong to the
"org.eclipse.equinox.p2.iu" namespace. Basically, in p2 world everything is
called an Installable Unit. Such a unit may be a feature, a plugin, a
fragment etc. All IUs have to be named and in order to avoid collisions
between similarly named features and plugins, namespaces were introduced.

I am not sure there is a good reference for namespaces, but you can take
any content.{jar|xml} and look inside it. If you do that, be ware that
features are usually composed of two IUs. The first one (*.feature.group)
includes a list of dependencies, and the second one includes a jar file.
You need the ones whose name ends with ".feature.group".

As for p2 version ranges, see slide 15 of this presentation:
http://www.slideshare.net/PascalRapicault/dos-and-do-nots-about-p2

Kind regards,
Mikhail Kalkov
Post by Laurent PETIT
Hello Paul,
Hi Laurent,
Post by Paul Webster
Post by Laurent PETIT
Hi Paul,
So thanks to you and the link, I've been able to fix my problem. I had
to remove the ccw feature definition from the product features list, and
instead add a requires.x.name to my product's ccw.p2.inf file.
And the final step is to manually invoke the Director to install
ccw.feature.feature.group to the product after the fact.
This is why I'm coming back to you. Since I've removed ccw.feature from
the product features list, I don't find feature artifacts in my product's
target/repository repository anymore. Before that, it was easy to point the
Director to this directory.
So Ive pointed instead the directory to a relative path like
../ccw.updatesite/target/repository.
I think others have answered this already, but you don't need to remove
your ccw feature from your product to update the require range using the
ccw.p2.inf. The p2.inf will override the defaults generated by the product
require. That will also still allow it to show up in your build p2 repo.
Thanks for the information. I wasn't really aware of that. And doing
"experiment tests" takes so much time that I hadn't discovered that by
myself.
Post by Paul Webster
It's the same for any other feature you'd like to allow independent
updating in your product. You need to find it's "inclusion" point (either
in your .product file, or in a feature) and use the p2.inf to broaden the
requirement range.
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 ?
Also, I have been unable to understand by myself / find an explanation
http://aniefer.blogspot.ca/2009/07/composing-and-updating-custom-eclipse.html
requires.1.namespace = org.eclipse.equinox.p2.iurequires.1.name = org.eclipse.cvs.feature.group
requires.1.range = [1.1.100, 1.2.0)
- Where does the namespace's value come from? What is it used for? Where
can I find it for the several features I would like to broaden ?
- What if I want to use an open upper bound for the features ? Do I need
to use some very large value such as defining [1.1.100, 9999.0.0.0), or is
there a cleaner way to achieve the goal?
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?
Thanks in advance for your answers,
--
Laurent
Post by Paul Webster
Later,
PW
--
Paul Webster
Hi floor. Make me a sammich! - GIR
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
Paul Webster
2014-02-04 15:20:22 UTC
Permalink
Hi Laurent,
Post by Laurent PETIT
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.
Post by Laurent PETIT
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.

PW
--
Paul Webster
Hi floor. Make me a sammich! - GIR
Laurent PETIT
2014-02-04 15:24:39 UTC
Permalink
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 ?
Post by S***@de.rhenus.com
Hi Laurent,
Post by Laurent PETIT
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.
Post by Laurent PETIT
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.
PW
--
Paul Webster
Hi floor. Make me a sammich! - GIR
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
Laurent PETIT
2014-03-06 22:51:11 UTC
Permalink
Hello,

Thanks to the new Tycho 0.20.0-SNAPSHOT installRoot feature, I was able to
cleanup my build, and get the root features.

But I'm still not totally there :

I want to simulate updates.
So I create a product based on Kepler sr1.
I open it, then trigger "check for updates", select it, let the update
happen, and the restart occur.
The restart takes a looooooooong time (several minutes, so long that on my
first attempts I didn't even wait, I just thought the Eclipse process was
down), but finally I've got a working environment
And then every new start keeps taking a looooooooooong time (and also I
think I don't see my product image and progress bar anymore, but maybe I'm
wrong since I don't have the patience to keep a constant eye on what's
happening in the background).

What may I be doing wrong ?

FWIW, here's the current product definition file:
https://github.com/laurentpetit/ccw/blob/master/ccw.product/ccw.product#L253

Thanks if you can help me,
--
Laurent Petit
Post by Laurent PETIT
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 ?
Post by S***@de.rhenus.com
Hi Laurent,
Post by Laurent PETIT
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.
Post by Laurent PETIT
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.
PW
--
Paul Webster
Hi floor. Make me a sammich! - GIR
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
Jeff MAURY
2014-03-06 22:55:26 UTC
Permalink
Can you tell us which features did you update ?

Jeff
Post by Laurent PETIT
Hello,
Thanks to the new Tycho 0.20.0-SNAPSHOT installRoot feature, I was able to
cleanup my build, and get the root features.
I want to simulate updates.
So I create a product based on Kepler sr1.
I open it, then trigger "check for updates", select it, let the update
happen, and the restart occur.
The restart takes a looooooooong time (several minutes, so long that on my
first attempts I didn't even wait, I just thought the Eclipse process was
down), but finally I've got a working environment
And then every new start keeps taking a looooooooooong time (and also I
think I don't see my product image and progress bar anymore, but maybe I'm
wrong since I don't have the patience to keep a constant eye on what's
happening in the background).
What may I be doing wrong ?
https://github.com/laurentpetit/ccw/blob/master/ccw.product/ccw.product#L253
Thanks if you can help me,
--
Laurent Petit
Hello Paul, and Mikhail,
Post by Laurent PETIT
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 ?
Post by S***@de.rhenus.com
Hi Laurent,
Post by Laurent PETIT
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.
Post by Laurent PETIT
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.
PW
--
Paul Webster
Hi floor. Make me a sammich! - GIR
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
--
Jeff MAURY


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

http://www.jeffmaury.com
http://riadiscuss.jeffmaury.com
http://www.twitter.com/jeffmaury
Laurent PETIT
2014-03-06 23:03:00 UTC
Permalink
The whole thing: I accepted everything that was proposed, consisting mainly
of Eclipse Kepler repository contents updates.

Here's the .log file after the IDE finally pops up to live:
https://gist.github.com/laurentpetit/9401617
Post by Jeff MAURY
Can you tell us which features did you update ?
Jeff
Post by Laurent PETIT
Hello,
Thanks to the new Tycho 0.20.0-SNAPSHOT installRoot feature, I was able
to cleanup my build, and get the root features.
I want to simulate updates.
So I create a product based on Kepler sr1.
I open it, then trigger "check for updates", select it, let the update
happen, and the restart occur.
The restart takes a looooooooong time (several minutes, so long that on
my first attempts I didn't even wait, I just thought the Eclipse process
was down), but finally I've got a working environment
And then every new start keeps taking a looooooooooong time (and also I
think I don't see my product image and progress bar anymore, but maybe I'm
wrong since I don't have the patience to keep a constant eye on what's
happening in the background).
What may I be doing wrong ?
https://github.com/laurentpetit/ccw/blob/master/ccw.product/ccw.product#L253
Thanks if you can help me,
--
Laurent Petit
Hello Paul, and Mikhail,
Post by Laurent PETIT
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 ?
Post by S***@de.rhenus.com
Hi Laurent,
Post by Laurent PETIT
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.
Post by Laurent PETIT
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.
PW
--
Paul Webster
Hi floor. Make me a sammich! - GIR
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
--
Jeff MAURY
"Legacy code" often differs from its suggested alternative by actually
working and scaling.
- Bjarne Stroustrup
http://www.jeffmaury.com
http://riadiscuss.jeffmaury.com
http://www.twitter.com/jeffmaury
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
Jeff MAURY
2014-03-06 23:12:24 UTC
Permalink
Can you tell is us if you still have your product running or has it been
replaced by one from Eclipse ?

Jeff
Post by Laurent PETIT
The whole thing: I accepted everything that was proposed, consisting
mainly of Eclipse Kepler repository contents updates.
https://gist.github.com/laurentpetit/9401617
Can you tell us which features did you update ?
Post by Jeff MAURY
Jeff
Post by Laurent PETIT
Hello,
Thanks to the new Tycho 0.20.0-SNAPSHOT installRoot feature, I was able
to cleanup my build, and get the root features.
I want to simulate updates.
So I create a product based on Kepler sr1.
I open it, then trigger "check for updates", select it, let the update
happen, and the restart occur.
The restart takes a looooooooong time (several minutes, so long that on
my first attempts I didn't even wait, I just thought the Eclipse process
was down), but finally I've got a working environment
And then every new start keeps taking a looooooooooong time (and also I
think I don't see my product image and progress bar anymore, but maybe I'm
wrong since I don't have the patience to keep a constant eye on what's
happening in the background).
What may I be doing wrong ?
https://github.com/laurentpetit/ccw/blob/master/ccw.product/ccw.product#L253
Thanks if you can help me,
--
Laurent Petit
Hello Paul, and Mikhail,
Post by Laurent PETIT
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 ?
Post by S***@de.rhenus.com
Hi Laurent,
On Thu, Jan 30, 2014 at 4:42 PM, Laurent PETIT <
Post by Laurent PETIT
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.
Post by Laurent PETIT
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.
PW
--
Paul Webster
Hi floor. Make me a sammich! - GIR
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
--
Jeff MAURY
"Legacy code" often differs from its suggested alternative by actually
working and scaling.
- Bjarne Stroustrup
http://www.jeffmaury.com
http://riadiscuss.jeffmaury.com
http://www.twitter.com/jeffmaury
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
--
Jeff MAURY


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

http://www.jeffmaury.com
http://riadiscuss.jeffmaury.com
http://www.twitter.com/jeffmaury
Laurent PETIT
2014-03-06 23:35:53 UTC
Permalink
Good question.

I still launch from my Counterclockwise.exe, when I go in About I see
branding from my product. How could I check more than that?
Post by Jeff MAURY
Can you tell is us if you still have your product running or has it been
replaced by one from Eclipse ?
Jeff
Post by Laurent PETIT
The whole thing: I accepted everything that was proposed, consisting
mainly of Eclipse Kepler repository contents updates.
https://gist.github.com/laurentpetit/9401617
Can you tell us which features did you update ?
Post by Jeff MAURY
Jeff
Post by Laurent PETIT
Hello,
Thanks to the new Tycho 0.20.0-SNAPSHOT installRoot feature, I was able
to cleanup my build, and get the root features.
I want to simulate updates.
So I create a product based on Kepler sr1.
I open it, then trigger "check for updates", select it, let the update
happen, and the restart occur.
The restart takes a looooooooong time (several minutes, so long that on
my first attempts I didn't even wait, I just thought the Eclipse process
was down), but finally I've got a working environment
And then every new start keeps taking a looooooooooong time (and also I
think I don't see my product image and progress bar anymore, but maybe I'm
wrong since I don't have the patience to keep a constant eye on what's
happening in the background).
What may I be doing wrong ?
https://github.com/laurentpetit/ccw/blob/master/ccw.product/ccw.product#L253
Thanks if you can help me,
--
Laurent Petit
Hello Paul, and Mikhail,
Post by Laurent PETIT
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 ?
Post by S***@de.rhenus.com
Hi Laurent,
On Thu, Jan 30, 2014 at 4:42 PM, Laurent PETIT <
Post by Laurent PETIT
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.
Post by Laurent PETIT
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.
PW
--
Paul Webster
Hi floor. Make me a sammich! - GIR
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
--
Jeff MAURY
"Legacy code" often differs from its suggested alternative by actually
working and scaling.
- Bjarne Stroustrup
http://www.jeffmaury.com
http://riadiscuss.jeffmaury.com
http://www.twitter.com/jeffmaury
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
--
Jeff MAURY
"Legacy code" often differs from its suggested alternative by actually
working and scaling.
- Bjarne Stroustrup
http://www.jeffmaury.com
http://riadiscuss.jeffmaury.com
http://www.twitter.com/jeffmaury
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
Jeff MAURY
2014-03-07 14:24:20 UTC
Permalink
So what is your problem ? Is is the long time to start ? Seeems you've got
a bunch of timeouts expired. I would suggest updating items per items to
see where the problem is from

Jeff
Post by Laurent PETIT
Good question.
I still launch from my Counterclockwise.exe, when I go in About I see
branding from my product. How could I check more than that?
Can you tell is us if you still have your product running or has it been
Post by Jeff MAURY
replaced by one from Eclipse ?
Jeff
Post by Laurent PETIT
The whole thing: I accepted everything that was proposed, consisting
mainly of Eclipse Kepler repository contents updates.
https://gist.github.com/laurentpetit/9401617
Can you tell us which features did you update ?
Post by Jeff MAURY
Jeff
Post by Laurent PETIT
Hello,
Thanks to the new Tycho 0.20.0-SNAPSHOT installRoot feature, I was
able to cleanup my build, and get the root features.
I want to simulate updates.
So I create a product based on Kepler sr1.
I open it, then trigger "check for updates", select it, let the update
happen, and the restart occur.
The restart takes a looooooooong time (several minutes, so long that
on my first attempts I didn't even wait, I just thought the Eclipse process
was down), but finally I've got a working environment
And then every new start keeps taking a looooooooooong time (and also
I think I don't see my product image and progress bar anymore, but maybe
I'm wrong since I don't have the patience to keep a constant eye on what's
happening in the background).
What may I be doing wrong ?
https://github.com/laurentpetit/ccw/blob/master/ccw.product/ccw.product#L253
Thanks if you can help me,
--
Laurent Petit
Hello Paul, and Mikhail,
Post by Laurent PETIT
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 ?
Post by S***@de.rhenus.com
Hi Laurent,
On Thu, Jan 30, 2014 at 4:42 PM, Laurent PETIT <
Post by Laurent PETIT
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.
Post by Laurent PETIT
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.
PW
--
Paul Webster
Hi floor. Make me a sammich! - GIR
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
--
Jeff MAURY
"Legacy code" often differs from its suggested alternative by actually
working and scaling.
- Bjarne Stroustrup
http://www.jeffmaury.com
http://riadiscuss.jeffmaury.com
http://www.twitter.com/jeffmaury
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
--
Jeff MAURY
"Legacy code" often differs from its suggested alternative by actually
working and scaling.
- Bjarne Stroustrup
http://www.jeffmaury.com
http://riadiscuss.jeffmaury.com
http://www.twitter.com/jeffmaury
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
--
Jeff MAURY


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

http://www.jeffmaury.com
http://riadiscuss.jeffmaury.com
http://www.twitter.com/jeffmaury
Laurent PETIT
2014-03-11 13:28:45 UTC
Permalink
Hello,

I have tried updating item per item. As long as I don't touch an item that
will trigger the update of core Eclipse stuff, everything works fine
(updating the JDT alone works fine, updating EGit alone works fine, etc.).

I acknowledge that it is not easy for you to help me based on the CCW
codebase, so I created a smaller example, based on ccw, but with almost all
ccw related stuff removed.

It's here: https://github.com/laurentpetit/my-ide

To compile, just issue "mvn clean verify" in the root folder.

It is a really tiny codebase, and it builds really fast compared to CCW, so
hopefully you'll be able to follow along with me by compiling it locally.

I've called this repo "my-ide", and its purpose is to illustrate a small
custom IDE based on Eclipse IDE, and using Tycho.

It builds correctly, starts correctly, and provides already some errors
when triggering "Check for Updates" and then accepting to update all that
is proposed.

Locally I see this message:
!MESSAGE Missing required capability Require-Capability: osgi.ee;
filter="(|(&(osgi.ee=JavaSE)(version=1.4))(&(osgi.ee
=CDC/Foundation)(version=1.0))(&(osgi.ee=JavaSE)(version=1.3)))".


So I have 2 questions:

1/
- can you help me understand and go past this message?

2/
Even before this message, when the product first starts, there are tons of
"warnings" such as :

!ENTRY org.eclipse.update.configurator 4 0 2014-03-11 14:09:19.232
!MESSAGE Could not install bundle
plugins/com.ibm.icu_50.1.1.v201304230130.jar Bundle "com.ibm.icu" version
"50.1.1.v201304230130" has already been installed from:
reference:file:plugins/com.ibm.icu_50.1.1.v201304230130.jar
.....
!ENTRY org.eclipse.update.configurator 4 0 2014-03-11 14:01:34.235
!MESSAGE Could not install bundle
plugins/org.w3c.dom.svg_1.1.0.v201011041433.jar Bundle "org.w3c.dom.svg"
version "1.1.0.v201011041433" has already been installed from:
reference:file:plugins/org.w3c.dom.svg_1.1.0.v201011041433.jar

Can I get rid of those? And how?

Thanks in advance,
--
Laurent
Post by Jeff MAURY
So what is your problem ? Is is the long time to start ? Seeems you've got
a bunch of timeouts expired. I would suggest updating items per items to
see where the problem is from
Jeff
Post by Laurent PETIT
Good question.
I still launch from my Counterclockwise.exe, when I go in About I see
branding from my product. How could I check more than that?
Can you tell is us if you still have your product running or has it been
Post by Jeff MAURY
replaced by one from Eclipse ?
Jeff
Post by Laurent PETIT
The whole thing: I accepted everything that was proposed, consisting
mainly of Eclipse Kepler repository contents updates.
https://gist.github.com/laurentpetit/9401617
Can you tell us which features did you update ?
Jeff
On Thu, Mar 6, 2014 at 11:51 PM, Laurent PETIT <
Post by Laurent PETIT
Hello,
Thanks to the new Tycho 0.20.0-SNAPSHOT installRoot feature, I was
able to cleanup my build, and get the root features.
I want to simulate updates.
So I create a product based on Kepler sr1.
I open it, then trigger "check for updates", select it, let the
update happen, and the restart occur.
The restart takes a looooooooong time (several minutes, so long that
on my first attempts I didn't even wait, I just thought the Eclipse process
was down), but finally I've got a working environment
And then every new start keeps taking a looooooooooong time (and also
I think I don't see my product image and progress bar anymore, but maybe
I'm wrong since I don't have the patience to keep a constant eye on what's
happening in the background).
What may I be doing wrong ?
https://github.com/laurentpetit/ccw/blob/master/ccw.product/ccw.product#L253
Thanks if you can help me,
--
Laurent Petit
Hello Paul, and Mikhail,
Post by Laurent PETIT
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 ?
Post by S***@de.rhenus.com
Hi Laurent,
On Thu, Jan 30, 2014 at 4:42 PM, Laurent PETIT <
Post by Laurent PETIT
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.
Post by Laurent PETIT
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.
PW
--
Paul Webster
Hi floor. Make me a sammich! - GIR
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
--
Jeff MAURY
"Legacy code" often differs from its suggested alternative by actually
working and scaling.
- Bjarne Stroustrup
http://www.jeffmaury.com
http://riadiscuss.jeffmaury.com
http://www.twitter.com/jeffmaury
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
--
Jeff MAURY
"Legacy code" often differs from its suggested alternative by actually
working and scaling.
- Bjarne Stroustrup
http://www.jeffmaury.com
http://riadiscuss.jeffmaury.com
http://www.twitter.com/jeffmaury
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
--
Jeff MAURY
"Legacy code" often differs from its suggested alternative by actually
working and scaling.
- Bjarne Stroustrup
http://www.jeffmaury.com
http://riadiscuss.jeffmaury.com
http://www.twitter.com/jeffmaury
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
Jeff MAURY
2014-03-11 13:34:55 UTC
Permalink
For the first message, one of your bundle is looking for the capability
JavaSE 1.3 or JavaSE 1.4 or CDC/Foundation 1.0. Old so not satisfied.

The error messaes are generated the first time you launch a product build
with Tycho. I have the sames in my product, you can ignore them.
I'm trying to build your small IDE.

Jeff
Post by Laurent PETIT
Hello,
I have tried updating item per item. As long as I don't touch an item that
will trigger the update of core Eclipse stuff, everything works fine
(updating the JDT alone works fine, updating EGit alone works fine, etc.).
I acknowledge that it is not easy for you to help me based on the CCW
codebase, so I created a smaller example, based on ccw, but with almost all
ccw related stuff removed.
It's here: https://github.com/laurentpetit/my-ide
To compile, just issue "mvn clean verify" in the root folder.
It is a really tiny codebase, and it builds really fast compared to CCW,
so hopefully you'll be able to follow along with me by compiling it locally.
I've called this repo "my-ide", and its purpose is to illustrate a small
custom IDE based on Eclipse IDE, and using Tycho.
It builds correctly, starts correctly, and provides already some errors
when triggering "Check for Updates" and then accepting to update all that
is proposed.
!MESSAGE Missing required capability Require-Capability: osgi.ee;
filter="(|(&(osgi.ee=JavaSE)(version=1.4))(&(osgi.ee
=CDC/Foundation)(version=1.0))(&(osgi.ee=JavaSE)(version=1.3)))".
1/
- can you help me understand and go past this message?
2/
Even before this message, when the product first starts, there are tons of
!ENTRY org.eclipse.update.configurator 4 0 2014-03-11 14:09:19.232
!MESSAGE Could not install bundle
plugins/com.ibm.icu_50.1.1.v201304230130.jar Bundle "com.ibm.icu" version
reference:file:plugins/com.ibm.icu_50.1.1.v201304230130.jar
.....
!ENTRY org.eclipse.update.configurator 4 0 2014-03-11 14:01:34.235
!MESSAGE Could not install bundle
plugins/org.w3c.dom.svg_1.1.0.v201011041433.jar Bundle "org.w3c.dom.svg"
reference:file:plugins/org.w3c.dom.svg_1.1.0.v201011041433.jar
Can I get rid of those? And how?
Thanks in advance,
--
Laurent
So what is your problem ? Is is the long time to start ? Seeems you've got
Post by Jeff MAURY
a bunch of timeouts expired. I would suggest updating items per items to
see where the problem is from
Jeff
Post by Laurent PETIT
Good question.
I still launch from my Counterclockwise.exe, when I go in About I see
branding from my product. How could I check more than that?
Can you tell is us if you still have your product running or has it been
Post by Jeff MAURY
replaced by one from Eclipse ?
Jeff
Post by Laurent PETIT
The whole thing: I accepted everything that was proposed, consisting
mainly of Eclipse Kepler repository contents updates.
https://gist.github.com/laurentpetit/9401617
Can you tell us which features did you update ?
Jeff
On Thu, Mar 6, 2014 at 11:51 PM, Laurent PETIT <
Post by Laurent PETIT
Hello,
Thanks to the new Tycho 0.20.0-SNAPSHOT installRoot feature, I was
able to cleanup my build, and get the root features.
I want to simulate updates.
So I create a product based on Kepler sr1.
I open it, then trigger "check for updates", select it, let the
update happen, and the restart occur.
The restart takes a looooooooong time (several minutes, so long that
on my first attempts I didn't even wait, I just thought the Eclipse process
was down), but finally I've got a working environment
And then every new start keeps taking a looooooooooong time (and
also I think I don't see my product image and progress bar anymore, but
maybe I'm wrong since I don't have the patience to keep a constant eye on
what's happening in the background).
What may I be doing wrong ?
https://github.com/laurentpetit/ccw/blob/master/ccw.product/ccw.product#L253
Thanks if you can help me,
--
Laurent Petit
Hello Paul, and Mikhail,
Post by Laurent PETIT
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 ?
Post by S***@de.rhenus.com
Hi Laurent,
On Thu, Jan 30, 2014 at 4:42 PM, Laurent PETIT <
Post by Laurent PETIT
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.
Post by Laurent PETIT
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.
PW
--
Paul Webster
Hi floor. Make me a sammich! - GIR
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
--
Jeff MAURY
"Legacy code" often differs from its suggested alternative by
actually working and scaling.
- Bjarne Stroustrup
http://www.jeffmaury.com
http://riadiscuss.jeffmaury.com
http://www.twitter.com/jeffmaury
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
--
Jeff MAURY
"Legacy code" often differs from its suggested alternative by actually
working and scaling.
- Bjarne Stroustrup
http://www.jeffmaury.com
http://riadiscuss.jeffmaury.com
http://www.twitter.com/jeffmaury
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
--
Jeff MAURY
"Legacy code" often differs from its suggested alternative by actually
working and scaling.
- Bjarne Stroustrup
http://www.jeffmaury.com
http://riadiscuss.jeffmaury.com
http://www.twitter.com/jeffmaury
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
--
Jeff MAURY


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

http://www.jeffmaury.com
http://riadiscuss.jeffmaury.com
http://www.twitter.com/jeffmaury
Laurent PETIT
2014-03-11 17:13:11 UTC
Permalink
Hi Jeff,

Thanks for the answer.

I deliberately kept the target platform targetting Kepler SR1 so that I can
then, with the built product, try a full update towards Kepler SR2 => the
target platform has been setup sometimes in late december or early january
and not updated since.

Have you been able to build "my-ide" ?
Post by Jeff MAURY
For the first message, one of your bundle is looking for the capability
JavaSE 1.3 or JavaSE 1.4 or CDC/Foundation 1.0. Old so not satisfied.
The error messaes are generated the first time you launch a product build
with Tycho. I have the sames in my product, you can ignore them.
I'm trying to build your small IDE.
Jeff
Post by Laurent PETIT
Hello,
I have tried updating item per item. As long as I don't touch an item
that will trigger the update of core Eclipse stuff, everything works fine
(updating the JDT alone works fine, updating EGit alone works fine, etc.).
I acknowledge that it is not easy for you to help me based on the CCW
codebase, so I created a smaller example, based on ccw, but with almost all
ccw related stuff removed.
It's here: https://github.com/laurentpetit/my-ide
To compile, just issue "mvn clean verify" in the root folder.
It is a really tiny codebase, and it builds really fast compared to CCW,
so hopefully you'll be able to follow along with me by compiling it locally.
I've called this repo "my-ide", and its purpose is to illustrate a small
custom IDE based on Eclipse IDE, and using Tycho.
It builds correctly, starts correctly, and provides already some errors
when triggering "Check for Updates" and then accepting to update all that
is proposed.
!MESSAGE Missing required capability Require-Capability: osgi.ee;
filter="(|(&(osgi.ee=JavaSE)(version=1.4))(&(osgi.ee
=CDC/Foundation)(version=1.0))(&(osgi.ee=JavaSE)(version=1.3)))".
1/
- can you help me understand and go past this message?
2/
Even before this message, when the product first starts, there are tons
!ENTRY org.eclipse.update.configurator 4 0 2014-03-11 14:09:19.232
!MESSAGE Could not install bundle
plugins/com.ibm.icu_50.1.1.v201304230130.jar Bundle "com.ibm.icu" version
reference:file:plugins/com.ibm.icu_50.1.1.v201304230130.jar
.....
!ENTRY org.eclipse.update.configurator 4 0 2014-03-11 14:01:34.235
!MESSAGE Could not install bundle
plugins/org.w3c.dom.svg_1.1.0.v201011041433.jar Bundle "org.w3c.dom.svg"
reference:file:plugins/org.w3c.dom.svg_1.1.0.v201011041433.jar
Can I get rid of those? And how?
Thanks in advance,
--
Laurent
So what is your problem ? Is is the long time to start ? Seeems you've
got a bunch of timeouts expired. I would suggest updating items per items
to see where the problem is from
Jeff
Post by Laurent PETIT
Good question.
I still launch from my Counterclockwise.exe, when I go in About I see
branding from my product. How could I check more than that?
Can you tell is us if you still have your product running or has it
been replaced by one from Eclipse ?
Jeff
On Fri, Mar 7, 2014 at 12:03 AM, Laurent PETIT <
Post by Laurent PETIT
The whole thing: I accepted everything that was proposed, consisting
mainly of Eclipse Kepler repository contents updates.
https://gist.github.com/laurentpetit/9401617
Can you tell us which features did you update ?
Jeff
On Thu, Mar 6, 2014 at 11:51 PM, Laurent PETIT <
Post by Laurent PETIT
Hello,
Thanks to the new Tycho 0.20.0-SNAPSHOT installRoot feature, I was
able to cleanup my build, and get the root features.
I want to simulate updates.
So I create a product based on Kepler sr1.
I open it, then trigger "check for updates", select it, let the
update happen, and the restart occur.
The restart takes a looooooooong time (several minutes, so long
that on my first attempts I didn't even wait, I just thought the Eclipse
process was down), but finally I've got a working environment
And then every new start keeps taking a looooooooooong time (and
also I think I don't see my product image and progress bar anymore, but
maybe I'm wrong since I don't have the patience to keep a constant eye on
what's happening in the background).
What may I be doing wrong ?
https://github.com/laurentpetit/ccw/blob/master/ccw.product/ccw.product#L253
Thanks if you can help me,
--
Laurent Petit
Hello Paul, and Mikhail,
Post by Laurent PETIT
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 ?
Post by S***@de.rhenus.com
Hi Laurent,
On Thu, Jan 30, 2014 at 4:42 PM, Laurent PETIT <
Post by Laurent PETIT
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.
Post by Laurent PETIT
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.
PW
--
Paul Webster
Hi floor. Make me a sammich! - GIR
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
--
Jeff MAURY
"Legacy code" often differs from its suggested alternative by
actually working and scaling.
- Bjarne Stroustrup
http://www.jeffmaury.com
http://riadiscuss.jeffmaury.com
http://www.twitter.com/jeffmaury
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
--
Jeff MAURY
"Legacy code" often differs from its suggested alternative by actually
working and scaling.
- Bjarne Stroustrup
http://www.jeffmaury.com
http://riadiscuss.jeffmaury.com
http://www.twitter.com/jeffmaury
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
--
Jeff MAURY
"Legacy code" often differs from its suggested alternative by actually
working and scaling.
- Bjarne Stroustrup
http://www.jeffmaury.com
http://riadiscuss.jeffmaury.com
http://www.twitter.com/jeffmaury
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
--
Jeff MAURY
"Legacy code" often differs from its suggested alternative by actually
working and scaling.
- Bjarne Stroustrup
http://www.jeffmaury.com
http://riadiscuss.jeffmaury.com
http://www.twitter.com/jeffmaury
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
Laurent PETIT
2014-03-11 19:35:36 UTC
Permalink
Hi Jeff,

I updated the "my-ide" repository because there was a missing
"my-ide.feature", and I don't want any doubt on what the problem may be.

Still the same message: "bundle is looking for the capability JavaSE 1.3 or
JavaSE 1.4 or CDC/Foundation 1.0. Old so not satisfied"
Post by Laurent PETIT
Hi Jeff,
Thanks for the answer.
I deliberately kept the target platform targetting Kepler SR1 so that I
can then, with the built product, try a full update towards Kepler SR2 =>
the target platform has been setup sometimes in late december or early
january and not updated since.
Have you been able to build "my-ide" ?
For the first message, one of your bundle is looking for the capability
Post by Jeff MAURY
JavaSE 1.3 or JavaSE 1.4 or CDC/Foundation 1.0. Old so not satisfied.
The error messaes are generated the first time you launch a product build
with Tycho. I have the sames in my product, you can ignore them.
I'm trying to build your small IDE.
Jeff
Post by Laurent PETIT
Hello,
I have tried updating item per item. As long as I don't touch an item
that will trigger the update of core Eclipse stuff, everything works fine
(updating the JDT alone works fine, updating EGit alone works fine, etc.).
I acknowledge that it is not easy for you to help me based on the CCW
codebase, so I created a smaller example, based on ccw, but with almost all
ccw related stuff removed.
It's here: https://github.com/laurentpetit/my-ide
To compile, just issue "mvn clean verify" in the root folder.
It is a really tiny codebase, and it builds really fast compared to CCW,
so hopefully you'll be able to follow along with me by compiling it locally.
I've called this repo "my-ide", and its purpose is to illustrate a small
custom IDE based on Eclipse IDE, and using Tycho.
It builds correctly, starts correctly, and provides already some errors
when triggering "Check for Updates" and then accepting to update all that
is proposed.
!MESSAGE Missing required capability Require-Capability: osgi.ee;
filter="(|(&(osgi.ee=JavaSE)(version=1.4))(&(osgi.ee
=CDC/Foundation)(version=1.0))(&(osgi.ee=JavaSE)(version=1.3)))".
1/
- can you help me understand and go past this message?
2/
Even before this message, when the product first starts, there are tons
!ENTRY org.eclipse.update.configurator 4 0 2014-03-11 14:09:19.232
!MESSAGE Could not install bundle
plugins/com.ibm.icu_50.1.1.v201304230130.jar Bundle "com.ibm.icu" version
reference:file:plugins/com.ibm.icu_50.1.1.v201304230130.jar
.....
!ENTRY org.eclipse.update.configurator 4 0 2014-03-11 14:01:34.235
!MESSAGE Could not install bundle
plugins/org.w3c.dom.svg_1.1.0.v201011041433.jar Bundle "org.w3c.dom.svg"
reference:file:plugins/org.w3c.dom.svg_1.1.0.v201011041433.jar
Can I get rid of those? And how?
Thanks in advance,
--
Laurent
So what is your problem ? Is is the long time to start ? Seeems you've
got a bunch of timeouts expired. I would suggest updating items per items
to see where the problem is from
Jeff
Post by Laurent PETIT
Good question.
I still launch from my Counterclockwise.exe, when I go in About I see
branding from my product. How could I check more than that?
Can you tell is us if you still have your product running or has it
been replaced by one from Eclipse ?
Jeff
On Fri, Mar 7, 2014 at 12:03 AM, Laurent PETIT <
Post by Laurent PETIT
The whole thing: I accepted everything that was proposed, consisting
mainly of Eclipse Kepler repository contents updates.
https://gist.github.com/laurentpetit/9401617
Can you tell us which features did you update ?
Jeff
On Thu, Mar 6, 2014 at 11:51 PM, Laurent PETIT <
Post by Laurent PETIT
Hello,
Thanks to the new Tycho 0.20.0-SNAPSHOT installRoot feature, I was
able to cleanup my build, and get the root features.
I want to simulate updates.
So I create a product based on Kepler sr1.
I open it, then trigger "check for updates", select it, let the
update happen, and the restart occur.
The restart takes a looooooooong time (several minutes, so long
that on my first attempts I didn't even wait, I just thought the Eclipse
process was down), but finally I've got a working environment
And then every new start keeps taking a looooooooooong time (and
also I think I don't see my product image and progress bar anymore, but
maybe I'm wrong since I don't have the patience to keep a constant eye on
what's happening in the background).
What may I be doing wrong ?
https://github.com/laurentpetit/ccw/blob/master/ccw.product/ccw.product#L253
Thanks if you can help me,
--
Laurent Petit
Hello Paul, and Mikhail,
Post by Laurent PETIT
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 ?
Post by S***@de.rhenus.com
Hi Laurent,
On Thu, Jan 30, 2014 at 4:42 PM, Laurent PETIT <
Post by Laurent PETIT
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.
Post by Laurent PETIT
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.
PW
--
Paul Webster
Hi floor. Make me a sammich! - GIR
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
--
Jeff MAURY
"Legacy code" often differs from its suggested alternative by
actually working and scaling.
- Bjarne Stroustrup
http://www.jeffmaury.com
http://riadiscuss.jeffmaury.com
http://www.twitter.com/jeffmaury
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
--
Jeff MAURY
"Legacy code" often differs from its suggested alternative by
actually working and scaling.
- Bjarne Stroustrup
http://www.jeffmaury.com
http://riadiscuss.jeffmaury.com
http://www.twitter.com/jeffmaury
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
--
Jeff MAURY
"Legacy code" often differs from its suggested alternative by actually
working and scaling.
- Bjarne Stroustrup
http://www.jeffmaury.com
http://riadiscuss.jeffmaury.com
http://www.twitter.com/jeffmaury
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
--
Jeff MAURY
"Legacy code" often differs from its suggested alternative by actually
working and scaling.
- Bjarne Stroustrup
http://www.jeffmaury.com
http://riadiscuss.jeffmaury.com
http://www.twitter.com/jeffmaury
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
Jeff MAURY
2014-03-11 21:42:17 UTC
Permalink
Hello,

I think this is related to the update of P2 related features.
Here is what I did.
Laurent PETIT
2014-03-11 21:49:10 UTC
Permalink
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.
--
Laurent
Post by Laurent PETIT
Hello,
I think this is related to the update of P2 related features.
Here is what I did.
Laurent PETIT
2014-03-12 21:25:48 UTC
Permalink
Post by Laurent PETIT
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 :-(
Post by Laurent PETIT
--
Laurent
Hello,
Post by Jeff MAURY
I think this is related to the update of P2 related features.
Here is what I did.
Continue reading on narkive:
Loading...