We don’t allow questions seeking recommendations for software libraries, tutorials, tools, books, or other off-site resources. You can edit the question so it can be answered with facts and citations.
Closed 7 years ago.
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
接受
或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
发布评论
评论(4)
(注:我是构建 Jazz 的团队的成员。我不再在 Jazz 团队工作,但仍在 IBM 工作。)
Jazz 是由 IBM Rational 部门创建的一系列技术,用于支持软件团队工具和软件配置等活动管理 (SCM)、错误和增强跟踪、构建自动化、发布和迭代规划、需求管理、测试管理等等。
Jazz 是由 Rational 团队于 2004 年底启动的,因为我们意识到我们需要一个新的技术基础来帮助团队应对现代挑战,例如地理上分散的团队以及治理和合规性问题。
与 Eclipse 有多种关系。首先,最初的 Jazz 团队由许多创建 Eclipse 的 IBM 人员组成,例如 John Wiegand、Erich Gamma、Jim des Rivieres、Nick Edgar 和 Jean-Michel Lemieux 等。此外,Eclipse 技术在 Jazz 的早期也发挥了一定的作用。我们创建的第一个客户端技术是对 Eclipse IDE 的一些新的团队扩展(这演变成了 Rational Team Concert Eclipse 客户端)。我们还使用 Eclipse Equinox(OSGi 的 Eclipse 实现)设计了原始服务器,以便您可以使用 OSGi 可扩展性模型来贡献服务器端资源,例如 Web 服务端点、数据模型定义和 Web UI 代码。
随着时间的推移,我们意识到通过共享运行时的可扩展性行不通,因此我们转向基于 RESTful HTTP 和 RDF 的分布式可扩展性模型。我们创建了一个开放社区,为团队资源定义 RESTful 数据模型,称为“生命周期协作开放服务”(http://open-services.net/)。
最后,Jazz 甚至对 Eclipse 产生了一些影响。当我开始编写 Jazz Web UI 代码时,起初我设想了一个可扩展的 Web UI,非常类似于 Eclipse UI(视图、编辑器等),但当我意识到要做正确的事情需要做多少工作时,我很快就放弃了这些雄心壮志。方式。然而,多年来我与 IBM Eclipse 人员合作讨论了如何在浏览器和富客户端(Eclipse IDE、Visual Studio)之间实现组件重用,并且我们还讨论了如果能够有一个一流的组件该多好Eclipse 的浏览器故事。经过极其曲折的道路后,Eclipse.org 在 IBM 的支持下提出了一个名为 Orion (http://www.eclipse.org/orion/) 的新项目,旨在为 Eclipse 提供这个浏览器故事。
是的,Eclipse 和 Jazz 之间有很多关系。 :-)
(Note: I was a member of the team who built Jazz. I no longer work on the Jazz team but still work for IBM.)
Jazz is a family of technologies created by IBM's Rational division to enable software team tools and activities like software configuration management (SCM), bug and enhancement tracking, build automation, release and iteration planning, requirement management, test management, amongst other things.
Jazz was started in late 2004 by the Rational group because we realized that we needed a new technological foundation to help teams deal with modern challenges like geographically dispersed teams and governance and compliance issues.
There are several relationships to Eclipse. First of all, the original Jazz team was staffed with many of the same IBM folks who created Eclipse, e.g. John Wiegand, Erich Gamma, Jim des Rivieres, Nick Edgar, and Jean-Michel Lemieux, among others. Also, Eclipse technology played a bit role in the early days of Jazz. The first client technology we created was some new team extensions to the Eclipse IDE (this evolved into the Rational Team Concert Eclipse client). We also engineered the original server using Eclipse Equinox (the Eclipse implementation of OSGi) so that you could use the OSGi extensibility model to contribute server-side resources like web service endpoints, data model definitions, and web UI code.
Over time, we realized that extensibility via shared runtime wasn't going to work so we shifted over to a distributed extensibility model based on RESTful HTTP and RDF. We started an open community to define RESTful data models for team resources called "Open Services for Lifecycle Collaboration" (http://open-services.net/).
Finally, there has even been some influence of Jazz on Eclipse. When I started the Jazz Web UI code, at first I envisioned an extensible web UI much like the Eclipse UI (views, editors, etc.) but quickly pulled back on those ambitions when I realized how much work that would be to do the right way. However, over the years I collaborated with the IBM Eclipse folks talking about how we could achieve component reuse between browser and rich clients (Eclipse IDE, Visual Studio) and we also talked about how nice it would be if there could be a first-class browser story for Eclipse. After an extremely circuitous path, Eclipse.org with IBM's support proposed a new project called Orion (http://www.eclipse.org/orion/) which intends to provide this browser story for Eclipse.
So yes, quite a few relationships between Eclipse and Jazz. :-)
它是一套协作工具,基于 IBM 赞助的先前研究。
您可以在此处浏览详细信息(以及一些历史记录):
原始项目: http://domino.watson.ibm.com/cambridge/research.nsf/99751d8eb5a20c1f852568db004efc90/605fd62cb9a5a54485256e200066adf6!OpenDocument
产品: http://jazz.net/about/about-jazz-products.jsp
It's a suite of collaboration tools, which are based in a previous research sponsored by IBM.
You can browse the details (and some history) here:
Original project: http://domino.watson.ibm.com/cambridge/research.nsf/99751d8eb5a20c1f852568db004efc90/605fd62cb9a5a54485256e200066adf6!OpenDocument
Products: http://jazz.net/about/about-jazz-products.jsp
我听说过这个 Jazz Process:
http://www.jazzprocess.com/concept/
还有一个书
http://www.amazon.co.uk/Jazz-Process-Collaboration -创新-敏捷
看起来很有趣
I heard about this Jazz Process:
http://www.jazzprocess.com/concept/
there's also a book
http://www.amazon.co.uk/Jazz-Process-Collaboration-Innovation-Agility
it seems interesting
我认为它是基于组件的服务器端应用程序的框架,专注于协作软件开发工具。透过流行语的面纱很难辨认出来。
想必很多都是使用Eclipse开发的。您可能还听说过它们一起使用,因为 Jazz 被设想为一种“服务器端 Eclipse”,即帮助开发和集成开发工具的平台。
I think It's a framework for component-based server-side applications, focussing on collaborative software development tools. It's hard to make out through the veil of buzzwords.
Presumably a lot of them are developed using Eclipse. You may also have heard them used together because Jazz is envisioned as a kind of "server-side Eclipse", i.e. a platform that aids development and integration of development tools.