Hi,
I’m in favor of this enhancement, too, thanks for requesting.
In the meantime, I also tried updating the whole product, but this doesn’t work when building with tycho.
TYCHO: It builds and runs fine, it just doesn’t find any updates.
PDE: When building the application and the following updated product/repository via PDE, it updates just fine.
Steps:
1-
build product
2-
update product version in .product/.pom
+ update feature version in feature.xml and .pom
+ referencing new feature version in .product
3-
build product and repository again
4-
update product (1) using the repository (3) via headless update
Am I missing something? What does PDE do differently, since it works fine?
Regards Robert
Von: tycho-user-bounces@eclipse.org
[mailto:tycho-user-bounces@xxxxxxxxxxx] Im Auftrag von Greg Amerson
Gesendet: Samstag, 22. Oktober 2011 11:22
An: Tycho user list
Betreff: Re: [tycho-user] Unable to update installable featuresthat are declared in a .product file independent of updatingthe product
Greg Amerson wrote:
> I am having the same problem described in this thread. Is there a way to
> install features into a build after a product has been created with Tycho?
> Of course we could use ant and p2 director to perform the install.
This is not possible, but would be a very useful extension of the current functionality. You should create an enhancement describing the use case in Bugzilla, and if possible, provide a patch ;-) But also just the enhancement request would
help.
Will do, I've entered an enhancement request here:
> Another question... is it possible to generate a repository site that
> contains the updated product, so that it can actually be updated including
> all of the dependent features?
Another build of your project after you have change the product?
Ok I have cleared up my own confusion on this. When I create the new build and get a new zip file of the repository, and when I would select this repository in my product and select it in the "Install new software..." dialog, I would just
see the top level feature, not the product. So I would try to update this "feature" and it would fail for the reasons mentioned in this thread. however, if I disable all of the other repositories in my product and just enable the new repository zip file
and use "Check for updates..." I'm presented with the "product" update which works.
Is there a way to invoke this product only update by pointing to the zip file in the Install dialog invoked from "install new software..."? Or does it only work from "check for updates.." action.
Greg Babcock wrote:
> This did not work for me.
>
> 1. I removed the a feature A from the .product dependencies and
> performed a build and verified that it was removed from the target
> repository, and the product.
>
> 2. I added the feature A as requirement in the <product_id>.p2.inf file
> adjacent to the .product file and performed a build. Feature A was once
> again installed in the repository, and installed in the product as a
> dependency of the product IU, and not at the root level as required to be
> independently updatable feature.
This is only partially true: The important thing is whether the installed product has a hard or version range requirement to the feature. The instructions in Andrews blog create a version range link, which allow new versions of the feature
to be installed.
The drawback of what you can currently achieve with Tycho is that this isn't particularly obvious to the users:
- Check for updates will not report new versions of the feature. For that, it would need to be listed as top-level installed feature.
- IIRC, the feature will be silently updated whenever something else is installed or updated.
So it is possible to update the feature, but I can understand if you would want the feature as top-level feature... Your requests are all very valid, please open enhancements in Bugzilla.
Regards
Tobias
--
Liferay, Inc.
