Was this moved to Needs Review by mistake?
(There are no comments or notes explaining what was done.)

Changes Summary:
1. Corrected parent pom parameter as it was no longer compiling.
2. Fixed problems in Javadocs like missing tags, syntax error, malformed HTML etc.
3. Added command to build javadoc in default pipeline - ( mvn clean install javadoc:jar -D skipTests=false) and commands to copy javadoc jars to downloads directory

Files changed:
bitbucket-pipelines.yml
genoviz_sdk/src/main/java/com/affymetrix/genoviz/bioviews/MapGlyphFactory.java
genoviz_sdk/src/main/java/com/affymetrix/genoviz/glyph/AbstractResiduesGlyph.java
genoviz_sdk/src/main/java/com/affymetrix/genoviz/glyph/AlignmentGlyph.java
genoviz_sdk/src/main/java/com/affymetrix/genoviz/glyph/AxisGlyph.java
genoviz_sdk/src/main/java/com/affymetrix/genoviz/glyph/ColorSepGlyph.java
genoviz_sdk/src/main/java/com/affymetrix/genoviz/glyph/FlyPointLinkerGlyph.java
genoviz_sdk/src/main/java/com/affymetrix/genoviz/parser/ContentParser.java
genoviz_sdk/src/main/java/com/affymetrix/genoviz/widget/NeoAssembler.java
pom.xml

Please find the commit below for review:
https://bitbucket.org/srishtitiwari/genoviz-sdk/commits/eb85e3467de50e2112cbd01323a60ab7f7da4e51

Change request:

• Add javadoc plugin to the POM.xml so that it will build the javadoc jar file as part of the default lifecycle
• Check that when you run "mvn install" the javadocs get created and added to your local .m2 (for extra awesomeness, check that you can now navigate to the javadocs for GenoViz methods and classes.)
• Change the mvn commands in the bitbucket pipelines yml file to "mvn install" (I'm pretty sure we don't need "clean")

If we ever start developing GenoViz SDK, then we will move the javadoc plugin jar task into a separate profile (out of the default profile) to allow for building code without building the javadoc jar. But for now, we should compile the library and the javadoc jar files during the default lifecycle. Also, if we do this, then I can run the "deploy to nexus" custom pipeline and the javadocs will get released along with the compiled code and source code.

Link showing how to configure javadoc plugin in a POM.xml:

https://mkyong.com/maven/generate-javadoc-jar-for-maven-based-project/

Hi Professor, I have made changes accordingly. Please have a look.

https://bitbucket.org/srishtitiwari/genoviz-sdk/branch/IGBF-2228#diff

Please check: Is the maven javadoc plugin already included in the super POM? If yes, you do not need to declare it in the Plugins section.

Please submit PR.

Pull Request Submitted:

https://bitbucket.org/lorainelab/genoviz-sdk/pull-requests/18/igbf-2228/diff

I am able to open the javadocs..