Re: [tycho-dev] [pomless] maven-deploy-plugin configuration

["Fauth Dirk (XC-ECO/ESM1)" <Dirk.Fauth@xxxxxxxxxxxx>]

Hi,

I noticed that my approach with skipping by default and enabling deployment only for those artifacts that I want to deploy is a bad decision. Especially with a pomless build, as we have a parent pom, and if that is not available on Maven Central the artifact resolution will not work. ☹

I changed this now to enable the deployment by default (so the parent also gets published) and skip the deployment for artifacts I don't want to publish. I used the hint from Hannes to specify profiles that activate for specific files.

For features I can check if feature.xml exists, for an update site I can check for the category.xml. These are quite generic checks. For the product and the target platform project I have to be more specific, as unfortunately you can not have that check on a directories, only on a file base as far as I found out. And wildcards seem to be not supported for the check. 

Tests are a bit more complicated. First of course the tests should not be skipped so the surefire.properties file is generated in the target folder. The check for target/surefire.properties worked locally, but on Jenkins this somehow fails. I have therefore added marker files in the test projects.

Last but not least I used the check for the file .polyglot.pom.tycho to avoid publishing of the connector poms in a structured environment (features, plugins, tests, releases).

        <profile>
          <id>skip-deploy-eclipse-feature</id>
          <activation>
            <file>
              <exists>feature.xml</exists>
            </file>
          </activation>
          <properties>
            <maven.deploy.skip>true</maven.deploy.skip>
          </properties>
        </profile>
        <profile>
          <id>skip-deploy-eclipse-test</id>
          <activation>
            <file>
              <exists>no_deploy.txt</exists>
            </file>
          </activation>
          <properties>
            <maven.deploy.skip>true</maven.deploy.skip>
          </properties>
        </profile>
        <profile>
          <id>skip-deploy-eclipse-target</id>
          <activation>
            <file>
              <exists>org.eclipse.app4mc.converters.target.target</exists>
            </file>
          </activation>
          <properties>
            <maven.deploy.skip>true</maven.deploy.skip>
          </properties>
        </profile>
        <profile>
          <id>skip-deploy-eclipse-product</id>
          <activation>
            <file>
              <exists>headless.product</exists>
            </file>
          </activation>
          <properties>
            <maven.deploy.skip>true</maven.deploy.skip>
          </properties>
        </profile>
        <profile>
          <id>skip-deploy-eclipse-updatesite</id>
          <activation>
            <file>
              <exists>category.xml</exists>
            </file>
          </activation>
          <properties>
            <maven.deploy.skip>true</maven.deploy.skip>
          </properties>
        </profile>
        <profile>
          <id>skip-deploy-connector-pom</id>
          <activation>
            <file>
              <exists>.polyglot.pom.tycho</exists>
            </file>
          </activation>
          <properties>
            <maven.deploy.skip>true</maven.deploy.skip>
          </properties>
        </profile>

If you have created pom.xml files for the projects that should be published to configure the dependencies in Maven style to be a good Maven Central citizen, the check could be simplified to only skip if no pom.xml is available in a pomless build:

<profile>
  <id>skip-deploy</id>
  <activation>
    <file>
      <missing>pom.xml</missing>
    </file>
  </activation>
  <properties>
    <maven.deploy.skip>true</maven.deploy.skip>
  </properties>
</profile>

I have updated the wiki page with that information and removed the "skip deploy by default" information:
https://wiki.eclipse.org/Tycho:How_to_deploy_to_a_Maven_repository

I hope the information is correct an I am not missing something. If there is some additional information to add, please feel free to add it (or to correct me if something is wrong).

Hope it helps others to be able to also deploy their Eclipse projects on Maven Central.

Mit freundlichen Grüßen / Best regards

 Dirk Fauth

Cross-Domain Computing Solutions, Cross Automotive Platforms - System, Software and Tools Engineering Engineering Software Methods and Tools1 (XC-ECO/ESM1)
Robert Bosch GmbH | Postfach 30 02 40 | 70442 Stuttgart | GERMANY | www.bosch.com
Tel. +49 711 811-57819 | Telefax +49 711 811 | Dirk.Fauth@xxxxxxxxxxxx

Sitz: Stuttgart, Registergericht: Amtsgericht Stuttgart, HRB 14000;
Aufsichtsratsvorsitzender: Franz Fehrenbach; Geschäftsführung: Dr. Volkmar Denner, 
Prof. Dr. Stefan Asenkerschbaumer, Filiz Albrecht, Dr. Michael Bolle, Dr. Christian Fischer, 
Dr. Stefan Hartung, Dr. Markus Heyn, Harald Kröger, Rolf Najork, Uwe Raschke

-----Ursprüngliche Nachricht-----
Von: tycho-dev <tycho-dev-bounces@xxxxxxxxxxx> Im Auftrag von Fauth Dirk (XC-ECO/ESM1) via tycho-dev
Gesendet: Montag, 14. Juni 2021 13:35
An: Tycho developers list <tycho-dev@xxxxxxxxxxx>
Cc: Fauth Dirk (XC-ECO/ESM1) <Dirk.Fauth@xxxxxxxxxxxx>
Betreff: Re: [tycho-dev] [pomless] maven-deploy-plugin configuration

Hi Christoph,

I just tested locally if a dry-run is possible, and it seems to work.

Either you modify the pom.xml and set for example a relative URL in the distributionManagement. Of course you then have to disable the gpg signing in the maven-publish profile.

Or you use the altDeploymentRepository environment variable. Then you don't need to activate the maven-publish profile and should be able to deploy to a local folder for verification.

mvn clean deploy -DskipTests=true -DaltDeploymentRepository=local-repo::default::file:../../repo_test/releases

Mit freundlichen Grüßen / Best regards

 Dirk Fauth

Cross-Domain Computing Solutions, Cross Automotive Platforms - System, Software and Tools Engineering Engineering Software Methods and Tools1 (XC-ECO/ESM1) Robert Bosch GmbH | Postfach 30 02 40 | 70442 Stuttgart | GERMANY | www.bosch.com Tel. +49 711 811-57819 | Telefax +49 711 811 | Dirk.Fauth@xxxxxxxxxxxx

Sitz: Stuttgart, Registergericht: Amtsgericht Stuttgart, HRB 14000;
Aufsichtsratsvorsitzender: Franz Fehrenbach; Geschäftsführung: Dr. Volkmar Denner, Prof. Dr. Stefan Asenkerschbaumer, Filiz Albrecht, Dr. Michael Bolle, Dr. Christian Fischer, Dr. Stefan Hartung, Dr. Markus Heyn, Harald Kröger, Rolf Najork, Uwe Raschke

-----Ursprüngliche Nachricht-----
Von: tycho-dev <tycho-dev-bounces@xxxxxxxxxxx> Im Auftrag von Fauth Dirk (XC-ECO/ESM1) via tycho-dev
Gesendet: Montag, 14. Juni 2021 12:47
An: Tycho developers list <tycho-dev@xxxxxxxxxxx>
Cc: Fauth Dirk (XC-ECO/ESM1) <Dirk.Fauth@xxxxxxxxxxxx>
Betreff: Re: [tycho-dev] [pomless] maven-deploy-plugin configuration

Ah, integration test ... got it. To cover everything I would need some time. I have nothing at hand right now. Maybe I find the time to change my simply RCP cookbook example to pomless Tycho. Although I am not sure if that would extend the idea of a simple integration test. 

I haven't tested yet if there is a way to "dry-run" a mvn deploy. But on stackoverflow there is a short post saying you could simply configure a local folder:

https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fstackoverflow.com%2Fquestions%2F62018354%2Fhow-to-test-maven-deploy&amp;data=04%7C01%7Cdirk.fauth%40de.bosch.com%7C7e29c825ce7047d88f5008d92f287317%7C0ae51e1907c84e4bbb6d648ee58410f4%7C0%7C0%7C637592673050274971%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=Fx9c2htjVQY7XM0kC6Fmh0zRc7JvdRZJWMrqaFSq16o%3D&amp;reserved=0


Mit freundlichen Grüßen / Best regards

 Dirk Fauth

Cross-Domain Computing Solutions, Cross Automotive Platforms - System, Software and Tools Engineering Engineering Software Methods and Tools1 (XC-ECO/ESM1) Robert Bosch GmbH | Postfach 30 02 40 | 70442 Stuttgart | GERMANY | www.bosch.com Tel. +49 711 811-57819 | Telefax +49 711 811 | Dirk.Fauth@xxxxxxxxxxxx

Sitz: Stuttgart, Registergericht: Amtsgericht Stuttgart, HRB 14000;
Aufsichtsratsvorsitzender: Franz Fehrenbach; Geschäftsführung: Dr. Volkmar Denner, Prof. Dr. Stefan Asenkerschbaumer, Filiz Albrecht, Dr. Michael Bolle, Dr. Christian Fischer, Dr. Stefan Hartung, Dr. Markus Heyn, Harald Kröger, Rolf Najork, Uwe Raschke

-----Ursprüngliche Nachricht-----
Von: tycho-dev <tycho-dev-bounces@xxxxxxxxxxx> Im Auftrag von Christoph Läubrich
Gesendet: Montag, 14. Juni 2021 12:03
An: tycho-dev@xxxxxxxxxxx
Betreff: Re: [tycho-dev] [pomless] maven-deploy-plugin configuration

 > Not sure how to provide an itest.

itest = integration test, see [1]. Actually an itest is just a minimal example maven project proving a given functionality.

 > Hope that is sufficient?

Is there some kind of 'dry-run' fro the deploy or will I need a nexus or something to test the deploy?

[1] https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Feclipse%2Ftycho%2Fwiki%23providing-an-integration-test&amp;data=04%7C01%7Cdirk.fauth%40de.bosch.com%7C7e29c825ce7047d88f5008d92f287317%7C0ae51e1907c84e4bbb6d648ee58410f4%7C0%7C0%7C637592673050274971%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=IuBe1BFdq7R0dlfcxyJTu0vNSrs7OabUIpJBDrx8RYk%3D&amp;reserved=0

Am 14.06.21 um 11:20 schrieb Fauth Dirk (XC-ECO/ESM1) via tycho-dev:
> Not sure how to provide an itest. What is an itest? Something specific for Maven Tycho build tests?
> 
> The build I am currently working on is the APP4MC Model Migration build. So you could have a look at that repository:
> 
> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit.
> eclipse.org%2Fc%2Fapp4mc%2Forg.eclipse.app4mc.addon.migration.git%2Flo
> g%2F%3Fh%3Drelease%2F1.1.0&amp;data=04%7C01%7Cdirk.fauth%40de.bosch.co
> m%7C4ffe99737f41493abb5d08d92f1bab11%7C0ae51e1907c84e4bbb6d648ee58410f
> 4%7C0%7C0%7C637592618156435139%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjA
> wMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=M
> 8kD5W6geEOEzZ63isoSLiQck6%2Boptbu8yhv1Mq1Ef0%3D&amp;reserved=0
> 
> In the last 3 commits I was trying to the it working. Today I will restore the pom.xml files, so there will be a new commit. But that should be the easiest way now. With skipping the tests the build also doesn't take too long.
> 
> Hope that is sufficient?
> 
> Mit freundlichen Grüßen / Best regards
> 
>   Dirk Fauth
> 
> Cross-Domain Computing Solutions, Cross Automotive Platforms - System, 
> Software and Tools Engineering Engineering Software Methods and Tools1
> (XC-ECO/ESM1) Robert Bosch GmbH | Postfach 30 02 40 | 70442 Stuttgart
> | GERMANY | www.bosch.com Tel. +49 711 811-57819 | Telefax +49 711 811 
> | Dirk.Fauth@xxxxxxxxxxxx
> 
> Sitz: Stuttgart, Registergericht: Amtsgericht Stuttgart, HRB 14000;
> Aufsichtsratsvorsitzender: Franz Fehrenbach; Geschäftsführung: Dr. 
> Volkmar Denner, Prof. Dr. Stefan Asenkerschbaumer, Filiz Albrecht, Dr. 
> Michael Bolle, Dr. Christian Fischer, Dr. Stefan Hartung, Dr. Markus 
> Heyn, Harald Kröger, Rolf Najork, Uwe Raschke
> 
> -----Ursprüngliche Nachricht-----
> Von: tycho-dev <tycho-dev-bounces@xxxxxxxxxxx> Im Auftrag von 
> Christoph Läubrich
> Gesendet: Montag, 14. Juni 2021 10:35
> An: tycho-dev@xxxxxxxxxxx
> Betreff: Re: [tycho-dev] [pomless] maven-deploy-plugin configuration
> 
> If there is an example that shows the problem I can take a look into this, but as mentioned before I'm not using the deploy-plugin at all currently with tycho so it is a bit hard for me to setup one on myself.
> 
> If you could even provide one in the form of an itest I even could integrate this so we make sure the feature does not break in the future...
> 
> Am 14.06.21 um 10:31 schrieb Fauth Dirk (XC-ECO/ESM1) via tycho-dev:
>> Thanks for the hints. Unfortunately I am currently not able to dig 
>> that deep into the Tycho internals at the moment. ☹
>>
>> For now I will switch back to create pom.xml files for the plugins I 
>> want to deploy. Maybe I find some time to have a look at this in more 
>> detail in the future.
>>
>> I just thought that it would be nice to have a feature like the 
>> build.properties stuff for pomless builds that actually already 
>> exists since 2.0 (and I wasn’t aware of).
>>
>> Thanks again for all the insights and the discussion!
>>
>> Mit freundlichen Grüßen / Best regards
>>
>> *Dirk Fauth*
>>
>> Cross-Domain Computing Solutions, Cross Automotive Platforms - 
>> System, Software and Tools Engineering Engineering Software Methods 
>> and Tools1
>> (XC-ECO/ESM1)
>> Robert Bosch GmbH | Postfach 30 02 40 | 70442 Stuttgart | GERMANY | 
>> www.bosch.com <www.bosch.com> Tel. +49 711 811-57819 | Telefax +49
>> 711
>> 811 | Dirk.Fauth@xxxxxxxxxxxx <mailto:Dirk.Fauth@xxxxxxxxxxxx>
>>
>> Sitz: Stuttgart, Registergericht: Amtsgericht Stuttgart, HRB 14000;
>> Aufsichtsratsvorsitzender: Franz Fehrenbach; Geschäftsführung: Dr.
>> Volkmar Denner,
>> Prof. Dr. Stefan Asenkerschbaumer, Filiz Albrecht, Dr. Michael Bolle, 
>> Dr. Christian Fischer, Dr. Stefan Hartung, Dr. Markus Heyn, Harald 
>> Kröger, Rolf Najork, Uwe Raschke ​
>>
>> *Von:* tycho-dev <tycho-dev-bounces@xxxxxxxxxxx> *Im Auftrag von 
>> *Hannes Wellmann
>> *Gesendet:* Freitag, 11. Juni 2021 09:11
>> *An:* tycho-dev@xxxxxxxxxxx
>> *Betreff:* Re: [tycho-dev] [pomless] maven-deploy-plugin 
>> configuration
>>
>>> The generated_pom.xml of the plugin I want to deploy does not have a properties section. Should this be the case for the build.properties feature?
>>
>> The properties from the build.properties are injected into the 
>> properties of the corresponding Maven-project by the 
>> "org.eclipse.tycho.core.resolver.DefaultTychoResolver" at runtime, so 
>> it is normal that no properties section is generated. This is the 
>> commit from Christoph that introduced the pom.model.property-feauture:
>>
>> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit.
>> eclipse.org%2Fc%2Ftycho%2Forg.eclipse.tycho.git%2Fcommit%2F%3Fid%3Da0
>> 8
>> e80d9a95ef6ac7132f2da5d8edbdeb449819c&amp;data=04%7C01%7Cdirk.fauth%4
>> 0
>> de.bosch.com%7C02da99082cb94a65d87008d92f0f4b0a%7C0ae51e1907c84e4bbb6
>> d
>> 648ee58410f4%7C0%7C0%7C637592564995031398%7CUnknown%7CTWFpbGZsb3d8eyJ
>> W
>> IjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000
>> &
>> amp;sdata=SkamMsjjwVJUXgH%2FnZdqBFdtFLrqf%2FFvZuelKC%2FuVyE%3D&amp;re
>> s
>> erved=0
>> <https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgi
>> t
>> .eclipse.org%2Fc%2Ftycho%2Forg.eclipse.tycho.git%2Fcommit%2F%3Fid%3Da
>> 0
>> 8e80d9a95ef6ac7132f2da5d8edbdeb449819c&amp;data=04%7C01%7Cdirk.fauth%
>> 4
>> 0de.bosch.com%7C02da99082cb94a65d87008d92f0f4b0a%7C0ae51e1907c84e4bbb
>> 6
>> d648ee58410f4%7C0%7C0%7C637592564995031398%7CUnknown%7CTWFpbGZsb3d8ey
>> J
>> WIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C100
>> 0
>> &amp;sdata=SkamMsjjwVJUXgH%2FnZdqBFdtFLrqf%2FFvZuelKC%2FuVyE%3D&amp;r
>> e
>> served=0>
>>
>>> I use Tycho 2.3 in the build and the extensions.
>>> I followed the description of Hannes and double checked that there are not typos. Any hints where to look further?
>>
>> I suggest to debug the build. You can start the build from a tycho 
>> workspace in debug mode and can check if a break-point in
>> DefaultTychoResolver.setBuildProperties(MavenProject) is hit and what 
>> happens (are the properties set?).
>>
>> If the value of the skipDeployment is set as expected into the 
>> projectProperties, I would continue debugging the maven-deploy-plugin 
>> and see if the property ends up there correctly.
>>
>> Usually I don't have the corresponding Mojo in my workspace. 
>> Therefore I just set a break-point at 
>> "org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(MavenS
>> e ssion, MojoExecution)" in the line that contains "mojo.execute();".
>> This is were each mojo is called.
>>
>> In order to get that break-point installed (DefaultBuildPluginManager 
>> is usually also not in my workspace) I start the build in debug-mode, 
>> just pause the main-thread and search up the call-stack and open the 
>> stack-frame of the mentioned location. It is very likely to be within
>> mojo.execute() during a build. Then a break-point can be installed.
>> However the sources are available in my Eclipse out of the box.
>>
>>>  From Christoph Läubrich
>>
>>> I would think this should be the goal, because even if it is 
>>> possible to specify properties in build.properties it's a bit 
>>> cumbersome to do so as it is a thing you have to  think of for each 
>>> and every new created item (what contradicts a bit
>> the nice thing about pomless that is about reducing configuration effort).
>>
>> That's right.
>>
>> Another solution could be, to set the skipDeployment-property in 
>> profiles of the root pom.xml and have one profile for each type of project.
>>
>> The corresponding profile could be activated by using a 
>> <file>-element 
>> (https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fma
>> v
>> en.apache.org%2Fguides%2Fintroduction%2Fintroduction-to-profiles.html
>> &
>> amp;data=04%7C01%7Cdirk.fauth%40de.bosch.com%7C02da99082cb94a65d87008
>> d
>> 92f0f4b0a%7C0ae51e1907c84e4bbb6d648ee58410f4%7C0%7C0%7C63759256499504
>> 1
>> 364%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBT
>> i
>> I6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=uFHg%2BDHzEwLjFtkWl9zbwi%2B
>> 3
>> t9evzGGR%2FhQYMH87FO4%3D&amp;reserved=0
>> <https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fma
>> v
>> en.apache.org%2Fguides%2Fintroduction%2Fintroduction-to-profiles.html
>> &
>> amp;data=04%7C01%7Cdirk.fauth%40de.bosch.com%7C02da99082cb94a65d87008
>> d
>> 92f0f4b0a%7C0ae51e1907c84e4bbb6d648ee58410f4%7C0%7C0%7C63759256499504
>> 1
>> 364%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBT
>> i
>> I6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=uFHg%2BDHzEwLjFtkWl9zbwi%2B
>> 3
>> t9evzGGR%2FhQYMH87FO4%3D&amp;reserved=0>)
>> that requires a file typical for a project of that type.
>>
>> For Eclipse-plugins you could use the following:
>>
>>     <profile>
>>       <id>deploy-eclipse-plugin</id>
>>       <activation>
>>         <file>
>>           <exists>META-INF/MANIFEST.MF</exists>
>>         </file>
>>       </activation>
>>       <properties>
>>         <maven.deploy.skip>false</maven.deploy.skip>
>>       </properties>
>>     </profile>
>>
>> For features you could use <exists>feature.xml</exists>, for 
>> repositories <exists>category.xml</exists> and so on.
>>
>> This way it is automatically detected if the corresponding project is 
>> deployed or not and you don't have to specify it in each project.
>>
>> Additionally you can use the user property maven.deploy.skip which 
>> available for the Maven-Deploy-Plugin since version 2.4 
>> (https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fma
>> v
>> en.apache.org%2Fplugins%2Fmaven-deploy-plugin%2Fdeploy-mojo.html%23sk
>> i
>> p&amp;data=04%7C01%7Cdirk.fauth%40de.bosch.com%7C02da99082cb94a65d870
>> 0
>> 8d92f0f4b0a%7C0ae51e1907c84e4bbb6d648ee58410f4%7C0%7C0%7C637592564995
>> 0
>> 41364%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJ
>> B
>> TiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=WEkklKDcDNj3ktGgqMhwrEUlK
>> k
>> wU3SqbsJbd4xxpfLA%3D&amp;reserved=0
>> <https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmaven.apache.org%2Fplugins%2Fmaven-deploy-plugin%2Fdeploy-mojo.html%23skip&amp;data=04%7C01%7Cdirk.fauth%40de.bosch.com%7C7e29c825ce7047d88f5008d92f287317%7C0ae51e1907c84e4bbb6d648ee58410f4%7C0%7C0%7C637592673050274971%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=B5SH%2FCDyykLLQ8T1Rbbz69DrjjAX2rn7LbHnuhfDihQ%3D&amp;reserved=0>).
>>
>> So you don't have to create an own skipDeployment property. You hast 
>> have to make sure you use the Maven-Deploy-Plugin in version 2.4 or older.
>>
>> Greetings
>>
>> Hannes
>>
>> *Gesendet:* Freitag, 11. Juni 2021 um 07:16 Uhr
>> *Von:* "Fauth Dirk (XC-ECO/ESM1) via tycho-dev" 
>> <tycho-dev@xxxxxxxxxxx <mailto:tycho-dev@xxxxxxxxxxx>>
>> *An:* "Tycho developers list" <tycho-dev@xxxxxxxxxxx 
>> <mailto:tycho-dev@xxxxxxxxxxx>>
>> *Cc:* "Fauth Dirk (XC-ECO/ESM1)" <Dirk.Fauth@xxxxxxxxxxxx 
>> <mailto:Dirk.Fauth@xxxxxxxxxxxx>>
>> *Betreff:* Re: [tycho-dev] [pomless] maven-deploy-plugin 
>> configuration
>>
>> Looking into my local Maven repository I can really see a target file.
>> Not sure if this would be an artefact that would be deployable though.
>> Similar for the feature. But probably I simply do not get the full 
>> picture here yet. You already mentioned that it is kind of 
>> experimental at the moment. 😊
>>
>> I ran the build locally with -Dpolyglot.dump.pom=generated_pom.xml
>>
>> The generated_pom.xml of the plugin I want to deploy does not have a 
>> properties section. Should this be the case for the build.properties 
>> feature?
>>
>> I use Tycho 2.3 in the build and the extensions.
>>
>> I followed the description of Hannes and double checked that there 
>> are not typos. Any hints where to look further?
>>
>> Mit freundlichen Grüßen / Best regards
>>
>> Dirk Fauth
>>
>> Cross-Domain Computing Solutions, Cross Automotive Platforms - 
>> System, Software and Tools Engineering Engineering Software Methods 
>> and Tools1
>> (XC-ECO/ESM1)
>> Robert Bosch GmbH | Postfach 30 02 40 | 70442 Stuttgart | GERMANY | 
>> www.bosch.com <http://www.bosch.com> Tel. +49 711 811-57819 | Telefax
>> +49 711 811 | Dirk.Fauth@xxxxxxxxxxxx 
>> +<mailto:Dirk.Fauth@xxxxxxxxxxxx>
>>
>> Sitz: Stuttgart, Registergericht: Amtsgericht Stuttgart, HRB 14000;
>> Aufsichtsratsvorsitzender: Franz Fehrenbach; Geschäftsführung: Dr.
>> Volkmar Denner,
>> Prof. Dr. Stefan Asenkerschbaumer, Filiz Albrecht, Dr. Michael Bolle, 
>> Dr. Christian Fischer, Dr. Stefan Hartung, Dr. Markus Heyn, Harald 
>> Kröger, Rolf Najork, Uwe Raschke
>>
>> -----Ursprüngliche Nachricht-----
>> Von: tycho-dev <tycho-dev-bounces@xxxxxxxxxxx 
>> <mailto:tycho-dev-bounces@xxxxxxxxxxx>> Im Auftrag von Christoph 
>> Läubrich
>> Gesendet: Donnerstag, 10. Juni 2021 13:17
>> An: Fauth Dirk (XC-ECO/ESM1) via tycho-dev <tycho-dev@xxxxxxxxxxx 
>> <mailto:tycho-dev@xxxxxxxxxxx>>
>> Betreff: Re: [tycho-dev] [pomless] maven-deploy-plugin configuration
>>
>>> But targets and features are only stuff that makes sense in a p2 > 
>>> environment, you typically would not consume a target or a feature > 
>>> via plain Maven
>>
>> You can consume deployed target files in m2e-pde/Tycho directly, 
>> tycho snapshot contains a new mojo that allows to create/deploy a p2 
>> site to maven as well and then consume all artifacts from maven 
>> directly without dedicated deployment (that's a bit experimental though atm).
>>
>>> improving the maven-deploy-plugin would be also an option
>>
>> I would think this should be the goal, because even if it is possible 
>> to specify properties in build.properties it's a bit cumbersome to do 
>> so as it is a thing you have to think of for each and every new 
>> created item (what contradicts a bit the nice thing about pomless 
>> that is about reducing configuration effort).
>>
>>> But do you know why the property replacement is not working?
>>
>> Most likely because a perquisite is not meet, eg you have a typo or 
>> do not use the most recent tycho version in the extensions.xml (!)
>>
>>> any hint how I could provide more information?
>>
>> You can output the generated pom.xml with the option
>>
>> -Dpolyglot.dump.pom=generated_pom.xml
>>
>> to better see whats going on.
>>
>>
>>
>> Am 10.06.21 um 13:04 schrieb Fauth Dirk (XC-ECO/ESM1) via tycho-dev:
>>> But targets and features are only stuff that makes sense in a p2 environment, you typically would not consume a target or a feature via plain Maven, as the plain Maven usage doesn't make sense. At least from my point of view. Maybe I oversee something.
>>>
>>> Well, improving the maven-deploy-plugin would be also an option. But do you know why the property replacement is not working? I mean, from the description it should do exactly what I was looking for. Why does it not work here? Any idea? Or any hint how I  could provide more information?
>>>
>>> Mit freundlichen Grüßen / Best regards
>>>
>>> Dirk Fauth
>>>
>>> Cross-Domain Computing Solutions, Cross Automotive Platforms - 
>>> System, Software and Tools Engineering Engineering Software Methods 
>>> and Tools1
>>> (XC-ECO/ESM1) Robert Bosch GmbH | Postfach 30 02 40 | 70442 
>>> Stuttgart
>>> | GERMANY | www.bosch.com <http://www.bosch.com> Tel. +49 711
>>> | 811-57819 | Telefax
>> +49 711 811
>>> | Dirk.Fauth@xxxxxxxxxxxx <mailto:Dirk.Fauth@xxxxxxxxxxxx>
>>>
>>> Sitz: Stuttgart, Registergericht: Amtsgericht Stuttgart, HRB 14000;
>>> Aufsichtsratsvorsitzender: Franz Fehrenbach; Geschäftsführung: Dr.
>>> Volkmar Denner, Prof. Dr. Stefan Asenkerschbaumer, Filiz Albrecht, Dr.
>>> Michael Bolle, Dr. Christian Fischer, Dr. Stefan Hartung, Dr. Markus 
>>> Heyn, Harald Kröger, Rolf Najork, Uwe Raschke
>>>
>>> -----Ursprüngliche Nachricht-----
>>> Von: tycho-dev <tycho-dev-bounces@xxxxxxxxxxx 
>>> <mailto:tycho-dev-bounces@xxxxxxxxxxx>> Im
>> Auftrag von
>>> Christoph Läubrich
>>> Gesendet: Donnerstag, 10. Juni 2021 12:46
>>> An: tycho-dev@xxxxxxxxxxx <mailto:tycho-dev@xxxxxxxxxxx>
>>> Betreff: Re: [tycho-dev] [pomless] maven-deploy-plugin configuration
>>>
>>> Targets can be useful and features as well. So I think its a bit hard to decide.
>>>
>>> maybe I overseen something but the maven-deploy-plugin seems not be very configurable, so maybe it would be better to try get the deploy plugin more flexible?
>>>
>>> e.g. instead of an generic <skip> i would find something to specify 
>>> include/exclude patterns much more convenient, so one can control at 
>>> the master-pom something like
>>>
>>> <build>
>>> <plugins>
>>> <plugin>
>>> <artifactId>maven-deploy-plugin</artifactId>
>>> <configuration>
>>> <exclude>**/features/*.jar</exclude>
>>> </configuration>
>>> </plugin>
>>> </plugins>
>>> </build>
>>>
>>>
>>>
>>> Am 10.06.21 um 12:36 schrieb Fauth Dirk (XC-ECO/ESM1) via tycho-dev:
>>>> Hi,
>>>>
>>>> This is exactly what I asked for. Unfortunately it does not work. It is skipping the deployment for all projects, even those where I have added the configuration in the build.properties.
>>>>
>>>> I tested it inside the pluginManagement, the build section in a profile and the general build section of the parent pom. In none scenario the property seems to be replaced with false.
>>>>
>>>> Any ideas on what could be wrong or missing?
>>>>
>>>> @Christoph
>>>> I am also not that familiar with the Maven deploy stuff. I just read some docs about it and found that you can skip artifact deployment this way.
>>>> Actually the default is false, so maybe a better first step would 
>>>> be to at least add the skip flag for the connector poms automatically.
>>>> Maybe even for the tests, as tests are nothing to be considered to 
>>>> be deployed on Maven Central. Same for the target,  product and 
>>>> probably the parent pom? Event features seem to doesn't
>> make sense to be deployed on Maven Central. Setting skip to true on 
>> those generated pom.xml files might be worth to have a look at.
>>>>
>>>> Mit freundlichen Grüßen / Best regards
>>>>
>>>> Dirk Fauth
>>>>
>>>> Cross-Domain Computing Solutions, Cross Automotive Platforms - 
>>>> System, Software and Tools Engineering Engineering Software Methods 
>>>> and Tools1
>>>> (XC-ECO/ESM1) Robert Bosch GmbH | Postfach 30 02 40 | 70442 
>>>> Stuttgart
>>>> | GERMANY | www.bosch.com <http://www.bosch.com> Tel. +49 711
>>>> | 811-57819 | Telefax
>> +49 711
>>>> | 811 Dirk.Fauth@xxxxxxxxxxxx <mailto:Dirk.Fauth@xxxxxxxxxxxx>
>>>>
>>>> Sitz: Stuttgart, Registergericht: Amtsgericht Stuttgart, HRB 14000;
>>>> Aufsichtsratsvorsitzender: Franz Fehrenbach; Geschäftsführung: Dr.
>>>> Volkmar Denner, Prof. Dr. Stefan Asenkerschbaumer, Filiz Albrecht, Dr.
>>>> Michael Bolle, Dr. Christian Fischer, Dr. Stefan Hartung, Dr. 
>>>> Markus Heyn, Harald Kröger, Rolf Najork, Uwe Raschke
>>>>
>>>> -----Ursprüngliche Nachricht-----
>>>> Von: tycho-dev <tycho-dev-bounces@xxxxxxxxxxx 
>>>> <mailto:tycho-dev-bounces@xxxxxxxxxxx>> Im
>> Auftrag von
>>>> Christoph Läubrich
>>>> Gesendet: Donnerstag, 10. Juni 2021 09:01
>>>> An: tycho-dev@xxxxxxxxxxx <mailto:tycho-dev@xxxxxxxxxxx>
>>>> Betreff: Re: [tycho-dev] [pomless] maven-deploy-plugin 
>>>> configuration
>>>>
>>>> @Hannes I'm glad that this feature is found useful by others :-)
>>>>
>>>> @Dirk: First of all MANY thanks for describing the workflow! I'm not very familiar with the maven-deploy-plugin but would it help if pomless would generate the following in the "non-artifact-poms":
>>>>
>>>> <build>
>>>> <plugins>
>>>> <plugin>
>>>> <artifactId>maven-deploy-plugin</artifactId>
>>>> <configuration>
>>>> <skip>false</skip>
>>>> </configuration>
>>>> </plugin>
>>>> </plugins>
>>>> </build>
>>>>
>>>> or can tycho-pomless do anything else to tell the maven-deploy-plugin that some parts are only intermediates?
>>>>
>>>> Am 10.06.21 um 08:33 schrieb Hannes Wellmann:
>>>>> Hello,
>>>>>
>>>>> since Tycho 2.0 it is possible to define (pom model) properties in 
>>>>> the build.properties of an Eclipse plug-in that are used by Maven:
>>>>> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2F
>>>>> w
>>>>> i
>> <https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwi
>> >
>>>>> k
>>>>> i
>>>>> .eclipse.org%2FTycho%2FRelease_Notes%2F2.0%23Define_Maven_Project_
>>>>> p
>>>>> r
>>>>> o
>>>>> p
>>>>> erties_in_build.properties&amp;data=04%7C01%7Cdirk.fauth%40de.bosch.
>>>>> c
>>>>> o
>>>>> m%7C05e2b8e71e3a445db0a508d92bdd9526%7C0ae51e1907c84e4bbb6d648ee58
>>>>> 4
>>>>> 1
>>>>> 0
>>>>> f
>>>>> 4%7C0%7C0%7C637589052951766653%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4
>>>>> w
>>>>> L
>>>>> j
>>>>> A
>>>>> wMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sda
>>>>> t
>>>>> a
>>>>> =
>>>>> y
>>>>> 40LLdLrzCkc6o9y67jJIas2yu07gZwnDmsjhvUcqXY%3D&amp;reserved=0
>>>>>
>>>>> So for your case the pom could have elements like the following:
>>>>>
>>>>> <properties>
>>>>>   <skipDeployment>true</skipDeployment>  <!-- skip the publishing 
>>>>> to Maven by default --> </properties>
>>>>>
>>>>> .
>>>>> .
>>>>> .
>>>>> <plugin>
>>>>>    <groupId>org.apache.maven.plugins</groupId>
>>>>>    <artifactId>maven-deploy-plugin</artifactId>
>>>>>    <version>2.8.2</version>
>>>>>    <configuration>
>>>>>      <skip>${skipDeployment}</skip>
>>>>>    </configuration>
>>>>> </plugin>
>>>>>
>>>>>
>>>>> The build.properties of the plugins you want to deploy should have 
>>>>> an entry like this:
>>>>>
>>>>> pom.model.property.skipDeployment=false
>>>>>
>>>>>
>>>>> This feature of Tycho is a bit hidden and not advertised, but I 
>>>>> find it very handy for situations like yours.
>>>>>
>>>>>
>>>>>
>>>>> Greetings
>>>>>
>>>>> Hannes Wellmann
>>>>> *Gesendet:* Donnerstag, 10. Juni 2021 um 07:05 Uhr
>>>>> *Von:* "Fauth Dirk (XC-ECO/ESM1) via tycho-dev"
>>>>> <tycho-dev@xxxxxxxxxxx <mailto:tycho-dev@xxxxxxxxxxx>>
>>>>> *An:* "Tycho developers list" <tycho-dev@xxxxxxxxxxx 
>>>>> <mailto:tycho-dev@xxxxxxxxxxx>>
>>>>> *Cc:* "Fauth Dirk (XC-ECO/ESM1)" <Dirk.Fauth@xxxxxxxxxxxx 
>>>>> <mailto:Dirk.Fauth@xxxxxxxxxxxx>>
>>>>> *Betreff:* [tycho-dev] [pomless] maven-deploy-plugin configuration
>>>>>
>>>>> Hi all,
>>>>>
>>>>> I have written this wiki page to describe the process on how to 
>>>>> deploy on Maven Central on the Eclipse infra with Tycho:
>>>>>
>>>>> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2F
>>>>> w
>>>>> i
>> <https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwi
>> >
>>>>> k
>>>>> i
>>>>> .eclipse.org%2FTycho%3AHow_to_deploy_to_a_Maven_repository&amp;dat
>>>>> a
>>>>> =
>>>>> 0
>>>>> 4
>>>>> %7C01%7Cdirk.fauth%40de.bosch.com%7C05e2b8e71e3a445db0a508d92bdd95
>>>>> 2
>>>>> 6
>>>>> %
>>>>> 7
>>>>> C0ae51e1907c84e4bbb6d648ee58410f4%7C0%7C0%7C637589052951766653%7CU
>>>>> n
>>>>> k
>>>>> n
>>>>> o
>>>>> wn%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1ha
>>>>> W
>>>>> w
>>>>> i
>>>>> L
>>>>> CJXVCI6Mn0%3D%7C1000&amp;sdata=IKVEjDoJIJmNMH00uphBbzfdADQ11W6flq1
>>>>> N
>>>>> H
>>>>> o
>>>>> a
>>>>> %2FQlQ%3D&amp;reserved=0
>>>>> <https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2
>>>>> F
>>>>> w
>> <https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fw>
>>>>> i
>>>>> k
>>>>> i.eclipse.org%2FTycho%3AHow_to_deploy_to_a_Maven_repository&amp;da
>>>>> t
>>>>> a
>>>>> =
>>>>> 0
>>>>> 4%7C01%7Cdirk.fauth%40de.bosch.com%7C05e2b8e71e3a445db0a508d92bdd9
>>>>> 5
>>>>> 2
>>>>> 6
>>>>> %
>>>>> 7C0ae51e1907c84e4bbb6d648ee58410f4%7C0%7C0%7C637589052951766653%7C
>>>>> U
>>>>> n
>>>>> k
>>>>> n
>>>>> own%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1h
>>>>> a
>>>>> W
>>>>> w
>>>>> i
>>>>> LCJXVCI6Mn0%3D%7C1000&amp;sdata=IKVEjDoJIJmNMH00uphBbzfdADQ11W6flq
>>>>> 1
>>>>> N
>>>>> H
>>>>> o
>>>>> a%2FQlQ%3D&amp;reserved=0>
>>>>>
>>>>> I adapted this on one project already successfully and now adapt 
>>>>> it on other projects. One thing that is really bothering me is the 
>>>>> handling of the maven-deploy-plugin. Without additional 
>>>>> configuration, all artefacts are deployed. In a pomless Tycho 
>>>>> build this means that a lot of artefacts are deployed that 
>>>>> actually should not be in Maven Central, like
>>>>>
>>>>> * features
>>>>> * tests
>>>>> * parent
>>>>> * connector poms
>>>>>
>>>>> You can see this for some Eclipse projects on Maven Central already.
>>>>>
>>>>> I therefore decided to globally skip the deployment by adding this 
>>>>> to the parent pom:
>>>>>
>>>>> *<plugin>*
>>>>>
>>>>> *<groupId>*org.apache.maven.plugins*</groupId>*
>>>>>
>>>>> *<artifactId>*maven-deploy-plugin*</artifactId>*
>>>>>
>>>>> *<version>*2.8.2*</version>*
>>>>>
>>>>> /<!-- skip the publishing to Maven by default -->/
>>>>>
>>>>> *<configuration>*
>>>>>
>>>>> *<skip>*true*</skip>*
>>>>>
>>>>> *</configuration>*
>>>>>
>>>>> *</plugin>*
>>>>>
>>>>> But then you of course need to enable the deployment on those 
>>>>> projects that should be deployed by adding this to the project pom:
>>>>>
>>>>> *<build**>*
>>>>>
>>>>> *<plugins**>*
>>>>>
>>>>> /<!-- publish this artifact to Maven repositories -->/
>>>>>
>>>>> *<plugin**>*
>>>>>
>>>>> *<artifactId**>*maven-deploy-plugin*</artifactId**>*
>>>>>
>>>>> *<configuration**>*
>>>>>
>>>>> *<skip**>*false*</skip**>*
>>>>>
>>>>> *</configuration**>*
>>>>>
>>>>> *</plugin**>*
>>>>>
>>>>> *</plugins**>*
>>>>>
>>>>> *</build**>*
>>>>>
>>>>> For a pomless build this has the negative side effect that you 
>>>>> actually need to introduce again pom’s for the projects you want 
>>>>> to publish on Maven Central.
>>>>>
>>>>> Would it be somehow possible to extend (pomless) Tycho to set that 
>>>>> configuration for example via build.properties? Not sure if and 
>>>>> how this could be done, therefore the question here to get some input.
>>>>>
>>>>> Mit freundlichen Grüßen / Best regards
>>>>>
>>>>> *Dirk Fauth*
>>>>>
>>>>> Cross-Domain Computing Solutions, Cross Automotive Platforms - 
>>>>> System, Software and Tools Engineering Engineering Software 
>>>>> Methods and Tools1
>>>>> (XC-ECO/ESM1)
>>>>> Robert Bosch GmbH | Postfach 30 02 40 | 70442 Stuttgart | GERMANY
>>>>> | www.bosch.com <http://www.bosch.com> <http://www.bosch.com
>> <http://www.bosch.com>> Tel. +49 711 811-57819 |
>>>>> Telefax
>>>>> +49 711 811 | Dirk.Fauth@xxxxxxxxxxxx 
>>>>> +<mailto:Dirk.Fauth@xxxxxxxxxxxx> <mailto:Dirk.Fauth@xxxxxxxxxxxx 
>>>>> +<mailto:Dirk.Fauth@xxxxxxxxxxxx>>
>>>>>
>>>>> Sitz: Stuttgart, Registergericht: Amtsgericht Stuttgart, HRB 
>>>>> 14000;
>>>>> Aufsichtsratsvorsitzender: Franz Fehrenbach; Geschäftsführung: Dr.
>>>>> Volkmar Denner,
>>>>> Prof. Dr. Stefan Asenkerschbaumer, Filiz Albrecht, Dr. Michael 
>>>>> Bolle, Dr. Christian Fischer, Dr. Stefan Hartung, Dr. Markus Heyn, 
>>>>> Harald Kröger, Rolf Najork, Uwe Raschke ​
>>>>>
>>>>> _______________________________________________ tycho-dev mailing 
>>>>> list tycho-dev@xxxxxxxxxxx <mailto:tycho-dev@xxxxxxxxxxx> To 
>>>>> unsubscribe from
>> this list, visit
>>>>> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2F
>>>>> w
>>>>> ww
>> <https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww>.
>>>>> eclipse.org%2Fmailman%2Flistinfo%2Ftycho-dev&amp;data=04%7C01%7Cdirk.
>>>>> f
>>>>> auth%40de.bosch.com%7C05e2b8e71e3a445db0a508d92bdd9526%7C0ae51e190
>>>>> 7
>>>>> c
>>>>> 8
>>>>> 4
>>>>> e4bbb6d648ee58410f4%7C0%7C0%7C637589052951766653%7CUnknown%7CTWFpb
>>>>> G
>>>>> Z
>>>>> s
>>>>> b
>>>>> 3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0
>>>>> %
>>>>> 3
>>>>> D
>>>>> %
>>>>> 7C1000&amp;sdata=ljzdAdE39ghAZVeovNa8XGA5vb%2F6xsPkYSMr4VBSjBU%3D&
>>>>> a
>>>>> m
>>>>> p
>>>>> ;
>>>>> reserved=0
>>>>> <https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2
>>>>> F
>>>>> w
>> <https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fw>
>>>>> w
>>>>> w
>>>>> .eclipse.org%2Fmailman%2Flistinfo%2Ftycho-dev&amp;data=04%7C01%7Cdirk.
>>>>> fauth%40de.bosch.com%7C05e2b8e71e3a445db0a508d92bdd9526%7C0ae51e19
>>>>> 0
>>>>> 7
>>>>> c
>>>>> 8
>>>>> 4e4bbb6d648ee58410f4%7C0%7C0%7C637589052951766653%7CUnknown%7CTWFp
>>>>> b
>>>>> G
>>>>> Z
>>>>> s
>>>>> b3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn
>>>>> 0
>>>>> %
>>>>> 3
>>>>> D
>>>>> %7C1000&amp;sdata=ljzdAdE39ghAZVeovNa8XGA5vb%2F6xsPkYSMr4VBSjBU%3D
>>>>> &
>>>>> a
>>>>> m
>>>>> p
>>>>> ;reserved=0>
>>>>>
>>>>> _______________________________________________
>>>>> tycho-dev mailing list
>>>>> tycho-dev@xxxxxxxxxxx <mailto:tycho-dev@xxxxxxxxxxx> To 
>>>>> unsubscribe from this list, visit 
>>>>> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2F
>>>>> w
>>>>> ww
>> <https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww>.
>>>>> eclipse.org%2Fmailman%2Flistinfo%2Ftycho-dev&amp;data=04%7C01%7Cdirk.
>>>>> f
>>>>> auth%40de.bosch.com%7C05e2b8e71e3a445db0a508d92bdd9526%7C0ae51e190
>>>>> 7
>>>>> c
>>>>> 8
>>>>> 4
>>>>> e4bbb6d648ee58410f4%7C0%7C0%7C637589052951766653%7CUnknown%7CTWFpb
>>>>> G
>>>>> Z
>>>>> s
>>>>> b
>>>>> 3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0
>>>>> %
>>>>> 3
>>>>> D
>>>>> %
>>>>> 7C1000&amp;sdata=ljzdAdE39ghAZVeovNa8XGA5vb%2F6xsPkYSMr4VBSjBU%3D&
>>>>> a
>>>>> m
>>>>> p
>>>>> ;
>>>>> reserved=0
>>>>>
>>>> _______________________________________________
>>>> tycho-dev mailing list
>>>> tycho-dev@xxxxxxxxxxx <mailto:tycho-dev@xxxxxxxxxxx> To unsubscribe 
>>>> from this list, visit 
>>>> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fw
>>>> w
>>>> w
>> <https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww>.
>>>> eclipse.org%2Fmailman%2Flistinfo%2Ftycho-dev&amp;data=04%7C01%7Cdirk.
>>>> f
>>>> auth%40de.bosch.com%7Cd9bb91d2d13347fe468408d92bfd05f8%7C0ae51e1907
>>>> c
>>>> 8
>>>> 4
>>>> e4bbb6d648ee58410f4%7C0%7C0%7C637589187988548728%7CUnknown%7CTWFpbG
>>>> Z
>>>> s
>>>> b
>>>> 3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%
>>>> 3
>>>> D
>>>> %
>>>> 7C1000&amp;sdata=2hp4dawZaiOWX5cNoARfZ%2FF7w1mgAADghG6cd17Mqhw%3D&a
>>>> m
>>>> p
>>>> ;
>>>> reserved=0 _______________________________________________
>>>> tycho-dev mailing list
>>>> tycho-dev@xxxxxxxxxxx <mailto:tycho-dev@xxxxxxxxxxx> To unsubscribe 
>>>> from this list, visit 
>>>> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fw
>>>> w
>>>> w
>> <https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww>.
>>>> eclipse.org%2Fmailman%2Flistinfo%2Ftycho-dev&amp;data=04%7C01%7Cdirk.
>>>> f
>>>> auth%40de.bosch.com%7Cd9bb91d2d13347fe468408d92bfd05f8%7C0ae51e1907
>>>> c
>>>> 8
>>>> 4
>>>> e4bbb6d648ee58410f4%7C0%7C0%7C637589187988558699%7CUnknown%7CTWFpbG
>>>> Z
>>>> s
>>>> b
>>>> 3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%
>>>> 3
>>>> D
>>>> %
>>>> 7C1000&amp;sdata=LsRYwWp10fQSnUgHSqiay8BWO0WJpTvmLgaW86xo1ls%3D&amp
>>>> ;
>>>> r
>>>> e
>>>> served=0
>>>>
>>> _______________________________________________
>>> tycho-dev mailing list
>>> tycho-dev@xxxxxxxxxxx <mailto:tycho-dev@xxxxxxxxxxx> To unsubscribe 
>>> from this list, visit 
>>> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fww
>>> w
>> <https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww>.
>>> eclipse.org%2Fmailman%2Flistinfo%2Ftycho-dev&amp;data=04%7C01%7Cdirk.
>>> f
>>> auth%40de.bosch.com%7C9ce64a20654a4d66a56608d92c0138a0%7C0ae51e1907c
>>> 8
>>> 4
>>> e4bbb6d648ee58410f4%7C0%7C0%7C637589206017149929%7CUnknown%7CTWFpbGZ
>>> s
>>> b
>>> 3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3
>>> D
>>> %
>>> 7C1000&amp;sdata=gMhgfZw%2Bf36crymBysL24cyi7RP1Pms8ueBTsOK5a%2Bw%3D&
>>> a
>>> m
>>> p;reserved=0 _______________________________________________
>>> tycho-dev mailing list
>>> tycho-dev@xxxxxxxxxxx <mailto:tycho-dev@xxxxxxxxxxx> To unsubscribe 
>>> from this list, visit 
>>> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fww
>>> w
>> <https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww>.
>>> eclipse.org%2Fmailman%2Flistinfo%2Ftycho-dev&amp;data=04%7C01%7Cdirk.
>>> f
>>> auth%40de.bosch.com%7C9ce64a20654a4d66a56608d92c0138a0%7C0ae51e1907c
>>> 8
>>> 4
>>> e4bbb6d648ee58410f4%7C0%7C0%7C637589206017149929%7CUnknown%7CTWFpbGZ
>>> s
>>> b
>>> 3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3
>>> D
>>> %
>>> 7C1000&amp;sdata=gMhgfZw%2Bf36crymBysL24cyi7RP1Pms8ueBTsOK5a%2Bw%3D&
>>> a
>>> m
>>> p;reserved=0
>>>
>> _______________________________________________
>> tycho-dev mailing list
>> tycho-dev@xxxxxxxxxxx <mailto:tycho-dev@xxxxxxxxxxx> To unsubscribe 
>> from this list, visit 
>> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.
>> eclipse.org%2Fmailman%2Flistinfo%2Ftycho-dev&amp;data=04%7C01%7Cdirk.
>> f
>> auth%40de.bosch.com%7C02da99082cb94a65d87008d92f0f4b0a%7C0ae51e1907c8
>> 4
>> e4bbb6d648ee58410f4%7C0%7C0%7C637592564995041364%7CUnknown%7CTWFpbGZs
>> b
>> 3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D
>> %
>> 7C1000&amp;sdata=ZZoU3bJYBRrJKYhsZuKA7J642SxRrSVWdJApa5Q7xNo%3D&amp;r
>> e
>> served=0
>> <https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fww
>> w
>> .eclipse.org%2Fmailman%2Flistinfo%2Ftycho-dev&amp;data=04%7C01%7Cdirk.
>> fauth%40de.bosch.com%7C02da99082cb94a65d87008d92f0f4b0a%7C0ae51e1907c
>> 8
>> 4e4bbb6d648ee58410f4%7C0%7C0%7C637592564995041364%7CUnknown%7CTWFpbGZ
>> s
>> b3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3
>> D
>> %7C1000&amp;sdata=ZZoU3bJYBRrJKYhsZuKA7J642SxRrSVWdJApa5Q7xNo%3D&amp;
>> r eserved=0> _______________________________________________
>> tycho-dev mailing list
>> tycho-dev@xxxxxxxxxxx <mailto:tycho-dev@xxxxxxxxxxx> To unsubscribe 
>> from this list, visit 
>> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.
>> eclipse.org%2Fmailman%2Flistinfo%2Ftycho-dev&amp;data=04%7C01%7Cdirk.
>> f
>> auth%40de.bosch.com%7C02da99082cb94a65d87008d92f0f4b0a%7C0ae51e1907c8
>> 4
>> e4bbb6d648ee58410f4%7C0%7C0%7C637592564995041364%7CUnknown%7CTWFpbGZs
>> b
>> 3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D
>> %
>> 7C1000&amp;sdata=ZZoU3bJYBRrJKYhsZuKA7J642SxRrSVWdJApa5Q7xNo%3D&amp;r
>> e
>> served=0
>> <https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fww
>> w
>> .eclipse.org%2Fmailman%2Flistinfo%2Ftycho-dev&amp;data=04%7C01%7Cdirk.
>> fauth%40de.bosch.com%7C02da99082cb94a65d87008d92f0f4b0a%7C0ae51e1907c
>> 8
>> 4e4bbb6d648ee58410f4%7C0%7C0%7C637592564995041364%7CUnknown%7CTWFpbGZ
>> s
>> b3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3
>> D
>> %7C1000&amp;sdata=ZZoU3bJYBRrJKYhsZuKA7J642SxRrSVWdJApa5Q7xNo%3D&amp;
>> r
>> eserved=0>
>>
>>
>> _______________________________________________
>> tycho-dev mailing list
>> tycho-dev@xxxxxxxxxxx
>> To unsubscribe from this list, visit
>> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.
>> eclipse.org%2Fmailman%2Flistinfo%2Ftycho-dev&amp;data=04%7C01%7Cdirk.
>> f
>> auth%40de.bosch.com%7C02da99082cb94a65d87008d92f0f4b0a%7C0ae51e1907c8
>> 4
>> e4bbb6d648ee58410f4%7C0%7C0%7C637592564995041364%7CUnknown%7CTWFpbGZs
>> b
>> 3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D
>> %
>> 7C1000&amp;sdata=ZZoU3bJYBRrJKYhsZuKA7J642SxRrSVWdJApa5Q7xNo%3D&amp;r
>> e
>> served=0
>>
> _______________________________________________
> tycho-dev mailing list
> tycho-dev@xxxxxxxxxxx
> To unsubscribe from this list, visit
> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.
> eclipse.org%2Fmailman%2Flistinfo%2Ftycho-dev&amp;data=04%7C01%7Cdirk.f
> auth%40de.bosch.com%7C4ffe99737f41493abb5d08d92f1bab11%7C0ae51e1907c84
> e4bbb6d648ee58410f4%7C0%7C0%7C637592618156445098%7CUnknown%7CTWFpbGZsb
> 3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%
> 7C1000&amp;sdata=ikzfLEzfbyacnX4dDUXyDHQCeZ58q7QoEZtx%2BGRPvdk%3D&amp;
> reserved=0 _______________________________________________
> tycho-dev mailing list
> tycho-dev@xxxxxxxxxxx
> To unsubscribe from this list, visit
> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.
> eclipse.org%2Fmailman%2Flistinfo%2Ftycho-dev&amp;data=04%7C01%7Cdirk.f
> auth%40de.bosch.com%7C4ffe99737f41493abb5d08d92f1bab11%7C0ae51e1907c84
> e4bbb6d648ee58410f4%7C0%7C0%7C637592618156445098%7CUnknown%7CTWFpbGZsb
> 3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%
> 7C1000&amp;sdata=ikzfLEzfbyacnX4dDUXyDHQCeZ58q7QoEZtx%2BGRPvdk%3D&amp;
> reserved=0
> 
_______________________________________________
tycho-dev mailing list
tycho-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.eclipse.org%2Fmailman%2Flistinfo%2Ftycho-dev&amp;data=04%7C01%7Cdirk.fauth%40de.bosch.com%7C7e29c825ce7047d88f5008d92f287317%7C0ae51e1907c84e4bbb6d648ee58410f4%7C0%7C0%7C637592673050274971%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=0kxE9Qe%2FBKTxAsw8q5xcirHFzgsPFSDnYjoo2w7JhJg%3D&amp;reserved=0
_______________________________________________
tycho-dev mailing list
tycho-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.eclipse.org%2Fmailman%2Flistinfo%2Ftycho-dev&amp;data=04%7C01%7Cdirk.fauth%40de.bosch.com%7C7e29c825ce7047d88f5008d92f287317%7C0ae51e1907c84e4bbb6d648ee58410f4%7C0%7C0%7C637592673050284921%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=u9OOWYqYJFoe8I98APUCa5Zc6rge%2BQQRbiJpwnesExo%3D&amp;reserved=0
_______________________________________________
tycho-dev mailing list
tycho-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.eclipse.org%2Fmailman%2Flistinfo%2Ftycho-dev&amp;data=04%7C01%7Cdirk.fauth%40de.bosch.com%7C7e29c825ce7047d88f5008d92f287317%7C0ae51e1907c84e4bbb6d648ee58410f4%7C0%7C0%7C637592673050284921%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=u9OOWYqYJFoe8I98APUCa5Zc6rge%2BQQRbiJpwnesExo%3D&amp;reserved=0