Maven-licence-plugin

[Vitaliy Kravchenko]

I'm using a maven licence plugin, I have one super pom and four submodules.

<build>
    <plugins>
      <plugin>
        <groupId>com.mycila.maven-license-plugin</groupId>
        <artifactId>maven-license-plugin</artifactId>
        <version>1.9.0</version>
        <configuration>
          <basedir>${headerBaseDir}</basedir>
          <header>${pathtoHeader}</header>
          <aggregate>true</aggregate>
          <includes>
            <include>src/**</include>
            <include>**/test/**</include>
          </includes>
          <excludes>
            <exclude>target/**</exclude>
            <exclude>**/*.properties</exclude>
            <exclude>**/*.sql</exclude>
            <exclude>**/*.xml</exclude>
          </excludes>
          <useDefaultExcludes>true</useDefaultExcludes>
          <strictCheck>true</strictCheck>
        </configuration>
        <executions>
          <execution>
            <phase>test</phase>
            <goals>
              <goal>check</goal>
            </goals>
          </execution>
        </executions>
      </plugin>    

    </plugins>
  </build>

  <properties>
    <headerBaseDir>${basedir}</headerBaseDir>
    <pathtoHeader>${headerBaseDir}\header.txt.</pathtoHeader>
  </properties>

when I'm ivoking licence-plugin from super pom everything is ok, but when I'm trying to invoke plugin from submodules, licence could'nt find the header.txt file. How can I define the root path for submodules? any ideas? thanks

[Peter Johnson]

Try this: in your submodules add this property to the pom:

  <properties>
    <headerBaseDir>${basedir}/..</headerBaseDir>  
  </properties> 

That will override the property value so that when pathToHeader is evaluated you will get the correct value. This of course assumes that you submodule is a submodule of the parent.

However, if the parent is in a completely different location, you cannot do this. Instead you will have to figure something out about having the file appear in source control in multiple locations (if you use a linking mechanism then the actual file will appear only once). Or you could store the file in the Maven repository as a classifier of the parent pom and then have it as a dependency. You'll then need to use the dependency plugin to extract it from the repository and place it where the license plugin can find it.

By the way, do not use backward slashes in filenames - they are too often interpreted as escape characters