[jira] [Commented] (MJAVADOC-471) When aggregator filters out artifacts of current reactor projects, only the primary artifact is considered
[
https://issues.apache.org/jira/browse/MJAVADOC-471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16090490#comment-16090490
]
Matt Benson commented on MJAVADOC-471:
--
Right; I'm looking into it. I'd really like to make 3.0.0-final and should be
able to devote the time needed.
> When aggregator filters out artifacts of current reactor projects, only the
> primary artifact is considered
> --
>
> Key: MJAVADOC-471
> URL: https://issues.apache.org/jira/browse/MJAVADOC-471
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Components: javadoc
>Affects Versions: 2.10.4
>Reporter: Matt Benson
> Fix For: 3.0.0
>
> Attachments: MJAVADOC-471.patch.txt
>
>
> given project structure
> {code}
> foo-parent
> - foo-child-1
> - foo-child-2
> {code}
> If {{foo-child-2}} depends on the {{tests}} artifact of {{foo-child-1}} the
> build still breaks, despite the changes made for MJAVADOC-437 .
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (MJAVADOC-471) When aggregator filters out artifacts of current reactor projects, only the primary artifact is considered
[
https://issues.apache.org/jira/browse/MJAVADOC-471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16088272#comment-16088272
]
Robert Scholte commented on MJAVADOC-471:
-
This IT succeeds, don't think that's intended, right?
> When aggregator filters out artifacts of current reactor projects, only the
> primary artifact is considered
> --
>
> Key: MJAVADOC-471
> URL: https://issues.apache.org/jira/browse/MJAVADOC-471
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Components: javadoc
>Affects Versions: 2.10.4
>Reporter: Matt Benson
> Fix For: 3.0.0
>
> Attachments: MJAVADOC-471.patch.txt
>
>
> given project structure
> {code}
> foo-parent
> - foo-child-1
> - foo-child-2
> {code}
> If {{foo-child-2}} depends on the {{tests}} artifact of {{foo-child-1}} the
> build still breaks, despite the changes made for MJAVADOC-437 .
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (MJAVADOC-471) When aggregator filters out artifacts of current reactor projects, only the primary artifact is considered
[
https://issues.apache.org/jira/browse/MJAVADOC-471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15425564#comment-15425564
]
Matt Benson commented on MJAVADOC-471:
--
You might notice that given the example structure, you would expect that
{{foo-child-2}} would depend on {{foo-child-1:tests}} only in {{test}} scope,
and therefore that the problem reported would actually apply not to
{{aggregate}} but instead to {{test-aggregate}}. With this in mind, my
recommendation is that, additionally, {{AbstractJavadocMojo}} should filter
dependencies by scope and my forthcoming patch will reflect this.
> When aggregator filters out artifacts of current reactor projects, only the
> primary artifact is considered
> --
>
> Key: MJAVADOC-471
> URL: https://issues.apache.org/jira/browse/MJAVADOC-471
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Components: javadoc
>Affects Versions: 2.10.4
>Reporter: Matt Benson
>
> given project structure
> {code}
> foo-parent
> - foo-child-1
> - foo-child-2
> {code}
> If {{foo-child-2}} depends on the {{tests}} artifact of {{foo-child-1}} the
> build still breaks, despite the changes made for MJAVADOC-437 .
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
