[ 
https://issues.apache.org/jira/browse/NETBEANS-2197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16945805#comment-16945805
 ] 

Thomas Zimmermann edited comment on NETBEANS-2197 at 10/7/19 11:38 AM:
-----------------------------------------------------------------------

Turns out there were many reasons this didn't work: NetBeans didn't look at the 
*-linux-javadoc.jar at all, the visible Javadoc was generated from the source 
jar. Even if NetBeans _had_  looked at the javadoc jar, it would not have 
understood the new HTML5 Javadoc format. I [opened a 
PR|https://github.com/apache/netbeans/pull/1548] to fix this and some other 
issues around JavaFX support, feel free to take a look.  


was (Author: zimmi):
Turns out there were many reasons this didn't work: NetBeans didn't look at the 
*-linux-javadoc.jar at all, the visible Javadoc was generated from the source 
jar. Even if NetBeans _had_  looked at the javadoc jar, it would not have 
understood the new HTML5 Javadoc format. I [opened a 
PR|https://github.com/apache/netbeans/pull/1548] to fix this and and some other 
issues around JavaFX support, feel free to take a look.  

> Missing code completion and Javadocs in maven projects with classifier.
> -----------------------------------------------------------------------
>
>                 Key: NETBEANS-2197
>                 URL: https://issues.apache.org/jira/browse/NETBEANS-2197
>             Project: NetBeans
>          Issue Type: Bug
>          Components: editor - Completion & Templates
>    Affects Versions: 11.0
>         Environment: All platforms
>            Reporter: Tobias Oelgarte
>            Priority: Major
>              Labels: maven, usability
>         Attachments: code-completion-failed.png, code-completion-ok.png
>
>
> If a maven artifact uses classifiers, then Netbeans isn't able to provide 
> code completion or to display Javadocs.
> To avoid duplication, sources and javadocs usually belong to the 'parent' 
> artifact, which has no classifier. But the actually used jar archive (the 
> library) resides within the artifact with classifier.
> A good example for this is JavaFX. The artifact 
> [javafx-base|http://central.maven.org/maven2/org/openjfx/javafx-base/11.0.2/] 
> is an empty shell and depending on the operating system the platform 
> dependent library is used, by utilizing classifiers. In the case of linux 
> this would be the _javafx-base-11.0.2-linux.jar_.
> Netbeans will not find the corresponding sources or javadoc archives, because 
> it looks for {color:#14892c}_javafx-base-11.0.2-linux-sources.jar_{color} and 
> {color:#14892c}_javafx-base-11.0.2-linux-javadoc.jar_{color}, but it won't 
> look for {color:#f79232}_javafx-base-11.0.2-sources.jar_{color} and 
> {color:#f79232}_javafx-base-11.0.2-javadoc.jar_{color}.
> As a temporary solution i created symlinks to the existing sources and 
> javadoc archives. But this solution also doesn't work as excepted. The 
> sources are found, but the Javadocs for a field or method can only be 
> displayed as long all parameters and return types belong to the same artifact.
> !code-completion-ok.png!
> !code-completion-failed.png!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Reply via email to