You are viewing a plain text version of this content. The canonical link for it is here.

Posted to users@maven.apache.org by Will Hoover <ja...@gmail.com> on 2010/08/31 19:09:44 UTC

Plugin configuration property access in POM?

Is there a way that a configuration property of a plug-in used in a parent
POM be accessed in a child POM? For example, If you had some plug-in like
the example below in a parent POM of your project and you wanted to access
the configuration property "escapeString" can you do it in your POM (i.e.
${project.XXX.escapeString} )?

 

<project>

  ...

  <build>

    <plugins>

      <plugin>

        <groupId>org.apache.maven.plugins</groupId>

        <artifactId>maven-resources-plugin</artifactId>

        <version>2.4.3</version>

        <configuration>

          ...

          <escapeString>\</escapeString>

          ...

        </configuration>

      </plugin>

    </plugins>

    ...

  </build>

  ...

</project>

Re: Plugin configuration property access in POM?

Posted by Anders Hammar <an...@hammar.net>.

Not that I know of. But you could declare a standard maven property and use
that for all plugin configuration where you want the same value.

/Anders

On Tue, Aug 31, 2010 at 19:09, Will Hoover <ja...@gmail.com> wrote:

> Is there a way that a configuration property of a plug-in used in a parent
> POM be accessed in a child POM? For example, If you had some plug-in like
> the example below in a parent POM of your project and you wanted to access
> the configuration property "escapeString" can you do it in your POM (i.e.
> ${project.XXX.escapeString} )?
>
>
>
> <project>
>
>  ...
>
>  <build>
>
>    <plugins>
>
>      <plugin>
>
>        <groupId>org.apache.maven.plugins</groupId>
>
>        <artifactId>maven-resources-plugin</artifactId>
>
>        <version>2.4.3</version>
>
>        <configuration>
>
>          ...
>
>          <escapeString>\</escapeString>
>
>          ...
>
>        </configuration>
>
>      </plugin>
>
>    </plugins>
>
>    ...
>
>  </build>
>
>  ...
>
> </project>
>
>
>
>
>
>
>
>
>
>