war web-inf/lib dependencies without declaration
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 WEB-INF/lib. -- View this message in context: http://maven.40175.n5.nabble.com/war-web-inf-lib-dependencies-without-dependency-declaration-tp5865497.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maybe a lack of specification ?
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 11:26 PM, Raffaele Esposito wrote:
>
>> Hi all,
>>
>> In the Maven super-pom.xml definition (4.0.0)
>> in the build section are defined some configuration parameters,
>> such as:
>>
>>
>>
>> ${project.basedir}/target
>>
>> ${project.build.directory}/classes
>> ${project.basedir}/target
>>
>> ${project.build.directory}/classes
>> ${project.artifactId}-${project.version}
>>
>>
>> ${project.build.directory}/test-classes
>>
>> ${project.basedir}/src/main/java
>> ...
>>
>> Now let's take for example :
>> ${project.build.directory}/classes
>>
>> *resources:resources* plugin goal uses it, as described in the
>> documentation:
>>
>> Name Type Since Description outputDirectory File - The output
>> directory into which to copy the resources. Default value is:
>> ${project.build.outputDirectory}.
>>
>
> Yes the maven-resources-plugin defines it and it means you can change it
> via the pom configuration for the goal: resources
>
>
>> *compiler:compile* plugin goal uses it as well (I guess),
>> but it is nowhere defined in the documentation of that plugin.
>>
>
>
> In the documentation you mean that you can use it as a configuration entry
> in the pom ? And yes this it is correct, cause it wouldn't make sense to
> change it...(which is also true for the maven-resources-plugin) but at the
> moment it is as it is...This might change for 3.0.0 of
> maven-resources-plugin...
>
>
> And the other thing it is defined for the compiler-plugin as you can see
> here:
>
>
> http://svn.apache.org/viewvc/maven/plugins/trunk/maven-compiler-plugin/src/main/java/org/apache/maven/plugin/compiler/CompilerMojo.java?revision=1517906&view=markup#l65
>
>
>
> >
>
>> Why is that
>> ? is it a lack in the specification or what ?
>> am I missing something ?
>>
>>
> Kind regards
> Karl Heinz Marbaise
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>
Re: Maybe a lack of specification ?
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
attached or related pull request (via githup) or at least write in the
issues what and how to improve this...
Apache Maven is an open source project ...any help is appreciated...
Kind regards
Karl Heinz Marbaise
Kind regards,
Raffaele
On Thu, Apr 14, 2016 at 12:21 AM, Karl Heinz Marbaise mailto:khmarba...@gmx.de>> wrote:
Hi,
On 4/13/16 11:26 PM, Raffaele Esposito wrote:
Hi all,
In the Maven super-pom.xml definition (4.0.0)
in the build section are defined some configuration parameters,
such as:
${project.basedir}/target
${project.build.directory}/classes
${project.basedir}/target
${project.build.directory}/classes
${project.artifactId}-${project.version}
${project.build.directory}/test-classes
${project.basedir}/src/main/java
...
Now let's take for example :
${project.build.directory}/classes
*resources:resources* plugin goal uses it, as described in the
documentation:
Name Type Since Description outputDirectory File - The output
directory into which to copy the resources. Default value is:
${project.build.outputDirectory}.
Yes the maven-resources-plugin defines it and it means you can
change it via the pom configuration for the goal: resources
*compiler:compile* plugin goal uses it as well (I guess),
but it is nowhere defined in the documentation of that plugin.
In the documentation you mean that you can use it as a configuration
entry in the pom ? And yes this it is correct, cause it wouldn't
make sense to change it...(which is also true for the
maven-resources-plugin) but at the moment it is as it is...This
might change for 3.0.0 of maven-resources-plugin...
And the other thing it is defined for the compiler-plugin as you can
see here:
http://svn.apache.org/viewvc/maven/plugins/trunk/maven-compiler-plugin/src/main/java/org/apache/maven/plugin/compiler/CompilerMojo.java?revision=1517906&view=markup#l65
>
Why is that
? is it a lack in the specification or what ?
am I missing something ?
Kind regards
Karl Heinz Marbaise
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Shared Component: Maven Archiver Version 3.0.1 Released
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 project's target directory. Important Notes: * Maven 3.X only * JDK 6 minimum requirement You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-source-plugin 3.0.0 You can download the appropriate sources etc. from the download page: http://maven.apache.org/plugins/maven-source-plugin/download.html Release Note Apache Maven Source Plugin Version 3.0.0 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317924&version=12331545 Bug: * [MSOURCES-81] - allow sources jar to contain Maven descriptor Improvements: * [MSOURCES-75] - Update version of plexus-archiver to 2.7 * [MSOURCES-76] - Upgrade from maven-plugins version 25 to 26 * [MSOURCES-77] - Upgrade maven-archiver from 2.5 to 2.6 * [MSOURCES-78] - Upgrade plexus-archiver 2.7 to 2.8.4 * [MSOURCES-79] - Upgrade to maven-plugins parent version 27 * [MSOURCES-80] - Upgrade plexus-archiver to 2.10.2 * [MSOURCES-82] - Make naming of properties consistent to the plugin name. * [MSOURCES-83] - Make Plugin only Maven 3.0 minimum * [MSOURCES-84] - Change package name from org.apache.maven.plugin to org.apache.maven.plugins * [MSOURCES-85] - Upgrade plexus-archiver to 3.0.1 * [MSOURCES-86] - Upgrade maven-archiver to 3.0.0 * [MSOURCES-88] - Upgrade plexus-utils to 3.0.22 * [MSOURCES-89] - Using plugin parent version 28 * [MSOURCES-90] - Upgrade junit to 4.11 * [MSOURCES-91] - Added several properties for parameters * [MSOURCES-92] - Generate Maven Descriptor by default * [MSOURCES-93] - Upgrade plexus-archiver from 3.0.1 to 3.0.3 Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Shared Component: Maven Archiver Version 3.0.1 Released
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 the Apache Maven Shared Component: Maven Archiver Version 3.0.1. https://maven.apache.org/shared/maven-archiver/ The Maven Archiver is mainly used by plugins to handle packaging. The version numbers referenced in the Since column on this page are the version of the Maven Archiver component - not for any specific plugin. To see which version of Maven Archiver a plugin uses, go to the site for that plugin. Important Note since Version 3.0.0: * Maven 3.X only * JDK 6 minimum requirement You should specify the version in your project's pom as follows: org.apache.maven.shared maven-archiver 3.0.1 You can download the appropriate sources etc. from the download page: https://maven.apache.org/shared/maven-archiver/download.cgi Release Notes Maven Archiver 3.0.1 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922&version=12334036 Bugs: * [MSHARED-154] - pomPropertiesFile does not actually permit override * [MSHARED-191] - Specification-Version must not contain "-SNAPSHOT" * [MSHARED-298] - Errors in manifest example on site Improvements: * [MSHARED-296] - Improve header of pom.properties * [MSHARED-465] - Remove @Deprecated marked code * [MSHARED-506] - Upgrade plexus-archiver from 2.9.1 to 3.1.1 * [MSHARED-511] - Using structures to keep insertion order for MANIFEST.MF * [MSHARED-512] - Remove @Deprecated marked code which has been missed. Tasks: * [MSHARED-492] - Upgrade parent to version 22 * [MSHARED-493] - Clean up warnings emitted by Javadoc 8 (doclint) and Checkstyle Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Site Plugin 3.5.1 Released
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 configuration:
org.apache.maven.plugins
maven-site-plugin
3.5.1
You can download the appropriate sources etc. from the download page:
http://maven.apache.org/plugins/maven-site-plugin/download.cgi
Release Notes - Apache Maven Site Plugin - Version 3.5.1
Bug
* [MSITE-771] FAQ Entry for difference between mvn site and mvn site:site is
incorrect
* [MSITE-769] Can't use property in breadcrumbs items in child module site
descriptor
Improvement
* [MSITE-768] Support Velocity's #parse and #include
* [MSITE-700] All inclusion of resources up to ${basedir} when Velocity 1.7 is
used
Enjoy,
-The Maven team
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
