You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If we have a flat structure I still have to add the modules manually.
To simplify this, Tycho could allow to specify another directory in which another pom file is generated in which all modules are listed which belong to the main directory. This would allow to configure only one module in the parent pom and all other.
(Maybe this could also be combined with the build.properties settings to define directory patterns which should be include or not).
The text was updated successfully, but these errors were encountered:
To simplify this, Tycho could allow to specify another directory in which another pom file is generated in which all modules are listed which belong to the main directory. This would allow to configure only one module in the parent pom and all other.
One could simply use a structured layout as well instead of adding some kind of indirection ... the main issue with such approaches is that they need to be smart for little benefit and heavily complicate things, e.g if it is a sub directory, it also needs to use a different parent in the flat modules (because the default for a parent is ../pom.xml), then in a flat hierarchy often people have also an extra parent so we need to account for this and so on...
So I would recommend to use a structured layout if you want to have it easy and convenient.
Tychos build extension allows to include modules based on common directories in
tycho/tycho-extras/tycho-pomless/src/main/java/org/eclipse/tycho/pomless/TychoAggregatorMapping.java
Line 46 in c9e3fe9
If we have a flat structure I still have to add the modules manually.
To simplify this, Tycho could allow to specify another directory in which another pom file is generated in which all modules are listed which belong to the main directory. This would allow to configure only one module in the parent pom and all other.
(Maybe this could also be combined with the build.properties settings to define directory patterns which should be include or not).
The text was updated successfully, but these errors were encountered: