You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by Gary Jones <ac...@garydjones.name> on 2009/03/23 10:44:26 UTC
Building camel failing
I tried to build camel based on the latest source from svn, and it
failed. Following the instructions on the website I eventually got to
(note: -e is my own addition, hoping to get some more info about the
problem):
mvn -e -Dtest=false clean install
[...many lines of output...]
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] An error has occurred in JavaDocs report generation:Exit code: 1 - javadoc: error - invalid flag: -author
Command line was:C:\Programme\Develop\Java\1.5se\jre\..\bin\javadoc.exe -J-Xmx500m @options
[INFO] ------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: An error has occurred in JavaDocs report generation:Exit code: 1 - javadoc: error - invalid flag: -author
Command line was:C:\Programme\Develop\Java\1.5se\jre\..\bin\javadoc.exe -J-Xmx500m @options
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:584)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:500)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:479)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:331)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:292)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:301)
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:585)
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 JavaDocs report generation:Exit code: 1 - javadoc: error - invalid flag: -author
Command line was:C:\Programme\Develop\Java\1.5se\jre\..\bin\javadoc.exe -J-Xmx500m @options
at org.apache.maven.plugin.javadoc.JavadocReport.execute(JavadocReport.java:215)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:453)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:559)
... 16 more
Caused by: org.apache.maven.reporting.MavenReportException: Exit code: 1 - javadoc: error - invalid flag: -author
Command line was:C:\Programme\Develop\Java\1.5se\jre\..\bin\javadoc.exe -J-Xmx500m @options
at org.apache.maven.plugin.javadoc.AbstractJavadocMojo.executeJavadocCommandLine(AbstractJavadocMojo.java:4013)
at org.apache.maven.plugin.javadoc.AbstractJavadocMojo.executeReport(AbstractJavadocMojo.java:1593)
at org.apache.maven.plugin.javadoc.JavadocReport.generate(JavadocReport.java:122)
at org.apache.maven.plugin.javadoc.JavadocReport.execute(JavadocReport.java:209)
... 18 more
Does anyone have any ideas what might be up? (BTW, "-author" seems to be
perfectly valid to pass to javadoc, javadoc -help says
"Provided by Standard doclet:
-d <directory> Destination directory for output files
-use Create class and package usage pages
-version Include @version paragraphs
-author Include @author paragraphs"
amongst other things, so I don't know why it should complain about it.)
On the previous maven step I had some errors regarding checksums, but
this seems more basic than something related to those (and in any case,
no error was reported at the end of that, I just happened to see some
"flash" by as the process was going through).
Re: Building camel failing
Posted by Claus Ibsen <cl...@gmail.com>.
Hi
Thanks for reporting back. I added the note about 2.0.9 is currently used.
On Tue, Mar 24, 2009 at 10:41 AM, Gary Jones <ac...@garydjones.name> wrote:
> On Mon, Mar 23, 2009 at 12:02:08PM +0100, Claus Ibsen wrote:
>> On Mon, Mar 23, 2009 at 11:56 AM, Gary Jones wrote:
>> > On Mon, Mar 23, 2009 at 10:14:26AM +0000, James Strachan wrote:
>
>> >> which maven version are you using?
>> >
>> > Maven version: 2.0.10
>> > Java version: 1.5.0_12
>> > OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"
>> Willem Jiang is also a Camel committer and he uses Windows XP.
>>
>> Can you try with Maven 2.0.9? That is what we use for building the release.
>
> That seems to be the cause of it :-( It's working for me now (i.e. with
> maven 2.0.9), so it looks like either maven introduced a bug in 2.0.10
> or there is something in the Camel build process that relied on
> previously incorrect behaviour in 2.0.9. Might be worth mentioning in
> the build instructions on the website that it requires maven 2.0.9 at
> the moment, not the latest version.
>
> Thanks for your help, all.
>
--
Claus Ibsen
Apache Camel Committer
Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/
Re: Building camel failing
Posted by Gary Jones <ac...@garydjones.name>.
On Mon, Mar 23, 2009 at 12:02:08PM +0100, Claus Ibsen wrote:
> On Mon, Mar 23, 2009 at 11:56 AM, Gary Jones wrote:
> > On Mon, Mar 23, 2009 at 10:14:26AM +0000, James Strachan wrote:
> >> which maven version are you using?
> >
> > Maven version: 2.0.10
> > Java version: 1.5.0_12
> > OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"
> Willem Jiang is also a Camel committer and he uses Windows XP.
>
> Can you try with Maven 2.0.9? That is what we use for building the release.
That seems to be the cause of it :-( It's working for me now (i.e. with
maven 2.0.9), so it looks like either maven introduced a bug in 2.0.10
or there is something in the Camel build process that relied on
previously incorrect behaviour in 2.0.9. Might be worth mentioning in
the build instructions on the website that it requires maven 2.0.9 at
the moment, not the latest version.
Thanks for your help, all.
Re: Building camel failing
Posted by Gary Jones <ac...@garydjones.name>.
On Mon, Mar 23, 2009 at 03:09:32PM +0100, Claus Ibsen wrote:
> On Mon, Mar 23, 2009 at 3:05 PM, Willem Jiang wrote:
> > My developments env is Maven 2.0.09, Java 1.5.0_13 and Windows Vista
> > The build looks good to me.
> > BTW, I just noticed the command line like this,
> > C:\Programme\Develop\Java\1.5se\jre\..\bin\javadoc.exe
> >
> > Did you set your JAVA_HOME to the 1.5se directory?
> Yeah it should point to the JRE directory.
It should point to a JDK directory, which it does:
C:\Dokumente und Einstellungen\gary>echo %JAVA_HOME%
C:\Programme\Develop\Java\1.5se
otherwise javac will fail, if I recall correctly.
Re: Building camel failing
Posted by Claus Ibsen <cl...@gmail.com>.
On Mon, Mar 23, 2009 at 3:05 PM, Willem Jiang <wi...@gmail.com> wrote:
> My developments env is Maven 2.0.09, Java 1.5.0_13 and Windows Vista
> The build looks good to me.
> BTW, I just noticed the command line like this,
> C:\Programme\Develop\Java\1.5se\jre\..\bin\javadoc.exe
>
> Did you set your JAVA_HOME to the 1.5se directory?
Yeah it should point to the JRE directory.
>
> Willem
>
> Claus Ibsen wrote:
>> On Mon, Mar 23, 2009 at 11:56 AM, Gary Jones <ac...@garydjones.name> wrote:
>>> On Mon, Mar 23, 2009 at 10:14:26AM +0000, James Strachan wrote:
>>>> Any idea which directory you were in when this failure occurred?
>>> The top level project directory, i.e. the one containing the README.txt
>>> file and so forth.
>>>
>>>> Also
>>>> which maven version are you using?
>>> Maven version: 2.0.10
>>> Java version: 1.5.0_12
>>> OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"
>> Willem Jiang is also a Camel committer and he uses Windows XP.
>>
>> Can you try with Maven 2.0.9? That is what we use for building the release.
>>
>>
>>>> 2009/3/23 Gary Jones <ac...@garydjones.name>:
>>>>> I tried to build camel based on the latest source from svn, and it
>>>>> failed. Following the instructions on the website I eventually got to
>>>>> (note: -e is my own addition, hoping to get some more info about the
>>>>> problem):
>>>>>
>>>>> mvn -e -Dtest=false clean install
>>>>> [...many lines of output...]
>>>>> [INFO] ------------------------------------------------------------------------
>>>>> [ERROR] BUILD ERROR
>>>>> [INFO] ------------------------------------------------------------------------
>>>>> [INFO] An error has occurred in JavaDocs report generation:Exit code: 1 - javadoc: error - invalid flag: -author
>>>>>
>>>>> Command line was:C:\Programme\Develop\Java\1.5se\jre\..\bin\javadoc.exe -J-Xmx500m @options
>>
>>
>>
>
>
--
Claus Ibsen
Apache Camel Committer
Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/
Re: Building camel failing
Posted by Willem Jiang <wi...@gmail.com>.
My developments env is Maven 2.0.09, Java 1.5.0_13 and Windows Vista
The build looks good to me.
BTW, I just noticed the command line like this,
C:\Programme\Develop\Java\1.5se\jre\..\bin\javadoc.exe
Did you set your JAVA_HOME to the 1.5se directory?
Willem
Claus Ibsen wrote:
> On Mon, Mar 23, 2009 at 11:56 AM, Gary Jones <ac...@garydjones.name> wrote:
>> On Mon, Mar 23, 2009 at 10:14:26AM +0000, James Strachan wrote:
>>> Any idea which directory you were in when this failure occurred?
>> The top level project directory, i.e. the one containing the README.txt
>> file and so forth.
>>
>>> Also
>>> which maven version are you using?
>> Maven version: 2.0.10
>> Java version: 1.5.0_12
>> OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"
> Willem Jiang is also a Camel committer and he uses Windows XP.
>
> Can you try with Maven 2.0.9? That is what we use for building the release.
>
>
>>> 2009/3/23 Gary Jones <ac...@garydjones.name>:
>>>> I tried to build camel based on the latest source from svn, and it
>>>> failed. Following the instructions on the website I eventually got to
>>>> (note: -e is my own addition, hoping to get some more info about the
>>>> problem):
>>>>
>>>> mvn -e -Dtest=false clean install
>>>> [...many lines of output...]
>>>> [INFO] ------------------------------------------------------------------------
>>>> [ERROR] BUILD ERROR
>>>> [INFO] ------------------------------------------------------------------------
>>>> [INFO] An error has occurred in JavaDocs report generation:Exit code: 1 - javadoc: error - invalid flag: -author
>>>>
>>>> Command line was:C:\Programme\Develop\Java\1.5se\jre\..\bin\javadoc.exe -J-Xmx500m @options
>
>
>
Re: Building camel failing
Posted by Claus Ibsen <cl...@gmail.com>.
On Mon, Mar 23, 2009 at 11:56 AM, Gary Jones <ac...@garydjones.name> wrote:
> On Mon, Mar 23, 2009 at 10:14:26AM +0000, James Strachan wrote:
>> Any idea which directory you were in when this failure occurred?
>
> The top level project directory, i.e. the one containing the README.txt
> file and so forth.
>
>> Also
>> which maven version are you using?
>
> Maven version: 2.0.10
> Java version: 1.5.0_12
> OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"
Willem Jiang is also a Camel committer and he uses Windows XP.
Can you try with Maven 2.0.9? That is what we use for building the release.
>
>> 2009/3/23 Gary Jones <ac...@garydjones.name>:
>> > I tried to build camel based on the latest source from svn, and it
>> > failed. Following the instructions on the website I eventually got to
>> > (note: -e is my own addition, hoping to get some more info about the
>> > problem):
>> >
>> > mvn -e -Dtest=false clean install
>> > [...many lines of output...]
>> > [INFO] ------------------------------------------------------------------------
>> > [ERROR] BUILD ERROR
>> > [INFO] ------------------------------------------------------------------------
>> > [INFO] An error has occurred in JavaDocs report generation:Exit code: 1 - javadoc: error - invalid flag: -author
>> >
>> > Command line was:C:\Programme\Develop\Java\1.5se\jre\..\bin\javadoc.exe -J-Xmx500m @options
>
--
Claus Ibsen
Apache Camel Committer
Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/
Re: Building camel failing
Posted by Gary Jones <ac...@garydjones.name>.
On Mon, Mar 23, 2009 at 10:14:26AM +0000, James Strachan wrote:
> Any idea which directory you were in when this failure occurred?
The top level project directory, i.e. the one containing the README.txt
file and so forth.
> Also
> which maven version are you using?
Maven version: 2.0.10
Java version: 1.5.0_12
OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"
> 2009/3/23 Gary Jones <ac...@garydjones.name>:
> > I tried to build camel based on the latest source from svn, and it
> > failed. Following the instructions on the website I eventually got to
> > (note: -e is my own addition, hoping to get some more info about the
> > problem):
> >
> > mvn -e -Dtest=false clean install
> > [...many lines of output...]
> > [INFO] ------------------------------------------------------------------------
> > [ERROR] BUILD ERROR
> > [INFO] ------------------------------------------------------------------------
> > [INFO] An error has occurred in JavaDocs report generation:Exit code: 1 - javadoc: error - invalid flag: -author
> >
> > Command line was:C:\Programme\Develop\Java\1.5se\jre\..\bin\javadoc.exe -J-Xmx500m @options
Re: Building camel failing
Posted by James Strachan <ja...@gmail.com>.
Any idea which directory you were in when this failure occurred? Also
which maven version are you using?
2009/3/23 Gary Jones <ac...@garydjones.name>:
> I tried to build camel based on the latest source from svn, and it
> failed. Following the instructions on the website I eventually got to
> (note: -e is my own addition, hoping to get some more info about the
> problem):
>
> mvn -e -Dtest=false clean install
> [...many lines of output...]
> [INFO] ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO] ------------------------------------------------------------------------
> [INFO] An error has occurred in JavaDocs report generation:Exit code: 1 - javadoc: error - invalid flag: -author
>
> Command line was:C:\Programme\Develop\Java\1.5se\jre\..\bin\javadoc.exe -J-Xmx500m @options
>
> [INFO] ------------------------------------------------------------------------
> [INFO] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: An error has occurred in JavaDocs report generation:Exit code: 1 - javadoc: error - invalid flag: -author
>
> Command line was:C:\Programme\Develop\Java\1.5se\jre\..\bin\javadoc.exe -J-Xmx500m @options
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:584)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:500)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:479)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:331)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:292)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:301)
> 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:585)
> 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 JavaDocs report generation:Exit code: 1 - javadoc: error - invalid flag: -author
>
> Command line was:C:\Programme\Develop\Java\1.5se\jre\..\bin\javadoc.exe -J-Xmx500m @options
> at org.apache.maven.plugin.javadoc.JavadocReport.execute(JavadocReport.java:215)
> at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:453)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:559)
> ... 16 more
> Caused by: org.apache.maven.reporting.MavenReportException: Exit code: 1 - javadoc: error - invalid flag: -author
>
> Command line was:C:\Programme\Develop\Java\1.5se\jre\..\bin\javadoc.exe -J-Xmx500m @options
> at org.apache.maven.plugin.javadoc.AbstractJavadocMojo.executeJavadocCommandLine(AbstractJavadocMojo.java:4013)
> at org.apache.maven.plugin.javadoc.AbstractJavadocMojo.executeReport(AbstractJavadocMojo.java:1593)
> at org.apache.maven.plugin.javadoc.JavadocReport.generate(JavadocReport.java:122)
> at org.apache.maven.plugin.javadoc.JavadocReport.execute(JavadocReport.java:209)
> ... 18 more
>
> Does anyone have any ideas what might be up? (BTW, "-author" seems to be
> perfectly valid to pass to javadoc, javadoc -help says
> "Provided by Standard doclet:
> -d <directory> Destination directory for output files
> -use Create class and package usage pages
> -version Include @version paragraphs
> -author Include @author paragraphs"
> amongst other things, so I don't know why it should complain about it.)
> On the previous maven step I had some errors regarding checksums, but
> this seems more basic than something related to those (and in any case,
> no error was reported at the end of that, I just happened to see some
> "flash" by as the process was going through).
>
--
James
-------
http://macstrac.blogspot.com/
Open Source Integration
http://fusesource.com/