Archetype build plugin changes - Magnolia 5.6
#1 by arjen on Nov 23, 2017 1:29:36 PM

Hi,

I've just started a fresh maven project based on Magnolia 5.6 archetype (parent pom with webapp) when I noticed building the project doesn't actually copy the jars of the sub modules into the lib folder of the web app, nor does it copy any of the dependencies.

Having done a bit of research I found that the parent POM of my previous project (5.4) used to contain 3 more build plugins that appear to be missing in this fresh 5.6 project.


<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-release-plugin</artifactId>
<version>2.5.3</version>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-deploy-plugin</artifactId>
<version>2.8.2</version>
<configuration>
<skip>true</skip>
</configuration>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-javadoc-plugin</artifactId>
<version>2.10.4</version>
<configuration>
<skip>true</skip>
</configuration>
</plugin>


Does anybody know if this has been done deliberately or not? And ideally how I should fix it so all jars are deployed correctly and I can see changes without having to redeploy my dev server every time?

Thanks
Arjen