Hi together,
I had a
discussion with Sebastian regarding the DEPENDENCIES file and different outcomes of the eclipse dash tool. The github workflow provided by sig infra includes the test dependencies and
the (commonly known) command for the maven plugin uses the compile scope.
If you’re wondering what’s right: The test dependencies MUST be included.
The discussion summarizes the different usage options, but Sebastian proposed to point out, that you could directly set the configuration
in the pom.xml of the maven plugin:
<plugin>
<groupId>org.eclipse.dash</groupId>
<artifactId>license-tool-plugin</artifactId>
<version>0.0.1-SNAPSHOT</version>
<configuration>
<projectId>automotive.tractusx</projectId>
<summary>DEPENDENCIES</summary>
<includeScope>test</includeScope>
</configuration>
<executions>
<execution>
<id>license-check</id>
<goals>
<goal>license-check</goal>
</goals>
</execution>
</executions>
</plugin>
Command: mvn org.eclipse.dash:license-tool-plugin:license-check
Maybe this could be an option for a few other persons. Maybe you also have something to add regarding the discussion.
BR
Tom Meyer
Fraunhofer-Institut für Software- und Systemtechnik ISST
Wissenschaftlicher Mitarbeiter Logistik
Speicherstraße 6, 44147 Dortmund, Germany
Telefon +49 231 97677-442
tom.meyer@xxxxxxxxxxxxxxxxxx
www.isst.fraunhofer.de
--------------------------------------------------------------------------------------------------
Folgen Sie uns: