Hi David, I've seen NPEs when generating the manual too if I run mvn -f openjpa-project/pom.xml -Pdocbook-profile clean verify. Replacing "clean verify" with process-sources seemed to resolve the problem. This isn't an ideal solution, but I wasn't able to gather any additional information. Mvn -e ... was less than enlightening. I did try rolling back to the previous version of the docbook plugin, 2.0.7 and that worked better for me (lots of warning / info messages but still better). I haven't checked the PDF for corruption though. I got a bit sidetracked on an issue with the distribution zip files. If 2.0.7 resolves the problem for you we should rollback the version for the time being. -mike On Wed, Jul 16, 2008 at 11:02 AM, David Ezzio wrote: > Hi Kevin, > > Thanks for the instructions on building the User Guide. > > I'm seeing problems in my three attempts thus far. During the two > failures, it doesn't build the html, and it gives a NullPointerException > when generating the PDF. During its one success, it generated the html but > the pdf was small and "corrupted." > > On my last try, I did a successful clean and install. Then followed your > instructions. Got the failure outcome. See attached console snippet. I'm > sync'ed to 1.1.x head. > > On the first try, it downloaded a bunch of jars and poms for the > repository. > > Any insights? > > Thanks, > > David > > ----------- console snippet ---------- > [INFO] > ------------------------------------------------------------------------ > [INFO] Reactor Summary: > [INFO] > ------------------------------------------------------------------------ > [INFO] OpenJPA ............................................... SUCCESS > [3.328s] > [INFO] OpenJPA Utilities ..................................... SUCCESS > [27.782s] > [INFO] OpenJPA Kernel ........................................ SUCCESS > [16.484s] > [INFO] OpenJPA JDBC .......................................... SUCCESS > [10.281s] > [INFO] OpenJPA JPA ........................................... SUCCESS > [4.938s] > [INFO] OpenJPA JPA JDBC ...................................... SUCCESS > [20:15.797s] > [INFO] OpenJPA XML Store ..................................... SUCCESS > [1.109s] > [INFO] OpenJPA Slice ......................................... SUCCESS > [23.016s] > [INFO] OpenJPA Aggregate Jar ................................. SUCCESS > [7.468s] > [INFO] OpenJPA Distribution .................................. SUCCESS > [14.219s] > [INFO] OpenJPA Persistence Examples .......................... SUCCESS > [1.469s] > [INFO] OpenJPA Integration Tests ............................. SUCCESS > [0.172s] > [INFO] OpenJPA Examples Integration Tests .................... SUCCESS > [1.187s] > [INFO] OpenJPA JPA TCK Integration Tests ..................... SUCCESS > [0.422s] > [INFO] > ------------------------------------------------------------------------ > [INFO] > ------------------------------------------------------------------------ > [INFO] BUILD SUCCESSFUL > [INFO] > ------------------------------------------------------------------------ > [INFO] Total time: 22 minutes 8 seconds > [INFO] Finished at: Wed Jul 16 11:46:04 EDT 2008 > [INFO] Final Memory: 26M/87M > [INFO] > ------------------------------------------------------------------------ > > C:\code\svn\RW_OpenJPA1-1Branch>mvn -f openjpa-project/pom.xml > process-resources -Pdocbook-profile > [INFO] Scanning for projects... > [INFO] > ---------------------------------------------------------------------------- > [INFO] Building OpenJPA Distribution > [INFO] task-segment: [process-resources] > [INFO] > ---------------------------------------------------------------------------- > [INFO] [docbkx:generate-pdf {execution: build-pdf-doc}] > [INFO] Processing manual.xml > [INFO] > ------------------------------------------------------------------------ > [ERROR] BUILD ERROR > [INFO] > ------------------------------------------------------------------------ > [INFO] Failed to transform document. > > Embedded error: java.lang.NullPointerException > [INFO] > ------------------------------------------------------------------------ > [INFO] For more information, run Maven with the -e switch > [INFO] > ------------------------------------------------------------------------ > [INFO] Total time: 35 seconds > [INFO] Finished at: Wed Jul 16 11:46:55 EDT 2008 > [INFO] Final Memory: 14M/64M > [INFO] > ------------------------------------------------------------------------ > > C:\code\svn\RW_OpenJPA1-1Branch>mvn -version > Maven version: 2.0.4 > > C:\code\svn\RW_OpenJPA1-1Branch>java -version > java version "1.5.0_14" > Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_14-b03) > Java HotSpot(TM) Client VM (build 1.5.0_14-b03, mixed mode) > > C:\code\svn\RW_OpenJPA1-1Branch> > > ----------- end console snippet -------- > > > Kevin Sutter wrote: > >> Shoot, I forgot to hit "reply all"... :-) >> >> ---------- Forwarded message ---------- >> From: Kevin Sutter >> Date: Wed, Jul 16, 2008 at 9:03 AM >> Subject: Re: Merging 1.1.x changes into mainline, was: svn commit: r676592 >> >> -/openjpa/branches/1.1.x/openjpa-project/src/doc/manual/ref_guide_dbsetup.xml >> To: David Ezzio >> >> >> Thanks, David, for the reply. I can understand your need to ensure that >> the >> changes are solid. As far as the docbook is concerned, you can build that >> yourself and see if you messed up the tags or not. The instructions are >> in >> the pom.xml, but here's what you can do to build it: >> >> >> >> As far as merging the 1.1.x branch back into the mainline. That's how >> Patrick was first maintaining that branch until it became "real". Patrick >> has since migrated all of the 1.1.x changes back into trunk. I would >> expect >> all subsequent changes going into 1.1.x (or 1.0.x) would immediately get >> moved to trunk as well. If we don't follow this practice, then it would >> be >> very easy for our branches and trunk to get seriously out of whack. >> Customers moving from one release to another wouldn't know whether fixes >> from an older release were also resolved in the next release. >> >> Thanks for looking into this and starting to resolve the situation. >> >> Kevin >> >> On Wed, Jul 16, 2008 at 8:44 AM, David Ezzio wrote: >> >> Hi Kevin, >>> >>> You can always ask! I have a multipart answer. One: I'm not 100% sure >>> if >>> the changes are solid. I know they are substantial. I have been waiting >>> for the snapshots of the 1.1.x line to come back on line so that I can >>> see >>> whether I messed up any of the docbook (I'm assuming that's what we're >>> using) tags. Two: I assumed, perhaps naively, that there was a plan to >>> merge the 1.1.x line into the mainline, and I was hoping, perhaps >>> somewhat >>> optimistically, that I might not be part of that plan. >>> >>> So, it looks like I need to learn about the plan and my role in it. >>> >>> Cheers, >>> >>> David >>> >>> >>> Kevin Sutter wrote: >>> >>> David, >>>> Are you noticing these type of messages? A few of the OpenJPA >>>> developers >>>> (myself included) have noticed that your committing some solid changes >>>> into >>>> the 1.1.x branch, but not back into trunk. We should be trying to keep >>>> trunk up-to-date with the service branches (1.0.x, 1.1.x, etc) -- if the >>>> changes apply. And, in most cases, they do apply. Can I ask what your >>>> plans >>>> are for synching up trunk with 1.1.x? >>>> >>>> Thanks! >>>> Kevin >>>> >>>> ---------- Forwarded message ---------- >>>> From: ** > >>>> Date: Mon, Jul 14, 2008 at 9:41 AM >>>> Subject: Re: svn commit: r676592 >>>> >>>> -/openjpa/branches/1.1.x/openjpa-project/src/doc/manual/ref_guide_dbsetup.xml >>>> To: dev@openjpa.apache.org >>>> >>>> >>>> Shouldn't these type of changes also be put into trunk? >>>> >>>> Kevin >>>> >>>> Sent from my Verizon Wireless BlackBerry >>>> >>>>