CODEWITHSUNDEEP
mavennexusmaven-assembly-pluginbuild-helper-maven-plugin
Sandy
Sandy

Reputation: 507

Confused with maven assembly plugin vs build-helper-maven:attach-artifact

I'm a bit confused between maven assembly plugin and build-helper-maven plugin. I've also read in the maven documentation that The assemblies/archive created by the Assembly Plugin gets deployed during the deployed phase.Hence, they can be deployed to the remote nexus repositories.

The purpose of maven assembly plugin is to archive many things into one(say in tar.gz format). However, the attach-artifact goal present within build-helper-maven plugin has the same role i.e.archiving,installing and deploying the artifact.

With that being said,why would anyone use both of them together? I've seen people using both of them together. Isn't one of the plugins an alternative choice of the other?

Kindly advise.

Upvotes: 0

Views: 842

Answers (1)

khmarbaise
khmarbaise

Reputation: 97447

If you use maven-assembly-plugin you can create as you already mentioned any kind of archives (range from very simple to very complex structures) they will be by default be attached to your project which means they will be deployed into remote repositories in one go if you do mvn deploy with no supplemental configuration.

The build-helper-maven-plugin is intended to add an artifact (one goal of this plugin) which is usually not generated by Maven itself which most of the cases is a smell. If people using them together (in the use case to create an archive and attach it) this makes no sense.

Apart from that the build-helper-maven-plugin can also be used to add other source directories for example for scala, kotlin projects (other goals for example add-source etc.)

So those plugins are not alternatives they have different intentions/use cases.

Upvotes: 1

Related Questions