See https://github.com/olamy/JavadocUpdaterTool
I added a maven build and a mojo.
IANAL so I don't know if we can integrate the source of
JavadocFixTool.java in javadoc plugin (
https://github.com/olamy/JavadocUpdaterTool/blob/master/LICENSE )
2013/6/20 sebb seb...@gmail.com:
On 19 June 2013
On 20 June 2013 12:15, Olivier Lamy ol...@apache.org wrote:
See https://github.com/olamy/JavadocUpdaterTool
I added a maven build and a mojo.
IANAL so I don't know if we can integrate the source of
JavadocFixTool.java in javadoc plugin (
FYI, I just sent an email on the jug-leaders ML to ask for clarification
about the license aspect by Oracle.
Let's hope this won't be dead letter.
Cheers
2013/6/20 sebb seb...@gmail.com
On 20 June 2013 12:15, Olivier Lamy ol...@apache.org wrote:
See
On 20 June 2013 13:08, sebb seb...@gmail.com wrote:
On 20 June 2013 12:15, Olivier Lamy ol...@apache.org wrote:
See https://github.com/olamy/JavadocUpdaterTool
I added a maven build and a mojo.
IANAL so I don't know if we can integrate the source of
JavadocFixTool.java in javadoc plugin (
2013/6/20 sebb seb...@gmail.com:
On 20 June 2013 12:15, Olivier Lamy ol...@apache.org wrote:
See https://github.com/olamy/JavadocUpdaterTool
I added a maven build and a mojo.
IANAL so I don't know if we can integrate the source of
JavadocFixTool.java in javadoc plugin (
On 20 June 2013 13:21, Olivier Lamy ol...@apache.org wrote:
2013/6/20 sebb seb...@gmail.com:
On 20 June 2013 12:15, Olivier Lamy ol...@apache.org wrote:
See https://github.com/olamy/JavadocUpdaterTool
I added a maven build and a mojo.
IANAL so I don't know if we can integrate the source of
I'm +1 with you on the fact that this code should be included after each
javadoc goal.
I guess they agree too,
but I *think* this is just something Olivier and the Maven PMC cannot
afford integrating this code into the maven-javadoc-plugin without being
200% sure this isn't going to be a license
On 20 June 2013 14:20, Baptiste MATHUS bmat...@batmat.net wrote:
I'm +1 with you on the fact that this code should be included after each
javadoc goal.
I guess they agree too,
but I *think* this is just something Olivier and the Maven PMC cannot
afford integrating this code into the
On 20 Jun 2013, at 15:19, sebb wrote:
On 20 June 2013 14:20, Baptiste MATHUS bmat...@batmat.net wrote:
I'm +1 with you on the fact that this code should be included after each
javadoc goal.
I guess they agree too,
but I *think* this is just something Olivier and the Maven PMC cannot
https://issues.apache.org/jira/browse/LEGAL-171
On 20 June 2013 15:35, Stuart McCulloch mccu...@gmail.com wrote:
On 20 Jun 2013, at 15:19, sebb wrote:
On 20 June 2013 14:20, Baptiste MATHUS bmat...@batmat.net wrote:
I'm +1 with you on the fact that this code should be included after each
I expect you have all see the news about the Javadoc javascript bug.
It's going to take a long time for everyone to update their Java
installations to Java 1.7 u25. Likewise for builds that need to use
other Java versions, tweaking poms so Java 7 is used for Javadocs
whilst still maintaining
Hi,
I think the best way to track this is to file a JIRA ticket on
http://jira.codehaus.org/browse/MJAVADOC
Btw, we might be interested by
https://github.com/AdoptOpenJDK/JavadocUpdaterTool/blob/master/src/main/java/JavadocFixTool.java
Cheers
2013/6/19 sebb seb...@gmail.com
I expect you
On 19 June 2013 22:40, Baptiste MATHUS bmat...@batmat.net wrote:
Hi,
I think the best way to track this is to file a JIRA ticket on
http://jira.codehaus.org/browse/MJAVADOC
Well OK, I can raise an enhancement request there too.
Btw, we might be interested by
13 matches
Mail list logo
