Aditya Kishore created DRILL-228:
------------------------------------
Summary: maven submodule build fails at license-maven-plugin
Key: DRILL-228
URL: https://issues.apache.org/jira/browse/DRILL-228
Project: Apache Drill
Issue Type: Bug
Affects Versions: M1
Reporter: Aditya Kishore
Assignee: Aditya Kishore
Doing a {{mvn install}} at any level except the drill-root cause the build to
fail during execution of license-maven-plugin.
Sample failure
{noformat}
Aditya@MACHINE /repo/git/apache-drill/exec/java-exec
$ mvn clean install -DskipTests
[INFO] Scanning for projects...
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building exec/Java Execution Engine 1.0.0-m1-incubating-SNAPSHOT
[INFO] ------------------------------------------------------------------------
.....
.....
[INFO] Rat check: Summary of files. Unapproved: 0 unknown: 0 generated: 0
approved: 461 licence.
[INFO]
[INFO] --- license-maven-plugin:2.3:check (default) @ java-exec ---
[INFO] Checking licenses...
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 18.158s
[INFO] Finished at: Tue Sep 10 23:45:56 PDT 2013
[INFO] Final Memory: 37M/510M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal com.mycila:license-maven-plugin:2.3:check
(default) on project java-exec: Resource header not found in file system,
classpath or URL: no protocol: header -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please
read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
