Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [tycho-user] Product build always modify config.ini
Yep, I am sure, I even see our config.ini copied in the target/products/<our product id>/config.ini without any modification;
And then the final target/products/<our product id>/win32/win32/x86_64/configuration/config.ini with the bundles injected with a new osgi.bundles key.

But you are right, we had to change the reference to the config.ini file and remove the workspace reference, the config file is located next to the .product and we just used the file name. 

SeB.
De : Jeff MAURY <jeffmaury@xxxxxxxxxxxxx>
Répondre à : Tycho user list <tycho-user@xxxxxxxxxxx>
Date : jeudi 4 septembre 2014 15:35
À : Tycho user list <tycho-user@xxxxxxxxxxx>
Objet : Re: [tycho-user] Product build always modify config.ini

I've look at the Tycho code (https://github.com/eclipse/tycho/blob/master/tycho-packaging-plugin/src/main/java/org/eclipse/tycho/packaging/ProductExportMojo.java) and see that the config.ini is always generated. Are you sure that Tycho loads your external file because the way it is store in the .product file is through a workspace reference (/project/folder1/folder2/config.ini) which cannot be resolved by Tycho

Jeff


On Thu, Sep 4, 2014 at 3:11 PM, Sebastien Gandon <sgandon@xxxxxxxxxx> wrote:
Nope, Tycho finds my config.ini fine because it is the right file that end-up in the final product except that it modifies the « osgi.bundles » property where it should not.
So to be clear, using eclipse export my config.ini is used and not modified, using tycho it is used too but some properties are modified without my consent.

SeB.

De : Jeff MAURY <jeffmaury@xxxxxxxxxxxxx>
Répondre à : Tycho user list <tycho-user@xxxxxxxxxxx>
Date : jeudi 4 septembre 2014 15:05

À : Tycho user list <tycho-user@xxxxxxxxxxx>
Objet : Re: [tycho-user] Product build always modify config.ini

I'm not sure I understand correctly. If you run from Eclipse, your product config.ini is correct ?
This may be because Tycho cannot resolve the reference to the external config.ini. 
Can you see in the .product file to see how it is specified ?

Jeff


On Thu, Sep 4, 2014 at 2:41 PM, Sebastien Gandon <sgandon@xxxxxxxxxx> wrote:
Hi Jeff,
From eclipse meaning using the integrate PDE export, the config.ini does not get injected just like I would expect.
This means  that the tycho handling of the .product differs from the PDE behavior, shall I fill a bugzilla ?

SeB.
De : Jeff MAURY <jeffmaury@xxxxxxxxxxxxx>
Répondre à : Tycho user list <tycho-user@xxxxxxxxxxx>
Date : jeudi 4 septembre 2014 10:38
À : Tycho user list <tycho-user@xxxxxxxxxxx>
Objet : Re: [tycho-user] Product build always modify config.ini

When you generate the product from within Eclipse, do you observe the same behaviour ?

Jeff


On Wed, Sep 3, 2014 at 5:31 PM, Sebastien Gandon <sgandon@xxxxxxxxxx> wrote:
Hello,
We are migrating our PDE build to tycho using .product definition for our product generation.
In our product we specify a config.ini file to be used instead of it getting automatically generated.
Nevertheless our config.ini gets modified by the list of bundles to be launched.

Is there a ways to prevent this as we have our own rcp launcher based on a license file and therefore do not want the property « osgi.bundles » to be modified ?

Of course we can use the "maven-resources-plugin » at the packaging phase to overwrite the file but is there a cleanest way ?
Thanks.

SeB.

Sébastien Gandon

Eclipse Software Architect 
Email : sgandon@xxxxxxxxxx | Skype : sebastien.gandon.talend.com
Talend SA | 9, rue Pagès - 92150 Suresnes - France | +33 1 46 25 06 00 | www.talend.com

Global Leader in Open Source Integration 


_______________________________________________
tycho-user mailing list
tycho-user@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/tycho-user



--
Jeff MAURY


"Legacy code" often differs from its suggested alternative by actually working and scaling.
 - Bjarne Stroustrup

http://www.jeffmaury.com
http://riadiscuss.jeffmaury.com
http://www.twitter.com/jeffmaury

_______________________________________________
tycho-user mailing list
tycho-user@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/tycho-user



--
Jeff MAURY


"Legacy code" often differs from its suggested alternative by actually working and scaling.
 - Bjarne Stroustrup

http://www.jeffmaury.com
http://riadiscuss.jeffmaury.com
http://www.twitter.com/jeffmaury

_______________________________________________
tycho-user mailing list
tycho-user@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/tycho-user



--
Jeff MAURY


"Legacy code" often differs from its suggested alternative by actually working and scaling.
 - Bjarne Stroustrup

http://www.jeffmaury.com
http://riadiscuss.jeffmaury.com
http://www.twitter.com/jeffmaury

Back to the top