| RCP self-update modifying product ini file [message #684914] |
Thu, 16 June 2011 13:20  |
 Prasanna Uppaladadium
Messages: 3
Registered: June 2011 |
Junior Member |
|
|
Hello --
When my p2 enabled RCP application gets updated automatically, its corresponding .ini file also gets modified. In particular, some -D arguments to the -vmargs option are removed. I am wondering if someone has experienced this problem before and has solved it. I greatly appreciate any pointers and help.
Here are the details:
a. The product is installed in C:\Scout. It has a Scout.ini file under C:\Scout.
b. The original contents of Scout.ini are as follows:
-vm
jre6/bin/javaw.exe
-vmargs
-Dosgi.splashPath=platform:/base/plugins/com.liquidnet.gpss.scout
-Dscout.xyz.host=host1
-Dscout.xyz.vpn=abc
-Dscout.xyz.user=default
-Dscout.idleTimeout=10
c. After the update, the contents of the file are as follows:
-vm
jre6/bin/javaw.exe
-vmargs
-Dosgi.splashPath=platform:/base/plugins/com.liquidnet.gpss.scout
-Dscout.xyz.host=host1
-Dscout.idleTimeout=10
d. Note that the vpn and user arguments have been removed.
e. I am using Eclipse RCP version 3.6 (Helios). My p2.inf file looks like this:
instructions.configure=\
addRepository(type:0,location:http${#58}//xyz.biz/eclipse,name:Scout Eclipse Repository,enabled:true);\
addRepository(type:1,location:http${#58}//xyz.biz/eclipse,name:Scout Eclipse Repository,enabled:true);\
addRepository(type:0,location:http${#58}//xyz.biz/scout,name:Scout,enabled:true);\
addRepository(type:1,location:http${#58}//xyz/scout,name:Scout,enabled:true);
The application's build process generates a p2 repository that is then hosted in a web server to enable auto-updates.
When a new product version is built and its p2 repository is deployed, the existing versions of the application correctly identify this and update themselves (except for the undesirable update to the .ini file). I am using the org.eclipse.equinox.p2.user.ui feature in the product so the entire update operation is left to the default implementation of p2 SDK's UI.
Thank you,
Prasanna
|
|
|
| Re: RCP self-update modifying product ini file [message #686126 is a reply to message #684914] |
Sun, 19 June 2011 15:05  |
Beyhan Veliev
Messages: 3
Registered: July 2009 |
Junior Member |
|
|
Do any of your repositories contain touch points to add/remove vmargs?
Missing touch points to add the unconfigured vmargs could be the problem.
Cheers,
Beyhan
On 16.06.2011 15:20, Prasanna Uppaladadium wrote:
> Hello --
>
> When my p2 enabled RCP application gets updated automatically, its
> corresponding .ini file also gets modified. In particular, some -D
> arguments to the -vmargs option are removed. I am wondering if someone
> has experienced this problem before and has solved it. I greatly
> appreciate any pointers and help.
>
> Here are the details:
>
> a. The product is installed in C:\Scout. It has a Scout.ini file under
> C:\Scout.
>
> b. The original contents of Scout.ini are as follows:
>
> -vm
> jre6/bin/javaw.exe
> -vmargs
> -Dosgi.splashPath=platform:/base/plugins/com.liquidnet.gpss.scout
> -Dscout.xyz.host=host1
> -Dscout.xyz.vpn=abc
> -Dscout.xyz.user=default
> -Dscout.idleTimeout=10
>
> c. After the update, the contents of the file are as follows:
>
> -vm
> jre6/bin/javaw.exe
> -vmargs
> -Dosgi.splashPath=platform:/base/plugins/com.liquidnet.gpss.scout
> -Dscout.xyz.host=host1
> -Dscout.idleTimeout=10
>
> d. Note that the vpn and user arguments have been removed.
>
> e. I am using Eclipse RCP version 3.6 (Helios). My p2.inf file looks
> like this:
>
> instructions.configure=\
> addRepository(type:0,location:http${#58}//xyz.biz/eclipse,name:Scout
> Eclipse Repository,enabled:true);\
> addRepository(type:1,location:http${#58}//xyz.biz/eclipse,name:Scout
> Eclipse Repository,enabled:true);\
> addRepository(type:0,location:http${#58}//xyz.biz/scout,name:Scout,enabled:true);\
>
> addRepository(type:1,location:http${#58}//xyz/scout,name:Scout,enabled:true);
>
>
> The application's build process generates a p2 repository that is then
> hosted in a web server to enable auto-updates.
>
> When a new product version is built and its p2 repository is deployed,
> the existing versions of the application correctly identify this and
> update themselves (except for the undesirable update to the .ini file).
> I am using the org.eclipse.equinox.p2.user.ui feature in the product so
> the entire update operation is left to the default implementation of p2
> SDK's UI.
>
> Thank you,
> Prasanna
>
--
Beyhan Veliev
Twitter: @EclipseRAP
Blog: http://eclipsesource.com/blogs/
Professional services for RAP and RCP?
http://eclipsesource.com/services/rap/
|
|
|
Powered by
FUDForum. Page generated in 0.04043 seconds
] 
Search
Help
Register
Login
Home
