I dont know if i completely understand the subject. But i'll try to give my
point of view.
> As far as I understand it, you have chosen Eclipse as the main build tool.
> The releng engineers then need to try to reproduce the build using Maven.
In a development phase, an eclipse plugin developper should only rely on
PDE tools to run its tests or to validate its mofidications.
In a context of continuous integration of eclipse-based project, non
intrusive tools such as buckminster or now tycho are usually used.
>IMO, Maven should be the main build tool.
>I would be satisfied if I can produce a build using Maven, and Eclipse
>offers only text highlighting and editing.
As i understand it, Eclipse PDE internally use ant generated scripts to
build plugins. Those scripts are generated using configuration files such
as build.properties and others.
> However, if you think there is a valid use case for this, please explain!
> Maybe in your situation it makes sense, I would like to understand.
I can see a use case that i've recently encourter, migrating a
buckminster-based build process into a tycho-based one, with sources only
accessible in a readonly mode.
----- Original Message -----
From: "Dieter Van de Walle" <***@ebit.be>
Sent: Mardi 15 Mai 2012 13:00:31
Subject: Re: [tycho-user] Tycho-Surefire guessing the Test Framework
When creating a software project, there is a need for reliable and
reproducable creation of builds.
To do this, a build tool is chosen and build metadata is committed with
As far as I understand it, you have chosen Eclipse as the main build tool.
The releng engineers then need to try to reproduce the build using Maven.
In my view, it is the responsability of the devs to supply a reliable,
tested and reproducable build.
How this is packaged and deployed is another concern.
However, relying on Eclipse as the main build tool seems like a bad idea.
Do you persist the Eclipse configuration also somewhere?
What build metadata do you persist? Eclipse project files?
IMO, Maven should be the main build tool.
I would be satisfied if I can produce a build using Maven, and Eclipse
offers only text highlighting and editing. All the rest is extra,
because build reproducability in time and between machines is primary.
Getting a project working in Eclipse and not in Maven is the equivalent
of "works on my machine" for me. Not acceptable.
However, if you think there is a valid use case for this, please explain!
Maybe in your situation it makes sense, I would like to understand.
On 05/15/2012 12:41 PM, Hervé Esteguet wrote:
>> What is the gain in separating?
> - We avoid polluting source with maven metadata. Tycho is not yet the
native method used by eclipse to build bundles from the workbench. When it
will be so, the presence of the pom.xml into a plugin source will be
> - The releng engineer is not always allowed to modify the source
repository which can be of different sources and natures. In fact the
project could depends on others projects in which you just have a readonly
>> Looks like it makes things more difficult
> - Tycho make this approach easier, in most case the modification of the
pom parent generated by tycho will suffice to configure the whole build
process (an XSLT transformation do the trick). There are small cases like
the original subject of this thread which complicated things.
> ----- Original Message -----
> From: "Mickael Istria"<***@redhat.com>
> To: "Tycho user list"<firstname.lastname@example.org>
> Sent: Mardi 15 Mai 2012 12:12:37
> Subject: Re: [tycho-user] Tycho-Surefire guessing the Test Framework
> On 05/15/2012 11:56 AM, Hervé Esteguet wrote:
> In our dev team we separate releng concerns from dev ones. Sounds like a
bad idea to separate them. They are tightly coupled. Code affects releng,
releng affects code. You cannot isolate them.
> Our idea is that, it's not the same person which is responsible for the
development and for the release engineering. Ok, but IMHO, the guy doing
release engineering is part of the dev team, and should be allowed to
commit poms into bundles.
> The releng engineer maintains a project which inject tycho configuration
during the build process on CI. By doing so we separate eclipse bundle
development from maven considerations.