[ANN] Apache Maven Site Plugin 3.5.1 Released

2016-04-14 Thread Hervé Boutemy
The Maven team is pleased to announce the release of the Apache Maven Site Plugin, version 3.5.1 The Maven Site Plugin is a plugin that generates a site for the current project. http://maven.apache.org/plugins/maven-site-plugin/ You should specify the version in your project's plugin

[ANN] Apache Maven Shared Component: Maven Archiver Version 3.0.1 Released

2016-04-14 Thread Karl Heinz Marbaise
Hi to all, unfortunately the previous email about Maven Archiver 3.0.1 announcement contained the wrong content. Now the following content is the correct one (hopefully ;-). Sorry for the confusion. Kind regards Karl Heinz Marbaise The Apache Maven team is pleased to announce the release of

[ANN] Apache Maven Shared Component: Maven Archiver Version 3.0.1 Released

2016-04-14 Thread Karl Heinz Marbaise
The Apache Maven team is pleased to announce the release of the Apache Maven Source Plugin Version 3.0.0. https://maven.apache.org/plugins/maven-source-plugin/ The Source Plugin creates a jar archive of the source files of the current project. The jar file is, by default, created in the

Re: Maybe a lack of specification ?

2016-04-14 Thread Karl Heinz Marbaise
Hi, On 4/14/16 5:37 PM, Raffaele Esposito wrote: Hi, Thank you for your mails. I still think maven plugin documentations are poorly designed, what I highlighted could indeed be considered defect in the documentation. So i would suggest to make appropriate issue in JIRA either with patches

Re: Maybe a lack of specification ?

2016-04-14 Thread Raffaele Esposito
Hi, Thank you for your mails. I still think maven plugin documentations are poorly designed, what I highlighted could indeed be considered defect in the documentation. Kind regards, Raffaele On Thu, Apr 14, 2016 at 12:21 AM, Karl Heinz Marbaise wrote: > Hi, > > On 4/13/16

war web-inf/lib dependencies without declaration

2016-04-14 Thread paulkc
Can maven build a legacy war project where all the dependencies are in WEB-INF/lib? I'm aware you can declare each jar in the pom as a dependency but this is not a realistic (or practical) approach. It needs to be dynamic... grab misc legacy war project and build it based on dependencies in