materialize products only for certain enviroment

[phermsdorf]

Hi,

to be able to run unit and UI tests on linux i have a target-platform configuration like this:

<plugin>
	<groupId>org.eclipse.tycho</groupId>
	<artifactId>target-platform-configuration</artifactId>
	<version>4.0.13</version>
	<configuration>
	  <target>
		<file>${maven.multiModuleProjectDirectory}/platform.target</file>
	  </target>
	  <environments>
		<environment>
		  <os>win32</os>
		  <ws>win32</ws>
		  <arch>x86_64</arch>
		</environment>
		<environment>
		  <os>linux</os>
		  <ws>gtk</ws>
		  <arch>x86_64</arch>
		</environment>
	  </environments>
	</configuration>
  </plugin>

This leads to also materializing products for eg. linux where i would only need the build products for windows.
I haven't found an option for that on the materialize-product goal.
Is there a way to prevent building the products for a certain environment on a central place? (because we build a lot of products in a lot of different modules ...)

Thanks for any hints on this.

Bye Peter

[laeubi]

If you don't specify an environment then it will simply use the one where you run the build.
Another option is to use maven profiles with <os> activation.

[sratz]

Can't you place the <environments> part of target-platform-configuration in a central super/parent pom.xml?

[laeubi]

But the maven profile would need to be specified in all 30+ modules where products are build... ?

Why? a profile can live everywhere... as said you don't need one at all if you only want to build for the running platform.

[merks]

If all the tests had a common parent you could specify this addition/configuration only in that common parent POM:

		<environment>
		  <os>linux</os>
		  <ws>gtk</ws>
		  <arch>x86_64</arch>
		</environment>

Similarly for having all the products share a common parent POM to remove that from the configuration.

[phermsdorf]

Thank you all for your input.

Why? a profile can live everywhere... as said you don't need one at all if you only want to build for the running platform.

I don't want it for the running platform, but the other way around (building on linux, product only for windows)

Similarly for having all the products share a common parent POM to remove that from the configuration.

That is not possible since our current project is structured like a nested tree of sub-projects and each sub-project provides the parent pom and groups child projects together ... (if that structure makes a lot of sense can be discussed, but thats another topic ...)

But since all our .product definitions are in maven modules of type eclipse-repository (i don't know if that's actually a requirement) i came up with the following which uses the profile approach you suggested:

<profile>
	<id>do-not-build-linux-products</id>
	<activation>
		<property>
			<name>packaging</name>
			<value>eclipse-repository</value>				
		</property>
	</activation>
	<build>
		<plugins>
			<plugin>
				<groupId>org.eclipse.tycho</groupId>
				<artifactId>target-platform-configuration</artifactId>
				<configuration>
					<environments>
						<environment>
							<os>win32</os>
							<ws>win32</ws>
							<arch>x86_64</arch>
						</environment>
					</environments>
				</configuration>
			</plugin>
		</plugins>
	</build>
</profile>

This does the trick and can be configured at the root pom level.

Thanks again for your suggestions!

Bye Peter

[merks]

That's clever and I learned something new. 😀

[laeubi]

I don't want it for the running platform, but the other way around (building on linux, product only for windows)

Hm... then you initial description was a bit unclear (to me) as it reads you only want to build/test one product on a certain environment (e.g either windows or linux) but not always building both. Testing on Linux and building for windows sounds a bit odd to me, but yes activation on the packaging type works for this very specific case.