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.
[code]
<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>
[/code]
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
--
Context is everything:
http://forum.magnolia-cms.com/forum/thread.html?threadId=7a710cff-d3da-43dc-a2fe-9855a4044926
----------------------------------------------------------------
For list details, see http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: <user-list-unsubscr...@magnolia-cms.com>
----------------------------------------------------------------
