Hi guys,
I have a use case where I would resolve beam classpath programmatically. I
wonder if it would be possible to add in META-INF (or BEAM-INF, in the jar
is the main request ;)) a dependencies.txt (or other file) listing all the
mandatory dependencies. I'm mainly interested by the java sdk core module
but can be beneficial to others as well.
With maven it is just a matter of defining:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-dependency-plugin</artifactId>
<version>${dependency-plugin.version}</version>
<executions>
<execution>
<id>create-META-INF/dependencies.txt</id>
<phase>prepare-package</phase>
<goals>
<goal>list</goal>
</goals>
<configuration>
<outputFile>${project.build.outputDirectory}/META-INF/dependencies.txt</outputFile>
</configuration>
</execution>
</executions>
</plugin>
with gradle it is a loop around a resolvedconfiguration which dumps the
artifacts in a maven format (group:name:type:version)
My interest of it being in beam is to be able to upgrade beam without
having to re-release these metadata.
Is it something the project could be interested in?
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://rmannibucau.metawerx.net/> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book
<https://www.packtpub.com/application-development/java-ee-8-high-performance>
