Javadoc with new build [was Re: Build error on OSX]
Marc Petit-Huguenin
marc at petit-huguenin.org
Sat Oct 27 15:14:24 PDT 2012
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
The attached patch contains an ugly workaround to build the javadoc from the
new build (you may need to run "make docs" twice).
That come too late for me - as now that MapStream is no longer in the API, JDK
1.8 becomes useless for my projects - but hopefully this will help someone else.
On 09/29/2012 11:12 AM, Mike Duigou wrote:
> Unfortunately the version of the new build files currently used by lambda
> do not include javadoc support. It is still possible to build the javadoc
> using the old build process. This will be fixed in the next sync with jdk8
> (which already has such support).
>
> Mike
>
> On Sep 29 2012, at 11:07 , Marc Petit-Huguenin wrote:
>
> On 09/23/2012 11:16 AM, Mike Duigou wrote:
>>>> This looks like a problem with the old build process.
>>>>
>>>> For the lambda repo we've almost entirely shifted over to the much
>>>> simpler and faster build-infra build system. This is also happening
>>>> because we expect that the old (existing) build system will be
>>>> retired in jdk8 quite soon.
>>>>
>>>> cd common/makefiles sh ../autoconf/configure
>>>> --with-boot-jdk=/Library/Java/JavaVirtualMachines/jdk1.7.0_07.jdk/Contents/Home
>>>>
>>>>
>
>>>>
make images
>>>>
>
> I am not able to build the javadoc with the new process:
>
> cd common/makefiles sh ../autoconf/configure --enable-docs make images
>
> Anything I missed?
>
> Thanks.
>
>
- --
Marc Petit-Huguenin
Email: marc at petit-huguenin.org
Blog: http://blog.marc.petit-huguenin.org
Profile: http://www.linkedin.com/in/petithug
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iQIcBAEBCAAGBQJQjFy+AAoJECnERZXWan7EqLUP/0LDPiwL51ldw0rMwFPKjLJy
ma1R6U500ZaapfupubTnu3v6JxFlUXgktvkN60uzsBv3Z1rPA4LqxwfwIWl/qzkJ
oIGV4j5LXI+/IIrHfHx/RnWmJOQpF83FlS5UzTlnAR/NGq19Z0G+aBQkN+ev6GW6
OUp19eLyf5qcOcBm8M2Z81Ay5MkSquUuGOLbeQ8+QWoTSL/shCSUQLLFyKS3mrp1
y++k0//VeAR/fd1XvsnxO1XALv4bwrydt8J0PAylys0I6smMscSENlBuHjecGmFG
bSp/+YDLU/3Fs0Xa8XyuAmGqQTGQ2VoVRwWwkVW5SazmH3+gFnMkchfkV3/rCUNR
HNBOtMu806MDnsq5EO64XbISejVfB8FQu9ZKaFhFpMLr4ZjIgAB198SnOYEPMxyz
kBtQAZJXmA1qLTxWGUaro10cF6RlKD2LctzThqneXN6LsDq9kcBiIowUfW8knJNt
Sx6bSfvT6hpI6u31DPtgvmH0Hi9vLIFUuxztBKPVma+k1ubm5uJ+EJchURhNzYM6
m9jxTq0X109JjkZ0Ke/haVW9w2t+YA1Y9m6ZxvCc1WXUX3UeSVswlbVnyloczlav
VIAKN8KISuKSQ7pWtq5+TRuNJGMT6S4PewQEpmYntYI4AGE8qYWEgh1pZp3yWdcI
QuNhgeRQI9Rmx+KAfjPe
=FY7v
-----END PGP SIGNATURE-----
More information about the lambda-dev
mailing list