Re: [tycho-dev] build failures with latest snapshot

[Igor Fedorenko <igor@xxxxxxxxxxxxxx>]

For optional dependencies, I think it is common to have optional runtime
dependencies that are required for compilation, so I think we need a way
to decouple compile- and run- time dependencies. Currently,
jars.extra.classpath can be used to express compile-only dependencies,
but I am not sure if this is the best solution going forward.

For feature id matching bundle ID... just don't do it. I realize this
will cause migration problems, but this never worked reliably
before and there are no plans to support artifactId != bundle/feature ID
in Tycho going forward (see [1]).

[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=353384

--
Regards,
Igor

On 11-08-26 9:42 AM, Steffen Pingel wrote:
> Since the latest Tycho snapshot release Mylyn builds are starting to
> fail. From a quick glance, there are two changes: Optional
> dependencies are no longer resolved (we use implicit targets in
> nightly builds) and Maven artifact ids are now expected to match
> feature and plug-in ids.
>
> Concerning the optional dependencies, is the Tycho behavior going to
> change again or do these now need to be marked as greedy in all
> manifests (assuming that's the cause of the problem)?
>
> Changing artifact ids is easy but what is the recommended strategy in
> case a plug-in and feature use the same id?
>
> Thanks,
>
> Steffen