Task #10201: Uber-jar-adoption
|Status:||Closed||Start date:||Oct 27, 2017|
|Assignee:||Gabriele Giammatteo||% Done:|
|Sprint:||zz - Uber-jar assembly|
In order to avoid issues caused by the use of jar-with-dependency plugin, which creates an unshaded uber-jar, a new assembly plugin has been prepared as in provided xml file.
Please evaluate if some further adjustments are needed and then publish it in one of our repository so that it can be shared among projects and maintained in a single point.
A working example of its use can be found under http://svn.research-infrastructures.eu/public/d4science/gcube/trunk/data-transfer/sis-geotk-plugin@157651
#1 Updated by Gabriele Giammatteo about 2 years ago
- % Done changed from 0 to 80
- Status changed from New to In Progress
I added your descriptor in the shared-assemblies component so they will be visible from all components. I also updated the maven-parent adding a common configuration to build uber jars. Before announcing this to all developers, can you please test if it works with your component replacing your assmbly plugin configuration with:
<plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-assembly-plugin</artifactId> <executions> <execution> <id>make-uberjar</id> <phase>install</phase> </execution> <execution> <id>make-servicearchive</id> <phase>install</phase> </execution> </executions> </plugin>
and verify that the uberjar is built correctly? (try to clean your local repository if it does not work the first time)
In addition, this new configuration should also build the servicearchive using a common configuration I included in the maven-parent. Please check that also the servicearchive is built correctly
#2 Updated by Gabriele Giammatteo about 2 years ago
- % Done changed from 80 to 100
- Status changed from In Progress to Feedback
The solution seems to work. I updated the wiki with the instructions to use this new artifact type . Let me know if further actions are required before closing the activity.