cayenne-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mike Kienenberger <>
Subject Re: javadoc security flaw
Date Tue, 09 Jul 2013 13:20:24 GMT
LUCENE's issue stated in the comments that the Oracle tool shouldn't
be used (apparently it can be integrated with maven).   It also stated
that there was a simple way to duplicate the functionality using
maven, but I didn't immediately see what that was:

Here's the thread it had on that:

This seems to point to
as one solution later on in the comments

Which seems to be a matter of updating the maven-javadoc-plugin
version from 2.9 to 2.9.1.   Maybe that's all we need as well?   If
not, I'm guessing you could diff the changes between versions 2.9 to
2.9.1 and find the solution in a maven environment?

--- maven/pom/trunk/asf/pom.xml 2013/06/28 09:11:27 1497691
+++ maven/pom/trunk/asf/pom.xml 2013/06/28 09:14:58 1497692
@@ -184,7 +184,7 @@
-          <version>2.9</version>
+          <version>2.9.1</version>

On Tue, Jul 9, 2013 at 9:12 AM, Mike Kienenberger <> wrote:
>> On Jul 9, 2013, at 2:57 AM, Aristedes Maniatis <> wrote:
>>> Did we change the javadoc build process to avoid the javadoc security flaw recently
discovered? I patched the website javadocs, but I'm not sure if we also have to change something
in our maven build process or upgrade some plugin.
> On Tue, Jul 9, 2013 at 2:12 AM, Andrus Adamchik <> wrote:
>> Me neither. Probably some research is in order. Should we take this to a separate
> Maybe you can copy what some other project has done.
> I saw a notice about it for tomcat but I believe it is built with ant.
> That notice pointed to Lucene, but it says it was built with ivy.
> So I didn't find a pointer to a maven-based fix.

View raw message