Upstream software project

vim-javabrowser

The javabrowser plugin for VIM editor

About vim-javabrowser

The javabrowser plugin for VIM editor

This project links 2 native package records across 2 recorded operating-system releases. Compare the retained versions and architectures below, then open the package for your own release.

These are catalog observations, not a guarantee of installation, compatibility, or upstream support.

Project pictures and package coverage

Fedora 43: 1 package records; Fedora 44: 1 package records. Catalog coverage diagram, not an application screenshot.vim-javabrowser: recorded package coverageFedora 431 recordsFedora 441 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
vim-javabrowser
Publisher
Not authoritatively mapped
Native package records
2
Operating systems
fedora-43, fedora-44
License expression
Vim
Source repository
Not reported

Source-reported description

The fullest retained description is shown with its source. Distribution packaging descriptions may include downstream details.

This script is SPECIFICALLY tailored for Java language. So, it shows structure of the Java file starting with classes defined within it and NOT in a general tag structure. It also has a nice syntax to show the class members in UML format.

Description source

Packages by operating system

Compare recorded versions, then open a package for dependency, file, checksum, and repository evidence. Version strings are distribution-specific, not a ranking of newer software.

Fedora 43

  1. Package vim-javabrowser

    43 (Fedora 43) (Unspecified): The javabrowser plugin for VIM editor

    2.03-26.fc43: noarch

    Source: vim-javabrowser

Fedora 44

  1. Package vim-javabrowser

    44 (Fedora 44) (Unspecified): The javabrowser plugin for VIM editor

    2.03-27.fc44: noarch

    Source: vim-javabrowser

Project resources and further reading

Mapping provenance

Only source-backed identity signals create public cross-OS links. A reviewer can later approve or dispute an inferred relationship without rewriting native package history.

No field-level source record is published yet.