<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Answers to: Externe JARs im maven build</title><link>https://answers.axonivy.com/questions/4046/externe-jars-im-maven-build</link><description>&lt;p&gt;Hi&lt;/p&gt;
&lt;p&gt;Bei unserem Ivyprojekt haben wir mehrere externe jar libraries (&amp;gt; 40MB). Wir haben grad den maven/jenkins build/deployment umgesetzt. Nach dem export von IARs enthalten aber Pakette immer alle externe libraries.&lt;/p&gt;
&lt;p&gt;Alle Ivy Projekten waren ja mavenized und koennen maven dependencies enthalten. Damit muessen wir eigentlich im Designer nicht die externe JARs haben - die werden aus public repo automatisch heruntergeladet. &lt;/p&gt;
&lt;p&gt;Gibt es eine Moeglichkeit, in den target Engine die JARs irgendwie einstecken, um wir dann die JARs in in exportierte IARs nicht haben muessen ? Es wird uns die IARs groesse auf 30% Groesse reduzieren, was waere toll.&lt;/p&gt;
&lt;p&gt;Danke
Josef&lt;/p&gt;</description><atom:link href="https://answers.axonivy.com/questions/4046/externe-jars-im-maven-build" rel="self"></atom:link><language>en</language><lastBuildDate>Thu, 03 Oct 2019 09:59:16 -0400</lastBuildDate><item><title>Answer by Reguel Wermelinger</title><link>https://answers.axonivy.com/questions/4046/externe-jars-im-maven-build/4056</link><description>&lt;p&gt;Hi Josef&lt;/p&gt;
&lt;p&gt;During the build process you could create multiple IAR files for each project. One that runs fine in dev environment and one that is build for deployment (containing the JARs). A multi-module Maven project could then craft the final application: A Zip that contains all IARs which can run on the engine.&lt;/p&gt;
&lt;p&gt;Aware that you are not yet on 7.4 and can not use the full power of the app deployment process I share the link how an app.zip can be created using the latest Axon.ivy products: &lt;a href="https://www.youtube.com/playlist?list=PLrFKpclzHMnJR0Nc3Zmtem9FFHW0g6Jsz"&gt;https://www.youtube.com/playlist?list=PLrFKpclzHMnJR0Nc3Zmtem9FFHW0g6Jsz&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;In the project the additional IAR could be created with an additional profile (that you'll only activate in your remote build environment). &lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;the profiles responsibility is to create a .classpath file which list all the JAR files from maven. I'd do this with a simple antrun-plugin invocation.&lt;/li&gt;
&lt;li&gt;the packed IAR must be assemblied with a special classifier for later retrieval (e.g. &lt;code&gt;com.acme:my-solution:engineIar&lt;/code&gt;)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;... don't hesitate to ask for details if you need more to apply this.&lt;/p&gt;
&lt;p&gt;Regards, 
Reguel&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Reguel Wermelinger</dc:creator><pubDate>Thu, 03 Oct 2019 09:59:16 -0400</pubDate><guid>https://answers.axonivy.com/questions/4046/externe-jars-im-maven-build/4056</guid></item></channel></rss>