You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@wink.apache.org by "Jason Dillon (JIRA)" <ji...@apache.org> on 2009/07/12 10:35:14 UTC
[jira] Updated: (WINK-75) Change
com.google.code.maven-license-plugin legal plugin to not be inherited
[ https://issues.apache.org/jira/browse/WINK-75?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason Dillon updated WINK-75:
-----------------------------
Description:
This JIRA is for changing the main pom.xml:
{noformat}
<plugin>
<groupId>com.google.code.maven-license-plugin</groupId>
<artifactId>maven-license-plugin</artifactId>
+ <inherited>false</inherited>
<configuration>
- <header>${module.relative.path}src/etc/header.txt</header>
+ <header>src/etc/header.txt</header>
<quiet>false</quiet>
<failIfMissing>true</failIfMissing>
<aggregate>true</aggregate>
<includes>
- <include>src/**</include>
+ <include>**/src/**</include>
<include>**/test/**</include>
</includes>
<excludes>
{noformat}
Random testing (removing license info on files in submodules) seemed to show this plugin working still. This will enable modules to be more easily created/moved around if necessary.
I think it's still a good idea to run the license plugin on mvn install in the default profile to give a heads up before a bad build.
was:
This JIRA is for changing the main pom.xml:
<plugin>
<groupId>com.google.code.maven-license-plugin</groupId>
<artifactId>maven-license-plugin</artifactId>
+ <inherited>false</inherited>
<configuration>
- <header>${module.relative.path}src/etc/header.txt</header>
+ <header>src/etc/header.txt</header>
<quiet>false</quiet>
<failIfMissing>true</failIfMissing>
<aggregate>true</aggregate>
<includes>
- <include>src/**</include>
+ <include>**/src/**</include>
<include>**/test/**</include>
</includes>
<excludes>
Random testing (removing license info on files in submodules) seemed to show this plugin working still. This will enable modules to be more easily created/moved around if necessary.
I think it's still a good idea to run the license plugin on mvn install in the default profile to give a heads up before a bad build.
> Change com.google.code.maven-license-plugin legal plugin to not be inherited
> ----------------------------------------------------------------------------
>
> Key: WINK-75
> URL: https://issues.apache.org/jira/browse/WINK-75
> Project: Wink
> Issue Type: Improvement
> Components: Build
> Affects Versions: 0.1
> Reporter: Bryant Luk
> Assignee: Bryant Luk
>
> This JIRA is for changing the main pom.xml:
> {noformat}
> <plugin>
> <groupId>com.google.code.maven-license-plugin</groupId>
> <artifactId>maven-license-plugin</artifactId>
> + <inherited>false</inherited>
> <configuration>
> - <header>${module.relative.path}src/etc/header.txt</header>
> + <header>src/etc/header.txt</header>
> <quiet>false</quiet>
> <failIfMissing>true</failIfMissing>
> <aggregate>true</aggregate>
> <includes>
> - <include>src/**</include>
> + <include>**/src/**</include>
> <include>**/test/**</include>
> </includes>
> <excludes>
> {noformat}
> Random testing (removing license info on files in submodules) seemed to show this plugin working still. This will enable modules to be more easily created/moved around if necessary.
> I think it's still a good idea to run the license plugin on mvn install in the default profile to give a heads up before a bad build.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.