[tycho-user] Tycho & Babel

[Jörg Schaible]

Hi,

for our application we're delivering some additional languages by
default. Therefore I have configured Babel as additional repository in
the target platform.

When I create now a launch configuration and add all required plugins
(incl. the optional ones), Eclipse adds automatically all the plugins
with existing translations for the plugins of the target platform.

How do I get a similar behavior with Tycho? Currently it does not add
those plugins also. I tried to configure in the target-platform-
configuration dependency-resolution/optionalDependencies to "require",
but it has no effect and should have been the default anyway.

What else can I do?

Cheers,
Jörg

[Mickael Istria]

On Thu, Feb 1, 2018 at 4:06 PM, Jörg Schaible <

Post by Jörg Schaible
I tried to configure in the target-platform-
configuration dependency-resolution/optionalDependencies to "require",
but it has no effect

Can you please share the snippet? Do you see the translation fragments
listed in target/work/configuration/config.ini with all other
bundles/fragments?

and should have been the default anyway.
No, it shouldn't have been the default. The target-platform defines what's
available for depedency resolution, not what's mandatory for dependency
resolution. Tycho more usually avoid installing stuff that's not needed
unless you explicitly tell it to (in the target-platfrom-configuration as
you tried).

[Jeff MAURY]

Add them to your product definition ?
ᐧ

Post by Mickael Istria

Post by Jörg Schaible
I tried to configure in the target-platform-
configuration dependency-resolution/optionalDependencies to "require",
but it has no effect

Can you please share the snippet? Do you see the translation fragments
listed in target/work/configuration/config.ini with all other
bundles/fragments?
and should have been the default anyway.
No, it shouldn't have been the default. The target-platform defines what's
available for depedency resolution, not what's mandatory for dependency
resolution. Tycho more usually avoid installing stuff that's not needed
unless you explicitly tell it to (in the target-platfrom-configuration as
you tried).
_______________________________________________
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

--
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

[Jörg Schaible]

Hi,

Post by Jeff MAURY
Add them to your product definition ?
ᐧ

The Babel repository for Oxygen contains ~38.000 optional plugins. In the
platform definition I already trimmed it down to the languages of
interest. The Eclipse launcher easily selects the available ones for all
the standard plugins of the Oxygen platform, that are included in our
product.

Adding them manually and keeping track for new releases of Babel would be
a vary tedious and annoying task. Isn't this something what a build tool
is made for? ;-)

Cheers,
Jörg

[Jeff MAURY]

I think your can add features instead of plugins. This is what I did in my
previous product
ᐧ

On Thu, Feb 1, 2018 at 6:07 PM, Jörg Schaible <

Post by Jörg Schaible
Hi,

Post by Jeff MAURY
Add them to your product definition ?
ᐧ

The Babel repository for Oxygen contains ~38.000 optional plugins. In the
platform definition I already trimmed it down to the languages of
interest. The Eclipse launcher easily selects the available ones for all
the standard plugins of the Oxygen platform, that are included in our
product.
Adding them manually and keeping track for new releases of Babel would be
a vary tedious and annoying task. Isn't this something what a build tool
is made for? ;-)
Cheers,
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

--
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

[Jörg Schaible]

Hi Michael,

On Thu, Feb 1, 2018 at 4:06 PM, Jörg Schaible <

Post by Jörg Schaible
I tried to configure in the target-platform-
configuration dependency-resolution/optionalDependencies to "require",
but it has no effect

Can you please share the snippet?

In the pom.xml of the project root we have configured the plugin like:

============== %< ============
<plugin>
<groupId>org.eclipse.tycho</groupId>
<artifactId>target-platform-configuration</artifactId>
<configuration>
<dependency-resolution>
<optionalDependencies>require</optionalDependencies>
</dependency-resolution>
<environments>
<environment>
<os>win32</os>
<ws>win32</ws>
<arch>x86_64</arch>
</environment>
...
</environments>
<target>
<artifact>
...
</artifact>
</target>
</configuration>
</plugin>
============== %< ============

Do you see the translation fragments
listed in target/work/configuration/config.ini with all other
bundles/fragments?

There is currently a setting in the product definition to generate a
default config.ini file. However, none is created during the Tycho build.
In target I get a big ZIP file containing something that looks like a P2
repo or update site and an additional binary folder with ZIP files
containing the launchers for the configured environments.

and should have been the default anyway.
No, it shouldn't have been the default.

According to the documentation (at least to what I have found), the
default for the configuration setting above is "require". Since there's
no difference in the output if I drop that part in the configuration
completely, I believe the documentation here.

The target-platform defines
what's available for dependency resolution, not what's mandatory for
dependency resolution.

Isn't it, that the available stuff is defined by the artifact with the
target platform definition referenced in the target section of the
plugin? Tycho has a lot more plugins available than the ones that are
finally packed into the result ZIP.

If the "optionalDependency" setting is not the proper parameter to select
the optional plugins as mandatory for dependency resolution, what can I
configure elsewhere?

Tycho more usually avoid installing stuff that's
not needed unless you explicitly tell it to (in the
target-platfrom-configuration as you tried).

What works?

I am using currently Maven 3.5.2, Tycho 1.0.0 with pomless extension.


Regards,
Jörg