[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [p2-dev] [equinox-dev] Writing something into the config.ini file

Hi All,
 
Ok, I think I found a bug with the p2.inf file.  Just wanted to run it by you before I create a bug.  If I create a p2.inf file with a set of instructions it works fine.  As soon as I modify the p2.inf file to do other stuff, it seems as though p2 doesn't execute the commands as times or fails to execute them other times.  I tested my theory by having a failing project.  I then create a new project, with the same data and it works fine.  Could it be that there is something being cached somewhere in p2 itself?
 
BR,
Dom


From: Domenico Alessi
Sent: May-13-11 8:14 AM
To: 'P2 developer discussions'
Subject: RE: [p2-dev] [equinox-dev] Writing something into the config.ini file

Hi Andrew,
 
Is there a document that describes these states?  Also, I tried the configure phase, but no luck.  I am not sure what I am doing wrong.  I have attached my project, would you have time to have a look?
 
Thanks in advance,
Dom


From: p2-dev-bounces@xxxxxxxxxxx [mailto:p2-dev-bounces@xxxxxxxxxxx] On Behalf Of Andrew Niefer
Sent: May-12-11 2:49 PM
To: P2 developer discussions
Subject: Re: [p2-dev] [equinox-dev] Writing something into the config.ini file

There is probably an ordering issue.
The root files will be artifacts associated with a second IU "feature_root" that is required by your feature's IU.  It is likely that the feature is getting installed first and the root file IU will be done a bit later, so when the feature's install actions run, the zip has not been extracted yet.

The zip will be extracted during the install phase for the root IU, the configure phase happens later, so things should work better if you move the unzip action to the configure phase.

-Andrew


From: Domenico Alessi <domenico.alessi@xxxxxxxxxxxx>
To: Equinox development mailing list <equinox-dev@xxxxxxxxxxx>
Cc: P2 developer discussions <p2-dev@xxxxxxxxxxx>
Date: 05/12/2011 12:38 PM
Subject: Re: [p2-dev] [equinox-dev] Writing something into the config.ini        file
Sent by: p2-dev-bounces@xxxxxxxxxxx





Hi Guys,
 
So trying some other nifty stuff out.  I have placed a zip file into the feature and I have this as my p2.inf
 
instructions.configure = \
org.eclipse.equinox.p2.touchpoint.eclipse.setProgramProperty(propName:testValue1,propValue:testValue2);\
instructions.install = \
org.eclipse.equinox.p2.touchpoint.natives.unzip(source:${installFolder}/test_temp/test.zip,target:${installFolder}/);\

 
Now, the zip files is there after installation as I set it to be there using
 
root.folder.test_temp=file:test.zip
 
in my feature build.properties
 
I see the following in my context.xml
 
- <touchpointData size="1">
- <instructions size="2">
 <instruction key="install">org.eclipse.equinox.p2.touchpoint.natives.unzip(source:${installFolder}/test_temp/test.zip,target:${installFolder}/);</instruction>
 <instruction key="configure">org.eclipse.equinox.p2.touchpoint.eclipse.setProgramProperty(propName:testValue1,propValue:testValue2);</instruction>
 </instructions>
 </touchpointData>

But, I don't see the zip file being extracted.  I have included org.eclipse.equinox.p2.touchpoint.natives in my feature.xml as a dependency.   Any thoughts?
 
Thanks,
Dom


From: equinox-dev-bounces@xxxxxxxxxxx [mailto:equinox-dev-bounces@xxxxxxxxxxx] On Behalf Of Pascal Rapicault
Sent:
May-11-11 3:22 PM
To:
Equinox development mailing list
Cc:
P2 developer discussions
Subject:
Re: [equinox-dev] Writing something into the config.ini file


If you want to make your example on the ML, I'm sure others would find it handy.

On 2011-05-11, at 3:21 PM, Domenico Alessi wrote:

Arg!  Nevermind, caching effect.  Worked like a charm.  
 
Thanks.  Dom


From: equinox-dev-bounces@xxxxxxxxxxx [mailto:equinox-dev-bounces@xxxxxxxxxxx] On Behalf Of Domenico Alessi
Sent:
May-11-11 3:12 PM
To:
Equinox development mailing list
Cc:
P2 developer discussions
Subject:
Re: [equinox-dev] Writing something into the config.ini file


Thanks Pascal.
 
Ok, so before I put the plugin below into the dependencies, I saw the actions in the content.jar.  Now that I have put in the include I no longer see the actions in my content.jar file.  So nothing gets placed into my config.ini, but install passes.
 
Thanks,
Dom


From: equinox-dev-bounces@xxxxxxxxxxx [mailto:equinox-dev-bounces@xxxxxxxxxxx] On Behalf Of Pascal Rapicault
Sent:
May-11-11 2:40 PM
To:
Equinox development mailing list
Cc:
P2 developer discussions
Subject:
Re: [equinox-dev] Writing something into the config.ini file


Make sure that the org.eclipse.equinox.p2.touchpoint.eclipse is in available.

On 2011-05-11, at 2:33 PM, Domenico Alessi wrote:

Hi Pascal,

I get the following error at install time:

 

An error occurred while configuring the installed items

session context was:(profile="" phase=org.eclipse.equinox.internal.p2.engine.phases.Configure, operand=null --> [R]com.test.p2.feature.feature.group 1.0.0.201105111415, action="">

No action found for: setProgramProperty.

No action found for: setProgramProperty.

My p2.inf looks like this:
 

instructions.configure=\

setProgramProperty(propName:testValue1,propValue:testValue2);\



Thanks in advance,
Dom


From: equinox-dev-bounces@xxxxxxxxxxx [mailto:equinox-dev-bounces@xxxxxxxxxxx] On Behalf Of Pascal Rapicault
Sent:
May-11-11 1:36 PM
To:
Equinox development mailing list; P2 developer discussions
Subject:
Re: [equinox-dev] Writing something into the config.ini file


This can be done using a touchpoint action (Provisioning Actions and Touchpoints)
In this particular case: setProgramProperty, for example setProgramProperty(propName:equinox.use.ds, propValue:true);

To get this added to your metadata you need to store that into a p2.inf file (Customizing metadata)


On 2011-05-11, at 1:30 PM, Domenico Alessi wrote:

Hi All,

I a have quick question.  I have a feature/plugin that I wish to install but I also want at installation time to put in a key/value pair into the config.ini.  I see that install Handlers are discouraged.  How can I accomplish this?

BR,
Dom

_______________________________________________
equinox-dev mailing list

equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev

_______________________________________________
equinox-dev mailing list

equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev

_______________________________________________
equinox-dev mailing list

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