Automic VaultAutomic Vault

brew

使用 Homebrew 安装 gwt

查看 gwt 的安装路径、可执行文件、元数据以及面向 AI 代理工作流的安全说明。

安装

其他安装命令

macOS

Homebrew已验证 · 100%
brew install gwt

local Homebrew formula metadata

概览

软件包摘要

Google web toolkit

命令和别名

  • i18nCreator
  • webAppCreator

历史

项目历史与用法

GWT, originally Google Web Toolkit, is a Java-to-JavaScript web application toolkit that lets developers write client-side web applications in Java and compile them to browser JavaScript. The project's own mission text emphasizes using existing Java tools to build AJAX applications for modern browsers.

项目历史

Google announced Google Web Toolkit in May 2006 as a publicly available software development tool for creating AJAX applications. The early Google Developers Blog description said developers could build and debug in Java with normal Java tools, then deploy browser-compliant JavaScript and HTML generated by the GWT compiler.

GWT 1.0 builds appeared in May 2006, followed by the 1.1 series in August 2006 and the 1.2 and 1.3 series later that year. In December 2006, Google announced that it was releasing all GWT source code under an open source license, after the tool took off faster than expected.

The project evolved through a long 1.x line and then GWT 2.0 in December 2009. The versions page notes that 2.0.0 introduced a single distribution for Windows, Mac OS X, and Linux, replacing earlier platform-specific download artifacts. Later 2.x releases continued through compiler, SDK, Java compatibility, and tooling changes.

The GitHub repository was created in 2013, and its README says it is the official open source project for GWT releases 2.5 and onward. This marks the package's transition from a Google-hosted toolkit with downloadable SDK zips into a GitHub-centered open source project with source builds, tests, and community contribution guidance.

采用历史

GWT gained early attention because it let Java developers build rich browser applications without switching fully to handwritten JavaScript. The official books page records a wave of third-party books from late 2006 through 2013, including GWT in Action, GWT in Practice, Google App Engine and GWT books, and GWT 2-focused books, which is a strong signal of ecosystem uptake.

The official resources also point to related frameworks such as Ext GWT and Vaadin, with Vaadin described as built on top of GWT. That ecosystem made GWT more than a compiler: it became a platform for Java-centric web UI libraries, enterprise application patterns, and server/client integration techniques.

GWT's community story shifted as browser tooling changed. The project retained its Java-to-JavaScript compiler identity while adding documentation around Super Dev Mode, JsInterop, JRE emulation, RequestFactory, activities and places, UiBinder, code splitting, and testing. The roadmap later focuses on Java language and JRE emulation support and explores J2CL-related JsInterop features.

使用方式

A typical GWT workflow uses Java source for client-side code, GWT modules, JRE emulation, widgets or direct DOM APIs, RPC or other AJAX communication, and the compiler to produce JavaScript. The official documentation covers project creation, UI building, event handling, debugging, styling, compilation, internationalization, testing, deployment, and API reference material.

For package-manager users, the brew package exposes older SDK command-line helpers such as webAppCreator and i18nCreator. Source builders use Java and Ant, with the GitHub README documenting SDK distribution builds, Maven artifact creation, code-style checks, and test suites.

为什么软件包爱好者会关心

GWT is important in package history because it represents a pre-TypeScript, pre-modern-SPA answer to the same problem: use a statically typed language and mature tooling to produce browser JavaScript. Its package shape, a Java SDK plus compiler plus command-line helpers, is very different from the npm-centered frontend stacks that later dominated web development.

It also matters as a long-lived compatibility package. Maintaining GWT means preserving Java APIs, emulated JRE behavior, compiler output, old SDK workflows, and documentation for applications that may have started in the Ajax boom but still need buildable artifacts years later.

时间线

  • 2006-05-16: Version 1.0 RC 1 build listed on the official versions page.
  • 2006-05-25: Version 1.0 build listed on the official versions page.
  • 2006-12: Google announced the release of GWT source code under an open source license.
  • 2009-12-08: GWT 2.0.0 build listed with a single Windows, Mac OS X, and Linux distribution.
  • 2012-10-24: GWT 2.5.0 build listed on the official versions page.
  • 2013-04-18: GitHub repository created; README says GitHub source is official for releases 2.5 and onward.
  • 2017-10-19: GWT 2.8.2 build listed on the official versions page.
  • 2020-05-13: GWT 2.9.0 build listed on the official versions page.
  • 2024-01-09: GWT 2.10.1 and 2.11.0 builds listed on the official versions page.

Related projects

  • J2CL: GWT roadmap discusses exploring J2CL-exclusive JsInterop features.
  • Vaadin and Ext GWT: official books page lists them as related frameworks in the GWT ecosystem.
  • Google App Engine: official books page records combined GWT and App Engine application development material.
  • Java, Ant, Maven, and JRE emulation: core build and compatibility technologies documented by the project.

来源

安全态势

风险级别:绿色

narrow executable package without higher-risk signals.

风险分类器

绿色 风险 · 低 置信度 · appliance

原因

  • narrow executable package without higher-risk signals

信号

  • metadata:no-higher-risk-signals

安装行为

  • formula 元数据中未记录 Homebrew post-install 钩子。
  • Homebrew bottle 元数据适用于 1 个平台目标。
  • 安装时包含 1 个运行时依赖。

建议审查

在无人值守的代理使用前,请检查该工具是否读取明文凭据、写入远程状态、发布制品或调用插件。

可执行文件

已安装的可执行文件

命令类型暴露范围备注
i18nCreatorcli全局可执行文件
webAppCreatorcli全局可执行文件

新鲜度

版本和新鲜度

这些信号区分页生成时间、软件包管理器活动和上游发布比较。只有存在证据 URL 和可比较版本时,才会提示版本落后。

页面生成时间2026-07-26
管理器版本2.13.1
管理器更新时间2026-06-19
本地数据OK
上游not checked
检测到的最新版本未检测到

https://github.com/gwtproject/gwt

安装元数据

软件包元数据

软件包键brew:gwt
版本2.13.1
软件包管理器Homebrew
软件包管理器页面https://formulae.brew.sh/formula/gwt
主页https://www.gwtproject.org/
仓库https://github.com/gwtproject/gwt
上游文档https://www.gwtproject.org/doc/latest
许可证Apache-2.0
源码归档https://github.com/gwtproject/gwt/releases/download/2.13.1/gwt-2.13.1.zip
最后更新2026-06-19T22:37:16Z
Pulseupdated
依赖openjdk
Bottle可用 (于 all)
Homebrew post-install未定义
服务未声明

注册表事实

源数据库详情

Source DatabaseHomebrew formula API
Taphomebrew/core
Full Namegwt
Version Scheme0
Revision0
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedno
Disabledno
Keg Onlyno
URL Keys
  • stable

来源线索

由仓库数据生成

此页面由 av-webscripts/generate-pkg-sqlite.py 生成的私有软件包 SQLite 工件提供。

使用的来源

  • Geiger risk classifier
  • Nucleus package database
  • av.db category and tag curation
  • cross-ecosystem install command graph
  • curated package history
  • package relationship graph
  • package version freshness
  • package-page enrichment