Re: [tycho-dev] "implicit target platform" -> "simple target platform"

[Igor Fedorenko <igor@xxxxxxxxxxxxxx>]

I always said, or at least implied, implicit and explicit target
platform *specifications*. Term "explicit" seemed like a good fit
when target platform contents was specified in .target file, and
naturally "implicit specification" was used to describe the case where
there was no explicit specification. I do agree that "implicit target
platform" does not make much sense.

Also note that the list of p2 repositories accessible by the project can
be changed at build-time using settings.xml, new repositories can be
introduced and existing repositories can be redirected to a mirror.

Anyways, not saying the terms are good, just explaining where they came
from. ;-)

--
Regards,
Igor

On 11-11-18 12:25 PM, Oberlies, Tobias wrote:
> How about saying that a project has a “simple target platform” if no
> target file is used but only repositories with layout p2?
> This is IMHO better than “implicit target platform”, because
>
>   * even with a target file, the resolution result can be non-explicit
>     in certain cases, e.g. if multiple versions of a bundle are included
>     (which is possible with includeMode=slicer)
>   * even though the resolution result is typically not explicitly
>     determined when repositories with layout p2 are used, the content of
>     the “target platform” (=artifact against which the project
>     dependencies may be matched) is explicitly specified. For example, I
>     can explicitly state that my project builds against Indigo.
>     “Non-explicit” or “implicit” makes me rather think of target
>     platform content which is not specified in the POM like the locally
>     built artifacts (but I am not proposing to use the term “implicit
>     target platform” for that instead ;-)
>
> What do you think?
> Regards
> Tobias
>
>
> _______________________________________________
> tycho-dev mailing list
> tycho-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/tycho-dev