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 <khmarba...@gmx.de
<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:

        <build>

                  <directory>${project.basedir}/target</directory>

          <outputDirectory>${project.build.directory}/classes</outputDirectory>
        <directory>${project.basedir}/target</directory>

          <outputDirectory>${project.build.directory}/classes</outputDirectory>

          <finalName>${project.artifactId}-${project.version}</finalName>

          
<testOutputDirectory>${project.build.directory}/test-classes</testOutputDirectory>

          <sourceDirectory>${project.basedir}/src/main/java</sourceDirectory>
        ...<build>

        Now let's take for example :
        <outputDirectory>${project.build.directory}/classes</outputDirectory>

        *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

Reply via email to