Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [tycho-user] What change in 0.15.0 caused the arch-specific entries in the application ini file?

this may be a change in the p2 product publisher. We are using p2 from Juno M7 in tycho 0.15.0.

we need more specific info and a small sample project to tell what's going on here.

- what exactly is the observed behaviour with the older version (which version?) of tycho?
- what exactly is the observed behaviour with tycho 0.15.0?

Jan

From: tycho-user-bounces@xxxxxxxxxxx [mailto:tycho-user-bounces@xxxxxxxxxxx] On Behalf Of Hansen, Alexander
Sent: Dienstag, 12. Juni 2012 08:35
To: tycho-user@xxxxxxxxxxx
Subject: [tycho-user] What change in 0.15.0 caused the arch-specific entries in the application ini file?

Hi! 

I recognized arch specific entries (launcher JAR) in my RCP applications ini file and I´m curious which change caused these. Especially because I did something similar using the p2 adivce file and these entries get overwritten now. What I did is copying arch specific ini files (different -vm entries for different archs, mainly win32 / win32_64) to the root directory during the configure stage. The <launcherArgs> section in my product file is empty, so no ini file was generated at all.


Back to the top