Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [tycho-user] Tycho builds eclipse-target-definitions after eclipse-plugins in Reactor. Problem?

AFAIK, this problem is unrelated to the linked bug.


What you are seeing here is an effect of how Tycho integrates with Maven: Target files are processed very early in the build, and independent of the module they are located in. The steps that are actually performed as part of the normal eclipse-target-definition build are not needed by the running reactor but may only be needed in a subsequent build that references the same target file.


So in short: there is no need for any worries. Hopefully things will get less confusing with





From: tycho-user-bounces@xxxxxxxxxxx [mailto:tycho-user-bounces@xxxxxxxxxxx] On Behalf Of Tonny Madsen
Sent: Mittwoch, 1. Mai 2013 13:07
To: Tycho user list
Subject: Re: [tycho-user] Tycho builds eclipse-target-definitions after eclipse-plugins in Reactor. Problem?


This is not a problem until you get an error in one of the modules of the reactor and just want to rebuild that module. Unless the target platform modules have been installed in the local Maven repository, it is not possible to re-build...


This is much like the problem outlined in and I have just moved my target platform modules to the beginning of the product-specific top-level POM...




On Wed, May 1, 2013 at 11:04 AM, Jeff MAURY <jeffmaury@xxxxxxxxxxxxx> wrote:

I'm having the same symptom with no problem at all.



On Wed, May 1, 2013 at 10:59 AM, Andreas Sewe <andreas.sewe@xxxxxxxxxxxxxx> wrote:


not sure whether I should be worried or not. Based on our POM [1] Tycho
schedules the build of our eclipse-target-definition artifacts *after*
the eclipse-plugin artifacts that are build w.r.t. to this target platform:

> [INFO] ------------------------------------------------------------------------
> [INFO] Reactor Build Order:
> [INFO]
> [INFO] org.eclipse.recommenders.parent
> [INFO] releng
> [INFO] coding-conventions
> [INFO] licenses
> [INFO] org.eclipse.recommenders.plugin.parent
> [INFO] org.eclipse.recommenders.utils
> [INFO] org.eclipse.recommenders.injection
> [INFO] org.eclipse.recommenders.utils.rcp
> [INFO] org.eclipse.recommenders.rcp
> [INFO] org.eclipse.recommenders.completion.rcp
> [INFO] targets
> [INFO] Eclipse 3.x Target Definition
> [INFO] Eclipse 4.2 Target Definition
> [INFO] Eclipse 4.3 Target Definition

Is this to be expected? Or is this a problem?

In the analogous(?) case of plugin dependencies, (e.g., the "licenses"
and "coding-conventions" artifacts), Maven/Tycho places them before the
projects that require the dependencies in the Reactor.

Hopefully someone can enlighten me.

Best regards,


Codetrails UG (haftungsbeschränkt)
The knowledge transfer company

Robert-Bosch-Str. 7, 64293 Darmstadt
Mobile: +49-170-811-3791

Managing Director: Dr. Marcel Bruch
Handelsregister: Darmstadt HRB 91940
tycho-user mailing list


Error! Filename not specified.
"Legacy code" often differs from its suggested alternative by actually working and scaling.
 - Bjarne Stroustrup

tycho-user mailing list



Tonny Madsen

My profiles: Image removed by sender. LinkedIn Image removed by sender. Twitter Image removed by sender. Blogger Image removed by sender. SlideShare

Back to the top