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?

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


"Legacy code" often differs from its suggested alternative by actually working and scaling.
 - Bjarne Stroustrup

Back to the top