[
https://issues.apache.org/jira/browse/MJAVADOC-651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jin Kwon updated MJAVADOC-651:
------------------------------
Description:
Recently, I found myself that I have no public/projected classes in my
{{src/test/java}} directory.
Nevertheless the basic/default rule of exposure I already know, IntelliJ IDEA
recommends this way.
And I failed to find a way to control the {{show}} property as successfully
separated from {{main}} and {{test}} in both {{default-cli}}(cmd) and
{{default-test-aggregate-no-fork}}(site).
was:
Recently, I found myself that I have no public/projected classes in my
{{src/test/java}} directory.
Nevertheless the basic/default rule of exposure I already know, IntelliJ IDEA
recommends this way.
And I failed to find a way to control the {{show}} property as successfully
separated from {{main}} and {{test}} in both {{default-cli}}(cmd) and
{{test-aggregate-no-fork}}(site).
> Separate visibility control for main and test
> ---------------------------------------------
>
> Key: MJAVADOC-651
> URL: https://issues.apache.org/jira/browse/MJAVADOC-651
> Project: Maven Javadoc Plugin
> Issue Type: New Feature
> Affects Versions: 3.2.0
> Reporter: Jin Kwon
> Priority: Major
>
> Recently, I found myself that I have no public/projected classes in my
> {{src/test/java}} directory.
> Nevertheless the basic/default rule of exposure I already know, IntelliJ IDEA
> recommends this way.
> And I failed to find a way to control the {{show}} property as successfully
> separated from {{main}} and {{test}} in both {{default-cli}}(cmd) and
> {{default-test-aggregate-no-fork}}(site).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
