[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[tycho-user] Tycho builds eclipse-target-definitions after eclipse-plugins in Reactor. Problem?
|
Hi,
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,
Andreas
[1]
<https://git.eclipse.org/c/recommenders/org.eclipse.recommenders.git/tree/pom.xml>
--
Codetrails UG (haftungsbeschränkt)
The knowledge transfer company
Robert-Bosch-Str. 7, 64293 Darmstadt
Mobile: +49-170-811-3791
http://www.codetrails.com/
Managing Director: Dr. Marcel Bruch
Handelsregister: Darmstadt HRB 91940
