[
https://issues.apache.org/jira/browse/MJAVADOC-617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17532713#comment-17532713
]
Phil commented on MJAVADOC-617:
-------------------------------
I'm unsure when the fix was included, but this is no longer causing me problems
in 3.3.2.
> aggregate-jar does nothing if aggregator modules are referenced using
> relative pathes and are not in sub folders (
> ------------------------------------------------------------------------------------------------------------------
>
> Key: MJAVADOC-617
> URL: https://issues.apache.org/jira/browse/MJAVADOC-617
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Affects Versions: 3.1.0, 3.1.1
> Reporter: Reto Weiss
> Priority: Major
> Attachments: fix.zip
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> If an aggregator project has modules that are not located in sub folders and
> are referenced using relative pathes (e.g. "../project1") then the javadoc
> aggregate-jar does nothing.
> It does not fail but no javadoc is generated at all.
> This works with 3.0.1.
> See attached Zip File with three projects all, project1 and project2. Project
> all is the aggregator project. It references project 1 and project 2 with
> ../project1 and ../project2
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
