I think if you use one of the Eclipse maven plugins and import the
Maven projects, it will create files it believes are missing.  You
should be able to delete that web.xml file and it will "work".

On Sat, Feb 13, 2010 at 12:03 AM, Henry Saputra <[email protected]> wrote:
> Thanks Bryan,
>
> Apparently there is a file
> "trunk/wink-itests/wink-itest/wink-example-helloworld/src/main/webapp/WEB-INF/web.xml"
> generated without the license header.
>
> I did fresh pull from trunk and was able to do mvn install.
>
> - Henry
>
> On Fri, Feb 12, 2010 at 9:20 PM, Bryant Luk <[email protected]> wrote:
>
>> Hi,
>>
>> I did a quick pull from trunk and I don't see this error.  Hudson (the
>> continuous build server) also seems to have worked out ok with the
>> latest code from trunk.
>>
>> Have you modified or added any custom files?  If you have, then you'll
>> need to add the Apache license to the file.  You can find the missing
>> ones usually by looking at the run and finding:
>>
>> [INFO] [license:check {execution: default}]
>> [INFO] Checking licenses...
>>
>> Then find the next [INFO] messages (ignore the WARNINGs) which should
>> list the file.
>>
>> You can also change the main trunk/pom.xml to disable license checking
>> (it's the maven-license-plugin near line 61).
>>
>> On Fri, Feb 12, 2010 at 10:49 PM, Henry Saputra <[email protected]>
>> wrote:
>> > HI Guys,
>> >
>> > I just tried to do svn update from trunk and run mvn install but got
>> error:
>> >
>> > [INFO]
>> > ------------------------------------------------------------------------
>> > [ERROR] BUILD ERROR
>> > [INFO]
>> > ------------------------------------------------------------------------
>> > [INFO] Some files do not have the expected license header
>> > [INFO]
>> > ------------------------------------------------------------------------
>> > [INFO] Trace
>> > org.apache.maven.lifecycle.LifecycleExecutionException: Some files do not
>> > have the expected license header
>> >    at
>> >
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:703)
>> >    at
>> >
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:540)
>> >    at
>> >
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:519)
>> >    at
>> >
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371)
>> >    at
>> >
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:332)
>> >    at
>> >
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181)
>> >    at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356)
>> >    at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137)
>> >    at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
>> >    at
>> > org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:41)
>> >    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> >    at
>> >
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>> >    at
>> >
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>> >    at java.lang.reflect.Method.invoke(Method.java:597)
>> >    at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
>> >    at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
>> >    at
>> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
>> >    at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
>> > Caused by: org.apache.maven.plugin.MojoExecutionException: Some files do
>> not
>> > have the expected license header
>> >    at
>> >
>> com.google.code.mojo.license.LicenseCheckMojo.execute(LicenseCheckMojo.java:60)
>> >    at
>> >
>> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:483)
>> >    at
>> >
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:678)
>> >    ... 17 more
>> >
>> >
>> > Has anyone else seen this?
>> >
>> > Thanks,
>> >
>> > Henry
>> >
>>
>

Reply via email to