Open jesse-gallagher opened 4 years ago
Just wanted to share a small workaround, we're using to let Maven handle the required dependencies:
Example configuration for the dependency plugin:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-dependency-plugin</artifactId>
<version>3.8.0</version>
<executions>
<execution>
<id>copy-dependencies</id>
<!-- we need to copy the dependencies BEFORE the generate-resource phase as
the NSFODP plugin is generating necessary metadata in that step. -->
<phase>initialize</phase>
<goals>
<goal>copy-dependencies</goal>
</goals>
<configuration>
<outputDirectory>${project.basedir}/nsf/Code/Jars</outputDirectory>
<includeScope>runtime</includeScope><!-- includes compile and runtime dependencies -->
<overWriteReleases>false</overWriteReleases>
<overWriteSnapshots>false</overWriteSnapshots>
<overWriteIfNewer>true</overWriteIfNewer>
<excludeTransitive>true</excludeTransitive>
</configuration>
</execution>
</executions>
</plugin>
Works as expected.
Best regards Ben
This would be a variant of https://github.com/OpenNTF/org.openntf.nsfodp/issues/88 , where it would also copy the JARs in the resultant NSF. This should be a configuration option, similar to maven-bundle-plugin/bnd's Embed-Dependency instruction.