[tycho-user] Tycho 1.2.0: Materialize-product generates invalid ini file

[Jörg Schaible]

Hi,

we have a strange effect in our build. We have two product files
configured for the materialize-product goal of the tycho-p2-director
plugin and support 3 OS targets.

The generated ini files for one product are correct for all target OSes,
but the ini files for the other product are "invalid" for all OSes, e.g.
Windows:

============ %< ===================
-startup
plugins/org.eclipse.equinox.launcher_1.4.0.v20161219-1356.jar
--launcher.library
plugins/
org.eclipse.equinox.launcher.win32.win32.x86_64_1.1.551.v20171108-1834
-nl
de
--launcher.library
/data/head/temp/products/target/products/com.bpminspire.designer/win32/
win32/x86_64/plugins/
org.eclipse.equinox.launcher.win32.win32.x86_64_1.1.551.v20171108-1834
-startup
/data/head/temp/products/target/products/com.bpminspire.designer/win32/
win32/x86_64/plugins/org.eclipse.equinox.launcher_1.4.0.v20161219-1356.jar
-vmargs
-Xms512m
-Xmx1024m
--add-modules=ALL-SYSTEM
============ %< ===================

The entries for startup and launcher.library are contained twice and the
second entries with the absolute paths from the build server clobber the
first (correct) ones, when the application tries to start. Obviously the
start fails.

We compared the two product files and cannot find any relevant difference.

Any idea, what causes those entries with absolute paths in the generated
ini files?

Regards,
Jörg

[Mickael Istria]

Hi,

Did you try the Tycho examples? Do they have the same issue? If yes,
please open a bug to bugs.eclipse.org so it has more chances to be
fixed in the future.

Cheers,

Post by Jörg Schaible
Hi,
we have a strange effect in our build. We have two product files
configured for the materialize-product goal of the tycho-p2-director
plugin and support 3 OS targets.
The generated ini files for one product are correct for all target OSes,
but the ini files for the other product are "invalid" for all OSes, e.g.
============ %< ===================
-startup
plugins/org.eclipse.equinox.launcher_1.4.0.v20161219-1356.jar
--launcher.library
plugins/
org.eclipse.equinox.launcher.win32.win32.x86_64_1.1.551.v20171108-1834
-nl
de
--launcher.library
/data/head/temp/products/target/products/com.bpminspire.designer/win32/
win32/x86_64/plugins/
org.eclipse.equinox.launcher.win32.win32.x86_64_1.1.551.v20171108-1834
-startup
/data/head/temp/products/target/products/com.bpminspire.designer/win32/
win32/x86_64/plugins/org.eclipse.equinox.launcher_1.4.0.v20161219-1356.jar
-vmargs
-Xms512m
-Xmx1024m
--add-modules=ALL-SYSTEM
============ %< ===================
The entries for startup and launcher.library are contained twice and the
second entries with the absolute paths from the build server clobber the
first (correct) ones, when the application tries to start. Obviously the
start fails.
We compared the two product files and cannot find any relevant difference.
Any idea, what causes those entries with absolute paths in the generated
ini files?
Regards,
Jörg
_______________________________________________
tycho-user mailing list
To change your delivery options, retrieve your password, or unsubscribe from
this list, visit
https://dev.eclipse.org/mailman/listinfo/tycho-user

[Jörg Schaible]

Hi Mickael,

Post by Mickael Istria
Hi,
Did you try the Tycho examples? Do they have the same issue? If yes,
please open a bug to bugs.eclipse.org so it has more chances to be fixed
in the future.

I tried to reproduce this with itp04-rcp (adding another product), but it
works as expected. I still have no idea, what triggers the strange
behavior for our build. :-/

Cheers,
Jörg