Hmm, how very odd. I'm aware of all the javadoc warnings, and I haven't had the chance to see how to configure the plugin to avoid these. If I recall correctly they are nearly all to do with not recognising the @generated tag. But I'm not seeing any of the failures you have been encountering. Is anyone else seeing these? I guess not many people are trying to go through the whole exercise of rebuilding the binary distribution. I'm afraid I can't give an explanation at the moment. This is very useful testing for us, and if you or anyone else can give any assistance or pointers from your investigations that would be great. Fixing these issues is going to become important in the run up to the next release. It would be good to know the details of the versions of the key components you are using. I guess you are still using IBM JDK 1.4.2, yes? To complete the picture, what's the rest of your environment; linux version, maven version, surefire plugin version, etc?
Best Regards, Kelvin. On 10/01/07, Stanislaw T. Findeisen <[EMAIL PROTECTED]> wrote:
Yes Kelvin, it seems that it helped -- that is, the build goes further. It still fails however: [many lines with JavaDoc generation warnings...] [INFO] ---------------------------------------------------------------------------- [INFO] Building Tuscany SDO Implementation [INFO] task-segment: [package, javadoc:javadoc] [INFO] ---------------------------------------------------------------------------- [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. [INFO] Copying 6 resources [INFO] Copying 0 resource to META-INF [INFO] [compiler:compile] [INFO] Nothing to compile - all classes are up to date [INFO] [resources:testResources] [INFO] Using default encoding to copy filtered resources. [INFO] Copying 32 resources [INFO] [compiler:testCompile] [INFO] Nothing to compile - all classes are up to date [INFO] [surefire:test] [INFO] Repository: apache.snapshots(snap=true rel=true) http://people.apache.org/repo/m2-snapshot-repository [INFO] Repository: codehaus-snapshot(snap=true rel=true) http://snapshots.repository.codehaus.org [INFO] Repository: central(snap=false rel=true) http://repo1.maven.org/maven2 [INFO] Repository: apache.snapshots(snap=true rel=true) http://people.apache.org/repo/m2-snapshot-repository [INFO] Repository: codehaus-snapshot(snap=true rel=true) http://snapshots.repository.codehaus.org [INFO] Repository: central(snap=false rel=true) http://repo1.maven.org/maven2 [INFO] Surefire report directory: /home/worker/tuscany/sdo/impl/target/surefire-reports The java class is not found: org/apache/maven/surefire/booter/SurefireBooter [INFO] ------------------------------------------------------------------------ [ERROR] BUILD FAILURE [INFO] ------------------------------------------------------------------------ ... kelvin goodson wrote: > Stanislaw, > > I have tried unsuccessfully to reproduce the symptom you are describing. > However, I see from the documentation at > http://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-mojo.htmlthat > the maven javadoc plugin can be influenced to handle assert statements by > the inclusion of the <source>1.4</source> configuration element, so I have > updated the sdo/pom.xml and the sdo/impl/pom.xml to contain this element. > Can you let me know if this fixes your problem pleas? If so I will then > ensure that this switch is in force generally as appropriate. > > Regards, Kelvin. > > On 08/01/07, Stanislaw T. Findeisen <[EMAIL PROTECTED]> wrote: > >> >> Hi >> >> (1) I switched to IBM Java 1.4.2, and now have "build successful". >> >> Thank you all. >> >> (2) There is another issue however. This: >> >> 5) Execute: mvn package javadoc:javadoc assembly:assembly >> This will build the Tuscany SDO for Java binary distribution >> artefacts in the sdo/distribution/target >> directory. >> >> ([tuscany-top-directory]/sdo/BUILDING.txt) doesn't seem to work: >> >> [INFO] >> ------------------------------------------------------------------------ >> [ERROR] BUILD ERROR >> [INFO] >> ------------------------------------------------------------------------ >> [INFO] An error has occurred in JavaDocs report generation:Exit code: 1 >> - >> >> /home/worker/tuscany/sdo/impl/src/main/java/org/apache/tuscany/sdo/util/StAX2SAXAdapter.java:188: >> >> warning: as of release 1.4, assert is a keyword, and may not be used as >> an identifier >> assert reader.getEventType() == >> XMLStreamConstants.START_ELEMENT; >> ^ >> >> /home/worker/tuscany/sdo/impl/src/main/java/org/apache/tuscany/sdo/util/StAX2SAXAdapter.java:188: >> >> ';' expected >> assert reader.getEventType() == >> XMLStreamConstants.START_ELEMENT; >> ^ >> >> Command line was:/opt/IBMJava2-142/jre/../bin/javadoc @options @packages >> >> [INFO] >> ------------------------------------------------------------------------ >> >> Perhaps when using IBM Java one has to specify assertions in some >> different way? -- Leave this world better than it was when you were born. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
