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
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/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 ?
Nice spot, just tried to work that one out myself.
My guess is... the documentation generation plugin has been updated and it
now skips/ignores required properties.
If you compare those two plugins, you can see resources was last published
1.5 years ago;
maven-resources-plugin is 2.7, last updated 2014-09-29
maven-compiler-plugin is 3.5.1, last updated 2016-02-06
If a new resources plugin occurs and it's updated to use new
dependencies/plugins, I would bet it doesn't have the required properties
section.
Anyway, my view would be this is a bug/defect with the documenation plugin
skipping/ignoring required properties. As you have highlighted the compiler
doesn't document it uses of ${project.build.outputDirectory}, and if you
look at latest file you can see more required properties are also not
listed.
https://github.com/apache/maven-plugins/blob/cb254e434a40b7ff58c936abbb3f823029a0e466/maven-compiler-plugin/src/main/java/org/apache/maven/plugin/compiler/CompilerMojo.java
John
On 13 April 2016 at 22:26, 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}.
>
> *compiler:compile* plugin goal uses it as well (I guess),
> but it is nowhere defined in the documentation of that plugin. Why is that
> ? is it a lack in the specification or what ?
> am I missing something ?
>
Maybe a lack of specification ?
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}.
*compiler:compile* plugin goal uses it as well (I guess),
but it is nowhere defined in the documentation of that plugin. Why is that
? is it a lack in the specification or what ?
am I missing something ?
