Sorry I didn't see this sooner, but I don't remember the special sauce it took/takes to build javadoc. I seem to recall cursing a lot the last time I had to do it.
On Mon, Apr 20, 2015 at 1:14 PM, Mark Struberg <[email protected]> wrote: > One more question. > How do you usually build the javadocs? > Probably we meet on #openjpa in irc or a hangout and publish the docs from > the tag together? > And of course document it in our BUILDING.txt file. > > LieGrue, > strub > > > Am 20.04.2015 um 19:45 schrieb Mark Struberg <[email protected]>: > > > > Hi Kevin! > > > > Yes, that was pretty broken with default values. The reason is that a > normal release simply cannot provide an 'aggregate' javadoc, because needs > all the jars to be installed in your local m2 repo already. Same happens > for the cumulated site. > > > > The way I did set it up now is that we create javadoc one per module. So > if you add openjpa as dependency then you will get all the source jars and > all the javadocs per module. > > > > Once the release is done we need to publish the javadoc + site from the > tag by building with the apropriate maven profiles. > > > > LieGrue, > > strub > > > >> Am 20.04.2015 um 16:38 schrieb Kevin Sutter <[email protected]>: > >> > >> Hi Mark, > >> Thanks for doing this release! > >> > >> Question: What about the manual and javadocs? I saw your other notes > >> about some issues with building the docs, but I thought you had resolved > >> them. And, I do like to verify javadocs for a release. The rest of the > >> artifacts look good thus far! > >> > >> Thanks, > >> Kevin > >> > >> On Mon, Apr 20, 2015 at 4:30 AM, Romain Manni-Bucau < > [email protected]> > >> wrote: > >> > >>> +1 (non binding) > >>> > >>> > >>> Romain Manni-Bucau > >>> @rmannibucau <https://twitter.com/rmannibucau> | Blog > >>> <http://rmannibucau.wordpress.com> | Github < > >>> https://github.com/rmannibucau> | > >>> LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber > >>> <http://www.tomitribe.com> > >>> > >>> 2015-04-19 17:03 GMT+02:00 Mark Struberg <[email protected]>: > >>> > >>>> It's a great pleasure to call a VOTE for releasing Apache > OpenJPA-2.4.0. > >>>> > >>>> OpenJPA-2.4.0 implements the JPA-2.0 specification. > >>>> > >>>> The staging repository can be found here: > >>>> > >>> > https://repository.apache.org/content/repositories/orgapacheopenjpa-1000/ > >>>> > >>>> The Release Notes can be found in the file > >>>> openjpa-project/RELEASE_NOTES.html and online under: > >>>> > >>>> > >>> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310351&version=12325298 > >>>> > >>>> The SVN source TAG is (1674626): > >>>> https://svn.apache.org/repos/asf/openjpa/tags/openjpa-parent-2.4.0/ > >>>> > >>>> The source release can be found here: > >>>> > >>>> > >>> > https://repository.apache.org/content/repositories/orgapacheopenjpa-1000/org/apache/openjpa/openjpa-parent/2.4.0/openjpa-parent-2.4.0-source-release.zip > >>>> > >>>> The binary release is here: > >>>> > >>>> > >>> > https://repository.apache.org/content/repositories/orgapacheopenjpa-1000/org/apache/openjpa/apache-openjpa/2.4.0/apache-openjpa-2.4.0-binary.zip > >>>> > >>>> My Key can be found here > >>>> https://svn.apache.org/repos/asf/openjpa/KEYS > >>>> > >>>> > >>>> The VOTE will be open for 72 hours. > >>>> [+1] approve > >>>> [+0] meh, don't care > >>>> [-1] stop, I've found a ${fish} in there > >>>> > >>>> > >>>> txs and LieGrue, > >>>> your OpenJPA team > >>> > > > > -- *Rick Curtis*
