that works because OpenJDK uses module-source-path, i.e.
src//<*.java>
Maven uses source-path because it matches exactly one module , i.e.
src/main/java/<*.java>
Aggregator for modules requires to make use of module-source-paths.
I guess we need to consider to make use of symbolic links :(
t
On 2017-11-18T17:44:23 +0100
Hervé BOUTEMY wrote:
> JDK javadoc seems to cover the "aggregated javadocs" scenario: in Java 9
> terms, that's "multi-modules" = exactly the case for JDK 9 javadoc [1]
> I don't know what's the command line to produce this, but looks feasible from
> javadoc side
>
I was actually going to ask on the list eventually. Tried using it with -B
to no success a few days ago.
I've also had no luck finding where this option is documented on the maven
site.
The only place to look was in the Jira and PR, but those mostly have the
syntax that's not actually what was imp
JDK javadoc seems to cover the "aggregated javadocs" scenario: in Java 9
terms, that's "multi-modules" = exactly the case for JDK 9 javadoc [1]
I don't know what's the command line to produce this, but looks feasible from
javadoc side
Regards,
Hervé
[1] https://docs.oracle.com/javase/9/docs/ap
Le samedi 18 novembre 2017, 17:18:06 CET Mark Raynsford a écrit :
> On 2017-11-18T16:14:04 +
>
> Mark Raynsford wrote:
> > Presumably, with the module-info.java files
> > excluded, it reverts back to plain classpath style JavaDoc.
>
> Actually, it results in sort of weird looking JavaDoc tha
On 2017-11-18T16:14:04 +
Mark Raynsford wrote:
> Presumably, with the module-info.java files
> excluded, it reverts back to plain classpath style JavaDoc.
Actually, it results in sort of weird looking JavaDoc that only
contains a single module, and claims that all packages are in
that module:
On 2017-11-18T17:04:12 +0100
"Robert Scholte" wrote:
> That's similar to MJAVADOC-479[1]
>
> Seems like all Java 9 issues are not resolved yet.
> I don't mind canceling the vote if we can fix this as well.
>
> thanks,
> Robert
>
> [1] https://issues.apache.org/jira/browse/MJAVADOC-479
Yeah, t
ello!
I'd like to vote on this issue, but I still have a remaining problem
and am not sure if it's because the plugin is broken due to the new
module changes, or just because my project setup is slightly
unusual.
See here:
https://github.com/io7m/maven-javadoc-bug-20171118
The &q
Hello!
I'd like to vote on this issue, but I still have a remaining problem
and am not sure if it's because the plugin is broken due to the new
module changes, or just because my project setup is slightly
unusual.
See here:
https://github.com/io7m/maven-javadoc-bug-20171118
The
Hi,
MNG-6220[1] was incomplete, which will be fixed with MNG-6296[2].
Commit:
https://git1-us-west.apache.org/repos/asf?p=maven.git;a=commit;h=b2afafe5
CI:
https://builds.apache.org/view/M-R/view/Maven/job/maven-3.x-jenkinsfile/job/MNG-6296/
Who wants to second this?
thanks,
Robert
[
Hi,
We solved 27 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317529&version=12330875&styleName=Text
There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=project%20%3D%2012317529%20AND%20status%20%3D%20Open%20ORDER%20BY%20key%2
Issue found related to a Maven multimodule projects and Java 9 module
descriptors.
This needs to be fixed for 3.0.0.
thanks,
Robert
On Fri, 17 Nov 2017 18:37:16 +0100, Robert Scholte
wrote:
Hi,
We solved 26 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=123175
Hi Mark,
thanks for testing. I can confirm the problem.
I'll cancel the vote and roll out another release based on your patch.
thanks,
Robert
On Sat, 18 Nov 2017 12:46:51 +0100, Mark Raynsford
wrote:
On 2017-11-17T19:00:54 +
Mark Raynsford wrote:
-1 (non-binding)
The staged versio
found something that can explain: when using the real url starting with /
components/, the CGI script works [4]
But not when using the user-visible url (that uses .htaccess rewrite rules)
[5]
INFRA Jira issue opened: https://issues.apache.org/jira/browse/INFRA-15513
Regards,
Hervé
[4] https:/
On 2017-11-17T19:00:54 +
Mark Raynsford wrote:
> -1 (non-binding)
>
> The staged version still fails with a basic module setup:
>
> https://github.com/io7m/maven-javadoc-bug-20171117
I've submitted a PR that I believe fixes the issue, but I'm not sure if
it's already too late to get it i
GitHub user io7m opened a pull request:
https://github.com/apache/maven-plugins/pull/137
[MJAVADOC-489] Find the main module descriptor
The existing code was checking for the existence of a file
"src/main/module-info.java" relative to the current directory. The
problem is tha
GitHub user io7m opened a pull request:
https://github.com/apache/maven-plugins/pull/136
[MDEP-584] Update plexus-utils to 3.1.0
This updates the plexus-utils dependency to 3.1.0. It corrects four
unit tests that were failing due to new behaviour in 3.1.0: It appears
that the
Github user io7m closed the pull request at:
https://github.com/apache/maven-plugins/pull/135
---
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
18 matches
Mail list logo
