p2-dev

[p2-dev] Is it possible to install a feature into an RCP app at build time?

briandealwis@xxxxxxx (Brian de Alwis) — Thu, 17 May 2012 11:32:31 GMT

On Wednesday, 16 May 2012, Trace Windham wrote:

Unfortunately, it is not installed at the root level of installed features. Instead, the feature is a child of the main RCP feature of my RCP application, and therefore when updates are available for this child feature they are not found during the execution of the "Check For Updates" command in my RCP application. My requirement is that this feature be independently updatable without having to be manually installed by a user. I think this is what the patch in bug 361722 addresses.

Do you think I'm accurate in this explanation? I'm not yet confident of my knowledge in this area.

Technically these features can still be updated by p2 independently of the product, even though they aren't root-level. But I guess the p2 Update UI only considers root-level IUs.

So I guess your antrun to install via the director is the best approach for now.

Brian.

Re: [p2-dev] Is it possible to install a feature into an RCP app at build time?

twindham@xxxxxxx (Trace Windham) — Wed, 16 May 2012 19:18:17 GMT

Brian,

First off, thank you for all of your help, I'm learning a great deal today.

The good news is that I have something that works now.

The bad news is that it is not quite working as desired.

Because of this experience, I can now see where your solution is different from the solution proposed by the bug described at https://bugs.eclipse.org/bugs/show_bug.cgi?id=361722

By making the modifications that you suggested to my <>.p2.inf file, I have successfully had my feature installed into my RCP application. Unfortunately, it is not installed at the root level of installed features. Instead, the feature is a child of the main RCP feature of my RCP application, and therefore when updates are available for this child feature they are not found during the execution of the "Check For Updates" command in my RCP application. My requirement is that this feature be independently updatable without having to be manually installed by a user. I think this is what the patch in bug 361722 addresses.

Do you think I'm accurate in this explanation? I'm not yet confident of my knowledge in this area.

Thanks,

Trace Windham

On Wed, May 16, 2012 at 1:34 PM, Brian de Alwis <briandealwis@xxxxxxxxx> wrote:

>
>
>
>
>

You can simplify these for Tycho and just specify the id attribute; that'll cause Tycho to pick up the latest version. I doubt Tycho even uses the url attribute.

> How is the RCP build going to find that? My other feature is built completely independently of the RCP build. When I ran my RCP build, the other feature still was not pre installed.

Tycho will find it as long as the feature is available in either your ~/.m2/repository, one of the configured , or is one of the projects being built.

> So I modified the RCP's category.xml by adding the url of my other feature's p2 repository and made it look like this,
>
> http://mydomain.com/p2reposiotry/myotherfeature/features/com.mydomain.myotherfeature.feature_1.0.0.qualifier.jar" id="com.mydomain.myotherfeature.feature" version="1.0.0.qualifier">
>
> But, that didn't work either.

Ah, that's likely the problem: the repository has to be added to your list. You should be able to add something like the following to your pom.xml:

jre
p2
http://mydomain.com/p2reposiotry/myotherfeature/

(note that there appears to be a typo: "reposiotory" vs "repository")

> Another reply on this discussion mentioned this bug, https://bugs.eclipse.org/bugs/show_bug.cgi?id=361722 and that leads me to believe that Tycho doesn't have the ability to do this, yet.

Well I do it in my product builds and have been for over a year ;)

Brian.

_______________________________________________
p2-dev mailing list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev

Trace Windham

Re: [p2-dev] How to update from a password protected repository?

carlos_odonell@xxxxxxx (Carlos O'Donell) — Wed, 16 May 2012 18:43:45 GMT

On 5/16/2012 2:10 PM, Samuel Wu wrote:
> When I tried to access a password protected web site for the update,
> I got the error message Authentication failed without being prompted
> for user ID and password. Wonder where to set the user id and
> password. Thanks. Best Regards

There was a recently fixed bug about this.

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

It should work with a recent enough Eclipse/p2.

Cheers,
Carlos.
-- 
Carlos O'Donell
Mentor Graphics / CodeSourcery
carlos_odonell@xxxxxxxxxx
carlos@xxxxxxxxxxxxxxxx
+1 (613) 963 1026

Re: [p2-dev] Is it possible to install a feature into an RCP app at build time?

briandealwis@xxxxxxx (Brian de Alwis) — Wed, 16 May 2012 18:35:02 GMT

> 
> 
>    
>       
>    

You can simplify these for Tycho and just specify the id attribute; that'll cause Tycho to pick up the latest version.  I doubt Tycho even uses the url attribute.

> How is the RCP build going to find that?  My other feature is built completely independently of the RCP build.  When I ran my RCP build, the other feature still was not pre installed.

Tycho will find it as long as the feature is available in either your ~/.m2/repository, one of the configured , or is one of the projects being built.

> So I modified the RCP's category.xml by adding the url of my other feature's p2 repository and made it look like this, 
> 
> http://mydomain.com/p2reposiotry/myotherfeature/features/com.mydomain.myotherfeature.feature_1.0.0.qualifier.jar"; id="com.mydomain.myotherfeature.feature" version="1.0.0.qualifier">
> 
> But, that didn't work either.

Ah, that's likely the problem: the repository has to be added to your list.  You should be able to add something like the following to your pom.xml:

  
    
      jre
      p2
      http://mydomain.com/p2reposiotry/myotherfeature/
    
  

(note that there appears to be a typo: "reposiotory" vs "repository")

> Another reply on this discussion mentioned this bug, https://bugs.eclipse.org/bugs/show_bug.cgi?id=361722  and that leads me to believe that Tycho doesn't have the ability to do this, yet.

Well I do it in my product builds and have been for over a year ;)

Brian.

Attachment: smime.p7s
Description: S/MIME cryptographic signature

[p2-dev] How to update from a password protected repository?

samuelwu@xxxxxxx (Samuel Wu) — Wed, 16 May 2012 18:10:45 GMT

When I tried to access a password protected web site for the update, I got the error message Authentication failed without being prompted for user ID and password. Wonder where to set the user id and password. Thanks.
Best Regards

Samuel Wu

Re: [p2-dev] Is it possible to install a feature into an RCP app at build time?

twindham@xxxxxxx (Trace Windham) — Wed, 16 May 2012 15:39:47 GMT

I've added my feature to the category.xml for my RCP product, but this didn't cause the feature to be pre installed after the build of the RCP product was finished.

My feature that I want to be pre installed is built completely independent from my RCP product. It has it's own parent pom.xml file and it's own category.xml file.

How does the category.xml file for my RCP product know where to find my feature that I want pre installed?

Here's what is in my category.xml file now that I've added my Feature to it.

Eclipse based features provided by My Company's Software Development Group

I noticed that the attribute "url" was set to "features/com.mydomain.myotherfeature.feature_1.0.0.qualifier.jar", and I thought.

How is the RCP build going to find that? My other feature is built completely independently of the RCP build. When I ran my RCP build, the other feature still was not pre installed.

So I modified the RCP's category.xml by adding the url of my other feature's p2 repository and made it look like this,

http://mydomain.com/p2reposiotry/myotherfeature/features/com.mydomain.myotherfeature.feature_1.0.0.qualifier.jar" id="com.mydomain.myotherfeature.feature" version="1.0.0.qualifier">

But, that didn't work either.

I think I'm still missing something here. Does Tycho have the ability to even do this?

Another reply on this discussion mentioned this bug, https://bugs.eclipse.org/bugs/show_bug.cgi?id=361722 and that leads me to believe that Tycho doesn't have the ability to do this, yet.

Thanks again for your time, it is greatly appreciated.

Trace Windham

On Wed, May 16, 2012 at 8:58 AM, Brian de Alwis <briandealwis@xxxxxxxxx> wrote:

On 16-May-2012, at 9:41 AM, Trace Windham wrote:
> Is there something else I need to do to get your proposed solution to work?

You need to ensure the features are included in the category.xml so that they are pulled in and available for installation.

Brian.
_______________________________________________
p2-dev mailing list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev

Trace Windham

Re: [p2-dev] Is it possible to install a feature into an RCP app at build time?

briandealwis@xxxxxxx (Brian de Alwis) — Wed, 16 May 2012 13:58:15 GMT

On 16-May-2012, at 9:41 AM, Trace Windham wrote:
> Is there something else I need to do to get your proposed solution to work?

You need to ensure the features are included in the category.xml so that they are pulled in and available for installation.

Brian.

Attachment: smime.p7s
Description: S/MIME cryptographic signature

Re: [p2-dev] Is it possible to install a feature into an RCP app at build time?

twindham@xxxxxxx (Trace Windham) — Wed, 16 May 2012 13:41:36 GMT

Brian,

I already have a <>.p2.inf file alongside my <>.product, and currently, it looks like this...

instructions.configure=\

org.eclipse.equinox.p2.touchpoint.eclipse.addRepository(location:http${#58}//mydomain.com/myp2repository/myrequiredfeature/,type:0,name:My Required Feature Name,enabled:true);\

org.eclipse.equinox.p2.touchpoint.eclipse.addRepository(location:http${#58}// mydomain.com/myp2repository/myrequiredfeature/ ,type:1,name: My Required Feature Name ,enabled:true);

This entry successfully adds the repository to my RCP application during build time.

I've added the entries you suggested and I ran by full build for my RCP app using "mvn clean install", and the feature doesn't not get installed in my RCP application.

Is there something else I need to do to get your proposed solution to work?

Thanks,

Trace Windham

On Tue, May 15, 2012 at 6:17 PM, Brian de Alwis <briandealwis@xxxxxxxxx> wrote:

Since you're using Tycho, you can save yourself a step and add a <>.p2.inf file alongside your <>.product file containing something like:

requires.101.namespace=org.eclipse.equinox.p2.iu
requires.101.name=my.feature.name.feature.group

requires.101.range=[0.9.1,1.0.0)

Repeat that for the features you'd like to have pre-installed, incrementing the "101" for each feature.

Brian.

On 15-May-2012, at 4:25 PM, Trace Windham wrote:

Thanks Paul, that worked like a charm.

Since Tycho had already zipped up my deliverable product, I had to add an ant zip task to re zip the product after I modified it using your ant task below.

It was no big deal, but I thought I should mention it for the next guy that reads this someday.

Thanks again!
TW

On Tue, May 15, 2012 at 12:19 PM, Paul Webster <pwebster@xxxxxxxxxxxxxxxxxxx> wrote:

You can use the p2 director as a final step in your build.

basebuilder/eclipse \
-application org.eclipse.equinox.p2.director \
-noSplash \
-repository \
http://download.eclipse.org/releases/juno \
-destination \
/path/to/rcp/build \
-bundlepool \
/path/to/rcp/build \
-installIUs \
org.eclipse.emf.sdk.feature.group

It can be called from your postBuild ant target as well, for example see http://git.eclipse.org/c/platform/eclipse.platform.releng.eclipsebuilder.git/tree/eclipse/buildConfigs/sdk.tests/testScripts/test.xml#n289

PW

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

_______________________________________________
p2-dev mailing list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev

--
Trace Windham

_______________________________________________
p2-dev mailing list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev

_______________________________________________
p2-dev mailing list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev

Trace Windham

Re: [p2-dev] Is it possible to install a feature into an RCP app at build time?

albertopose@xxxxxxx (Alberto Miguel Pose) — Wed, 16 May 2012 00:09:12 GMT

Have you look at the following patch: https://bugs.eclipse.org/bugs/show_bug.cgi?id=361722 ?

HTH!

On Tue, May 15, 2012 at 4:17 PM, Brian de Alwis <briandealwis@xxxxxxxxx> wrote:

Since you're using Tycho, you can save yourself a step and add a <>.p2.inf file alongside your <>.product file containing something like:

requires.101.namespace=org.eclipse.equinox.p2.iu
requires.101.name=my.feature.name.feature.group

requires.101.range=[0.9.1,1.0.0)

Repeat that for the features you'd like to have pre-installed, incrementing the "101" for each feature.

Brian.

On 15-May-2012, at 4:25 PM, Trace Windham wrote:

Thanks Paul, that worked like a charm.

Since Tycho had already zipped up my deliverable product, I had to add an ant zip task to re zip the product after I modified it using your ant task below.

It was no big deal, but I thought I should mention it for the next guy that reads this someday.

Thanks again!
TW

On Tue, May 15, 2012 at 12:19 PM, Paul Webster <pwebster@xxxxxxxxxxxxxxxxxxx> wrote:

You can use the p2 director as a final step in your build.

basebuilder/eclipse \
-application org.eclipse.equinox.p2.director \
-noSplash \
-repository \
http://download.eclipse.org/releases/juno \
-destination \
/path/to/rcp/build \
-bundlepool \
/path/to/rcp/build \
-installIUs \
org.eclipse.emf.sdk.feature.group

It can be called from your postBuild ant target as well, for example see http://git.eclipse.org/c/platform/eclipse.platform.releng.eclipsebuilder.git/tree/eclipse/buildConfigs/sdk.tests/testScripts/test.xml#n289

PW

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

_______________________________________________
p2-dev mailing list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev

--
Trace Windham

_______________________________________________
p2-dev mailing list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev

_______________________________________________
p2-dev mailing list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev

Re: [p2-dev] Is it possible to install a feature into an RCP app at build time?

briandealwis@xxxxxxx (Brian de Alwis) — Tue, 15 May 2012 23:17:08 GMT

Since you're using Tycho, you can save yourself a step and add a <>.p2.inf file alongside your <>.product file containing something like:

requires.101.namespace=org.eclipse.equinox.p2.iu
requires.101.name=my.feature.name.feature.group
requires.101.range=[0.9.1,1.0.0)

Repeat that for the features you'd like to have pre-installed, incrementing the "101" for each feature.

Brian.

On 15-May-2012, at 4:25 PM, Trace Windham wrote:

Thanks Paul, that worked like a charm.

Since Tycho had already zipped up my deliverable product, I had to add an ant zip task to re zip the product after I modified it using your ant task below.

It was no big deal, but I thought I should mention it for the next guy that reads this someday.

Thanks again!
TW

On Tue, May 15, 2012 at 12:19 PM, Paul Webster <pwebster@xxxxxxxxxxxxxxxxxxx> wrote:

You can use the p2 director as a final step in your build.

basebuilder/eclipse \
-application org.eclipse.equinox.p2.director \
-noSplash \
-repository \
http://download.eclipse.org/releases/juno \
-destination \
/path/to/rcp/build \
-bundlepool \
/path/to/rcp/build \
-installIUs \
org.eclipse.emf.sdk.feature.group

It can be called from your postBuild ant target as well, for example see http://git.eclipse.org/c/platform/eclipse.platform.releng.eclipsebuilder.git/tree/eclipse/buildConfigs/sdk.tests/testScripts/test.xml#n289

PW

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

_______________________________________________
p2-dev mailing list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev

--
Trace Windham

_______________________________________________
p2-dev mailing list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev

Attachment: smime.p7s
Description: S/MIME cryptographic signature