• 设为首页
  • 点击收藏
  • 手机版
    手机扫一扫访问
    迪恩网络手机版
  • 关注官方公众号
    微信扫一扫关注
    迪恩网络公众号

phasebash/jsdoc3-maven-plugin: End Of Life: An automatic documentation generator ...

原作者: [db:作者] 来自: 网络 收藏 邀请

开源软件名称(OpenSource Name):

phasebash/jsdoc3-maven-plugin

开源软件地址(OpenSource Url):

https://github.com/phasebash/jsdoc3-maven-plugin

开源编程语言(OpenSource Language):

Java 99.2%

开源软件介绍(OpenSource Introduction):

jsdoc3-maven-plugin

An automatic documentation generator for JavaScript within the Maven Reporting lifecycle.

Public Service Announcement

A lot has changed since the introduction of this plugin many many years ago. Docker was still very new and not widely available, Node.js was still at 0.x.x, Gradle was not in wide use and didn't have a wide array of plugins available as are today.

Given today's dev-ops landscape, this plugin has no reason to exist. Please consider one of the following options:

  • Use jsdoc with plain-old Node.js
  • Use Docker and a project local Dockerfile to contain your Node.js dependencies
  • Alternatively consider using Gradle and the gradle-node-plugin to control your Node.js dependency

Other possibilities exist, but I'm sure you get where I'm going. The need to write Maven plugins for all tool integrations is a thing of the past, and I strongly recommend using common tools available to the community.

But wait, I have a very neat Maven build, and you're asking me to pollute it with Node.js? If this idea appauls you, consider adding another step in your CI/CD pipeline and contain the Node.js bits there.

The below exists for legacy reasons.

What is the jsdoc3-maven-plugin?

The jsdoc3-maven-plugin is a maven plugin and maven report built for the purposes of generating jsdoc along with a Maven Build, or Maven Reporting lifecycle. By default, the plugin will bind to the site phase when used as a Maven Mojo or Maven Report, though this is configurable as with any other Maven plugin with goals.

Why Maven Mojo and Maven Report?

It has been requested by enough users that we should provide both a Maven Mojo for people who prefer to generate documentation using the command line or don't care about producing a complete site, while other users prefer to simply generate a complete Maven Site with JSDoc included.

Getting Started

The following examples enumerate the most common POM configurations for the jsdoc3-maven-plugin. This plugin is made available through Sonatype and is synchronized with the central Maven repository.

Release

The current release version is 1.2.0, using jsdoc3 3.3.2.

Current Status

Build Status

Example Configurations

The jsdoc3-maven-plugin can fit into both the Maven Build and Maven Report lifecycle and offers both a Mojo and MavenReport which provide the same API. The snippets of POM configuration below can be placed both within reporting.plugins as well as build.plugins.

Example POM: Recurse subdirectories only

<reporting>
    <plugins>
        <plugin>
            <groupId>com.phasebash.jsdoc</groupId>
            <artifactId>jsdoc3-maven-plugin</artifactId>
            <version>1.2.0</version>
            <configuration>
                <recursive>true</recursive>
                <directoryRoots>
                    <directoryRoot>${basedir}/src/main/webapp/resources/js</directoryRoot>
                    <directoryRoot>${basedir}/src/main/javascript</directoryRoot>
                </directoryRoots>
            </configuration>
        </plugin>
    </plugins>
</reporting>

Example POM: Recurse subdirectories + errant files

<reporting>
    <plugins>
        <plugin>
            <groupId>com.phasebash.jsdoc</groupId>
            <artifactId>jsdoc3-maven-plugin</artifactId>
            <version>1.2.0</version>
            <configuration>
                <recursive>true</recursive>
                <directoryRoots>
                    <directoryRoot>${basedir}/src/main/webapp/resources/js</directoryRoot>
                    <directoryRoot>${basedir}/src/main/javascript</directoryRoot>
                </directoryRoots>
                <sourceFiles>
                    <sourceFile>${baseDir}/src/main/resources/js/classic.js</sourceFile>
                </sourceFiles>
            </configuration>
        </plugin>
    </plugins>
</reporting>

Example POM: Cherry pick

<reporting>
    <plugins>
        <plugin>
            <groupId>com.phasebash.jsdoc</groupId>
            <artifactId>jsdoc3-maven-plugin</artifactId>
            <version>1.2.0</version>
            <configuration>
                <sourceFiles>
                    <sourceFile>${baseDir}/src/main/resources/js/menu.js</sourceFile>
                    <sourceFile>${baseDir}/src/main/resources/js/header.js</sourceFile>
                    <sourceFile>${baseDir}/src/main/resources/js/content.js</sourceFile>
                    <sourceFile>${baseDir}/src/main/resources/js/ads.js</sourceFile>
                </sourceFiles>
            </configuration>
        </plugin>
    </plugins>
</reporting>

Commandline

Run the Mojo, this requires that the plugin be added via pluginManagement.

mvn clean jsdoc3:jsdoc3

Otherwise, you may use the maven site (as the examples above are configured):

mvn clean site

Mojo Parameters

  • directoryRoots - File[]: An Array of Files which will be used as directory roots, any file within this directory will be included into the final jsdoc argument list.
  • recursive (Optional) - Boolean: A flag to indicate whether or not all directory roots should be searched and all files included recursively.
  • lenient (Optional) - Boolean: A flag to indicate whether or not the generator should tolerate errors (false), or keep plodding along despite them (true).
  • sourceFiles (Optional) - File[]: An Array of Files which will be included into the final jsdoc argument list.
  • outputDirectory (Optional) - File: The place where jsdoc should be written. default: "${project.build.directory}/site/jsdoc"
  • includePrivate (Optional) - Boolean: A flag to indicate whether @private symbols are included in the generated documentation.
  • tutorialsDirectory (Optional) - File: A file indicating where jsdoc tutorial resources can be found.
  • templateDirectory (Optional) - File: A file inddicating where jsdoc templates resources can be found.
  • configFile (Optional) - File: A configuration file to be passed to jsdoc for more detailed project configuration.

System Properties

  • maven.jsdoc.skip - Boolean: A flag to skip JSDoc reporting. Utilized by both the Maven Report and Mojo.

Questions, Feedback?

Feel free to submit an issue ticket through github or contact me directly. I will help you.

License

The jsdoc3-maven-plugin has been released under Apache 2.0 as per all it's dependencies.

Enhancements

  • Consolidate duplicated Plexus parameters between Mojo and Maven Report (using Groovy)
  • Support remaining command line arguments

Limitations

  • Test coverage could be better
  • Missing Mojo integration tests (so fix it already)



鲜花

握手

雷人

路过

鸡蛋
该文章已有0人参与评论

请发表评论

全部评论

专题导读
热门推荐
阅读排行榜

扫描微信二维码

查看手机版网站

随时了解更新最新资讯

139-2527-9053

在线客服(服务时间 9:00~18:00)

在线QQ客服
地址:深圳市南山区西丽大学城创智工业园
电邮:jeky_zhao#qq.com
移动电话:139-2527-9053

Powered by 互联科技 X3.4© 2001-2213 极客世界.|Sitemap