whirr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrei Savu <savu.and...@gmail.com>
Subject Re: [jira] [Updated] (WHIRR-352) mvn package assembly:assembly fails
Date Wed, 09 Nov 2011 09:22:53 GMT
David I will give it a try now on a test machine. I'm more confident that
it should work.

Thanks for following this through!

-- Andrei

On Wed, Nov 9, 2011 at 11:19 AM, David Alves <davidralves@gmail.com> wrote:

> Hi Paul
>
> > No wonder it's called rat.
>
> :)
>
>        That is a different error (checkstyle). I think than in this case
> is a checkstyle problem (code) rather than a checkstyle-plugin problem (as
> was before)
>        Checkstyle is another plugin that is meant to make sure code
> conventions are enforced.
>        You should not be seeing checkstyle errors with a clean trunk
> checkout and a clean application of WHIRR-352 (I don't).
>        Anyhow as the purpose is just to check whether maven builds, you
> can try and correct what checkstyle is complaining about (described in
> project-where-the-build-failed/target/checkstyle-results.xml) and recompile.
>
>        Again, thank you for your help, maven can be maddening sometimes
>
> Cheers
> -david
>
> On Nov 9, 2011, at 3:09 AM, Paul Baclace wrote:
>
> > No wonder it's called rat.  I removed the *.patch file, but it is
> keeping the other irritating file secret and svn cannot spot it.
> >
> > There really should be a way to build a non-official release for testing.
> >
> > [INFO] [jar:jar {execution: default-jar}]
> > [INFO] Building jar:
> /Users/me/project/ws/whirr/trunk/core/target/whirr-core-0.7.0-SNAPSHOT.jar
> > [INFO] [checkstyle:checkstyle {execution: default}]
> > [INFO]
> > [INFO]
> ------------------------------------------------------------------------
> > [ERROR] BUILD ERROR
> > [INFO]
> ------------------------------------------------------------------------
> > [INFO] An error has occurred in Checkstyle report generation.
> >
> > Embedded error: Failed during checkstyle execution
> > There are 1 checkstyle errors.
> > [INFO]
> ------------------------------------------------------------------------
> > [INFO] Trace
> > org.apache.maven.lifecycle.LifecycleExecutionException: An error has
> occurred in Checkstyle report generation.
> >    at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:719)
> >    at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
> >    at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
> >    at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
> >    at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
> >    at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
> >    at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
> >    at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
> >    at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
> >    at
> org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
> >    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: An error has
> occurred in Checkstyle report generation.
> >    at
> org.apache.maven.reporting.AbstractMavenReport.execute(AbstractMavenReport.java:122)
> >    at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
> >    at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
> >    ... 17 more
> > Caused by: org.apache.maven.reporting.MavenReportException: Failed
> during checkstyle execution
> >    at
> org.apache.maven.plugin.checkstyle.AbstractCheckstyleReport.executeReport(AbstractCheckstyleReport.java:278)
> >    at
> org.apache.maven.plugin.checkstyle.CheckstyleReport.executeReport(CheckstyleReport.java:348)
> >    at
> org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:190)
> >    at
> org.apache.maven.reporting.AbstractMavenReport.execute(AbstractMavenReport.java:99)
> >    ... 19 more
> > Caused by:
> org.apache.maven.plugin.checkstyle.CheckstyleExecutorException: There are 1
> checkstyle errors.
> >    at
> org.apache.maven.plugin.checkstyle.DefaultCheckstyleExecutor.executeCheckstyle(DefaultCheckstyleExecutor.java:212)
> >    at
> org.apache.maven.plugin.checkstyle.AbstractCheckstyleReport.executeReport(AbstractCheckstyleReport.java:259)
> >    ... 22 more
> >
> >
> >
> > On 20111108 23:21 , David Alves wrote:
> >> Hi Paul,
> >>
> >> Thanks for testing.
> >> Please make sure no other files but the project's files are in the base
> folder (and any other folders for that matter).
> >> Its common to download patch files to the base dir to apply them but
> these make the maven build fail (rat plugin) because thy don't have the
> apache license and rat does not know that they do not belong to the project.
> >>
> >> Maven 2.2 should be ok
> >>
> >> Cheers
> >> -david
> >>
> >>
> >> On Nov 9, 2011, at 1:08 AM, Paul Baclace wrote:
> >>
> >>> I tried the patch, but I get plenty of errors.   Is mvn v2.2 okay to
> use?
> >>>
> >>>> mvn clean   package assembly:assembly
> >>> [...]
> >>> [ERROR] BUILD FAILURE
> >>> [INFO]
> ------------------------------------------------------------------------
> >>> [INFO] Too many unapproved licenses: 2
> >>>
> >>> What does "Too many unapproved licenses" mean?  Legal assertion failed?
> >>>
> >>> If I could build it, then I could test it.  (There must be something
> wrong since it appears the progression from make(1) to Ant to Maven has had
> the effects "don't know how to build x from y" to "undefined plugin" to
> "Too many unapproved licenses".)
> >>>
> >>>
> >>> Paul
> >>>
> >>>
> >>> On 20111108 21:03 , David Alves (Updated) (JIRA) wrote:
> >>>>      [
> https://issues.apache.org/jira/browse/WHIRR-352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel]
> >>>>
> >>>> David Alves updated WHIRR-352:
> >>>> ------------------------------
> >>>>
> >>>>     Attachment: WHIRR-352.patch
> >>>>
> >>>> I *think* I got it. I removed the dependency on parent proj from
> build-tools so that now it builds first.
> >>>>
> >>>> Please Review!
> >>>>
> >>>>> mvn package assembly:assembly fails
> >>>>> -----------------------------------
> >>>>>
> >>>>>                 Key: WHIRR-352
> >>>>>                 URL: https://issues.apache.org/jira/browse/WHIRR-352
> >>>>>             Project: Whirr
> >>>>>          Issue Type: Bug
> >>>>>          Components: build
> >>>>>    Affects Versions: 0.6.0
> >>>>>         Environment: linux
> >>>>>            Reporter: Karel Vervaeke
> >>>>>            Assignee: David Alves
> >>>>>              Labels: patch
> >>>>>             Fix For: 0.7.0
> >>>>>
> >>>>>         Attachments: WHIRR-352.patch, WHIRR-352.patch,
> WHIRR-352.patch
> >>>>>
> >>>>>
> >>>>> mvn package assembly:assembly fails. Output ends with:
> >>>>> [ERROR] BUILD ERROR
> >>>>> [INFO]
> ------------------------------------------------------------------------
> >>>>> [INFO] An error has occurred in Checkstyle report generation.
> >>>>> Embedded error: Failed during checkstyle execution
> >>>>> Could not find resource
> './build-tools/src/main/resources/checkstyle.xml'.
> >>>>> [INFO]
> ------------------------------------------------------------------------
> >>>>> [INFO] For more information, run Maven with the -e switch
> >>>>> [INFO]
> ------------------------------------------------------------------------
> >>>> --
> >>>> This message is automatically generated by JIRA.
> >>>> If you think it was sent incorrectly, please contact your JIRA
> administrators:
> https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
> >>>> For more information on JIRA, see:
> http://www.atlassian.com/software/jira
> >>>>
> >>>>
> >>>>
> >>
> >
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message