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%3Da08
e80d9a95ef6ac7132f2da5d8edbdeb449819c&data=04%7C01%7Cdirk.fauth%40
de.bosch.com%7C02da99082cb94a65d87008d92f0f4b0a%7C0ae51e1907c84e4bbb6d
648ee58410f4%7C0%7C0%7C637592564995031398%7CUnknown%7CTWFpbGZsb3d8eyJW
IjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&
amp;sdata=SkamMsjjwVJUXgH%2FnZdqBFdtFLrqf%2FFvZuelKC%2FuVyE%3D&res
erved=0
<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit
.eclipse.org%2Fc%2Ftycho%2Forg.eclipse.tycho.git%2Fcommit%2F%3Fid%3Da0
8e80d9a95ef6ac7132f2da5d8edbdeb449819c&data=04%7C01%7Cdirk.fauth%4
0de.bosch.com%7C02da99082cb94a65d87008d92f0f4b0a%7C0ae51e1907c84e4bbb6
d648ee58410f4%7C0%7C0%7C637592564995031398%7CUnknown%7CTWFpbGZsb3d8eyJ
WIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000
&sdata=SkamMsjjwVJUXgH%2FnZdqBFdtFLrqf%2FFvZuelKC%2FuVyE%3D&re
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(MavenSe
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%2Fmav
en.apache.org%2Fguides%2Fintroduction%2Fintroduction-to-profiles.html&
amp;data=04%7C01%7Cdirk.fauth%40de.bosch.com%7C02da99082cb94a65d87008d
92f0f4b0a%7C0ae51e1907c84e4bbb6d648ee58410f4%7C0%7C0%7C637592564995041
364%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTi
I6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=uFHg%2BDHzEwLjFtkWl9zbwi%2B3
t9evzGGR%2FhQYMH87FO4%3D&reserved=0
<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmav
en.apache.org%2Fguides%2Fintroduction%2Fintroduction-to-profiles.html&
amp;data=04%7C01%7Cdirk.fauth%40de.bosch.com%7C02da99082cb94a65d87008d
92f0f4b0a%7C0ae51e1907c84e4bbb6d648ee58410f4%7C0%7C0%7C637592564995041
364%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTi
I6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=uFHg%2BDHzEwLjFtkWl9zbwi%2B3
t9evzGGR%2FhQYMH87FO4%3D&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%2Fmav
en.apache.org%2Fplugins%2Fmaven-deploy-plugin%2Fdeploy-mojo.html%23ski
p&data=04%7C01%7Cdirk.fauth%40de.bosch.com%7C02da99082cb94a65d8700
8d92f0f4b0a%7C0ae51e1907c84e4bbb6d648ee58410f4%7C0%7C0%7C6375925649950
41364%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJB
TiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=WEkklKDcDNj3ktGgqMhwrEUlKk
wU3SqbsJbd4xxpfLA%3D&reserved=0
<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmaven.apache.org%2Fplugins%2Fmaven-deploy-plugin%2Fdeploy-mojo.html%23skip&data=04%7C01%7Cdirk.fauth%40de.bosch.com%7C02da99082cb94a65d87008d92f0f4b0a%7C0ae51e1907c84e4bbb6d648ee58410f4%7C0%7C0%7C637592564995041364%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=WEkklKDcDNj3ktGgqMhwrEUlKkwU3SqbsJbd4xxpfLA%3D&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%2Fw
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&data=04%7C01%7Cdirk.fauth%40de.bosch.
c
o
m%7C05e2b8e71e3a445db0a508d92bdd9526%7C0ae51e1907c84e4bbb6d648ee584
1
0
f
4%7C0%7C0%7C637589052951766653%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4w
L
j
A
wMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdat
a
=
y
40LLdLrzCkc6o9y67jJIas2yu07gZwnDmsjhvUcqXY%3D&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%2Fw
i
<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwi>
k
i
.eclipse.org%2FTycho%3AHow_to_deploy_to_a_Maven_repository&data
=
0
4
%7C01%7Cdirk.fauth%40de.bosch.com%7C05e2b8e71e3a445db0a508d92bdd952
6
%
7
C0ae51e1907c84e4bbb6d648ee58410f4%7C0%7C0%7C637589052951766653%7CUn
k
n
o
wn%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haW
w
i
L
CJXVCI6Mn0%3D%7C1000&sdata=IKVEjDoJIJmNMH00uphBbzfdADQ11W6flq1N
H
o
a
%2FQlQ%3D&reserved=0
<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2F
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&dat
a
=
0
4%7C01%7Cdirk.fauth%40de.bosch.com%7C05e2b8e71e3a445db0a508d92bdd95
2
6
%
7C0ae51e1907c84e4bbb6d648ee58410f4%7C0%7C0%7C637589052951766653%7CU
n
k
n
own%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1ha
W
w
i
LCJXVCI6Mn0%3D%7C1000&sdata=IKVEjDoJIJmNMH00uphBbzfdADQ11W6flq1
N
H
o
a%2FQlQ%3D&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%2Fw
ww
<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww>.
eclipse.org%2Fmailman%2Flistinfo%2Ftycho-dev&data=04%7C01%7Cdirk.
f
auth%40de.bosch.com%7C05e2b8e71e3a445db0a508d92bdd9526%7C0ae51e1907
c
8
4
e4bbb6d648ee58410f4%7C0%7C0%7C637589052951766653%7CUnknown%7CTWFpbG
Z
s
b
3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%
3
D
%
7C1000&sdata=ljzdAdE39ghAZVeovNa8XGA5vb%2F6xsPkYSMr4VBSjBU%3D&a
m
p
;
reserved=0
<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2F
w
<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fw>
w
w
.eclipse.org%2Fmailman%2Flistinfo%2Ftycho-dev&data=04%7C01%7Cdirk.
fauth%40de.bosch.com%7C05e2b8e71e3a445db0a508d92bdd9526%7C0ae51e190
7
c
8
4e4bbb6d648ee58410f4%7C0%7C0%7C637589052951766653%7CUnknown%7CTWFpb
G
Z
s
b3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0
%
3
D
%7C1000&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
ww
<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww>.
eclipse.org%2Fmailman%2Flistinfo%2Ftycho-dev&data=04%7C01%7Cdirk.
f
auth%40de.bosch.com%7C05e2b8e71e3a445db0a508d92bdd9526%7C0ae51e1907
c
8
4
e4bbb6d648ee58410f4%7C0%7C0%7C637589052951766653%7CUnknown%7CTWFpbG
Z
s
b
3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%
3
D
%
7C1000&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%2Fww
w
<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww>.
eclipse.org%2Fmailman%2Flistinfo%2Ftycho-dev&data=04%7C01%7Cdirk.
f
auth%40de.bosch.com%7Cd9bb91d2d13347fe468408d92bfd05f8%7C0ae51e1907c
8
4
e4bbb6d648ee58410f4%7C0%7C0%7C637589187988548728%7CUnknown%7CTWFpbGZ
s
b
3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3
D
%
7C1000&sdata=2hp4dawZaiOWX5cNoARfZ%2FF7w1mgAADghG6cd17Mqhw%3D&am
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&data=04%7C01%7Cdirk.
f
auth%40de.bosch.com%7Cd9bb91d2d13347fe468408d92bfd05f8%7C0ae51e1907c
8
4
e4bbb6d648ee58410f4%7C0%7C0%7C637589187988558699%7CUnknown%7CTWFpbGZ
s
b
3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3
D
%
7C1000&sdata=LsRYwWp10fQSnUgHSqiay8BWO0WJpTvmLgaW86xo1ls%3D&
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%2Fwww
<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww>.
eclipse.org%2Fmailman%2Flistinfo%2Ftycho-dev&data=04%7C01%7Cdirk.
f
auth%40de.bosch.com%7C9ce64a20654a4d66a56608d92c0138a0%7C0ae51e1907c8
4
e4bbb6d648ee58410f4%7C0%7C0%7C637589206017149929%7CUnknown%7CTWFpbGZs
b
3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D
%
7C1000&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
<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww>.
eclipse.org%2Fmailman%2Flistinfo%2Ftycho-dev&data=04%7C01%7Cdirk.
f
auth%40de.bosch.com%7C9ce64a20654a4d66a56608d92c0138a0%7C0ae51e1907c8
4
e4bbb6d648ee58410f4%7C0%7C0%7C637589206017149929%7CUnknown%7CTWFpbGZs
b
3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D
%
7C1000&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&data=04%7C01%7Cdirk.f
auth%40de.bosch.com%7C02da99082cb94a65d87008d92f0f4b0a%7C0ae51e1907c84
e4bbb6d648ee58410f4%7C0%7C0%7C637592564995041364%7CUnknown%7CTWFpbGZsb
3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%
7C1000&sdata=ZZoU3bJYBRrJKYhsZuKA7J642SxRrSVWdJApa5Q7xNo%3D&re
served=0
<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww
.eclipse.org%2Fmailman%2Flistinfo%2Ftycho-dev&data=04%7C01%7Cdirk.
fauth%40de.bosch.com%7C02da99082cb94a65d87008d92f0f4b0a%7C0ae51e1907c8
4e4bbb6d648ee58410f4%7C0%7C0%7C637592564995041364%7CUnknown%7CTWFpbGZs
b3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D
%7C1000&sdata=ZZoU3bJYBRrJKYhsZuKA7J642SxRrSVWdJApa5Q7xNo%3D&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&data=04%7C01%7Cdirk.f
auth%40de.bosch.com%7C02da99082cb94a65d87008d92f0f4b0a%7C0ae51e1907c84
e4bbb6d648ee58410f4%7C0%7C0%7C637592564995041364%7CUnknown%7CTWFpbGZsb
3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%
7C1000&sdata=ZZoU3bJYBRrJKYhsZuKA7J642SxRrSVWdJApa5Q7xNo%3D&re
served=0
<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww
.eclipse.org%2Fmailman%2Flistinfo%2Ftycho-dev&data=04%7C01%7Cdirk.
fauth%40de.bosch.com%7C02da99082cb94a65d87008d92f0f4b0a%7C0ae51e1907c8
4e4bbb6d648ee58410f4%7C0%7C0%7C637592564995041364%7CUnknown%7CTWFpbGZs
b3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D
%7C1000&sdata=ZZoU3bJYBRrJKYhsZuKA7J642SxRrSVWdJApa5Q7xNo%3D&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&data=04%7C01%7Cdirk.f
auth%40de.bosch.com%7C02da99082cb94a65d87008d92f0f4b0a%7C0ae51e1907c84
e4bbb6d648ee58410f4%7C0%7C0%7C637592564995041364%7CUnknown%7CTWFpbGZsb
3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%
7C1000&sdata=ZZoU3bJYBRrJKYhsZuKA7J642SxRrSVWdJApa5Q7xNo%3D&re
served=0
