Reputation: 4403
I am currently developing a go lang
application which will be used to provision a server (written in Java
) by building a given pom.xml
file. Since Java
is required for running the server, the running system is already having Java
installed but it could or could not have maven
installed.
So without installing maven
or setting M2_HOME
in $PATH
variable of the running system, the go
application is written in such a way that it uses a exploded maven
distribution (which is needed to be packed with the release) for the above provisioning.
Since the maven
distribution (apache-maven-3.5.2-bin.zip) size is around 9MB the release zip of the application becomes bulky as it is packed with exploded maven
distribution. If possible is there any way of reducing the size of the maven
distribution by keeping only the libs which required for performing the maven
build, so that the release zip will become less bulky.
Upvotes: 0
Views: 284
Reputation: 4403
As with the responses received from the maven-mailing list
, the maven
installation/distribution just includes the basic features to perform the core features of a build and additional plugins are downloaded as needed to do specific tasks during the build steps. As they suggests the only way to reduce the size is by removing the jansi
jar which is used for colour logging.
Upvotes: 1