As part of its ongoing commitment to Java technology and the choice it provides to customers as well as industry-wide technology standards and open source, SAP AG (NYSE: SAP) is taking a more active leadership role in the Eclipse Foundation by increasing its membership level from Strategic Consumer to Strategic Developer. SAP will provide at least eight full-time development resources to various projects and lead open source projects, ensuring direct input into the development and architecture of Eclipse. As a Strategic Developer, SAP will be more active within the Eclipse community, including the new Eclipse Git Team Provider (EGit), the Eclipse Modeling Project (EMP) and the Eclipse Equinox Project. Eclipse technology has become the de-facto standard in many domains and for many companies ongoing collaboration on various projects with other industry leaders supports the standards and open source strategies of customers and partners.
The use of standard technologies developed within the Eclipse community provides customers and partners with a familiar development environment and, as a result, the steep learning curve for resources is eliminated. SAP supports the mission of the Eclipse Foundation to help increase developer adoption of Eclipse technologies in the software industry, as well as the broad support by a large number of software vendors, has increased interoperability between solutions based on the same common Eclipse technologies.
SAP is a founding member of the foundation and has been using Eclipse technology since 2002. As an active contributor to the Eclipse Web Tools Platform Project (WTP) and an original contributor of the Eclipse Memory Analyzer Tool (see "SAP Contributes New Tool to Open Source Eclipse Developer Community"), SAP has been involved in the Eclipse ecosystem since 2004. Through its expanded involvement, SAP will collaborate with other members on building an open development platform comprised of extensible frameworks, tools and runtimes for building, deploying and managing software across the lifecycle. The Eclipse Git Team Provider (EGit) project was co-initiated by SAP to drive the evolution of a modern distributed version control system boosting development productivity with easier Eclipse integration and higher performance at reduced total cost of ownership. Participation in the Eclipse Modeling Project (EMP) will drive the evolution and promotion of model-based development technologies, and the Eclipse Equinox Project will provide a service-oriented OSGi-based modular platform for application development and operations. Additionally, SAP has proposed a new project, codename Pave, within WTP, with initial code donation from SAP that will provide a template-based application framework to simplify development of complex applications.
As part of its increasing commitment to the Eclipse community, SAP hosted the most recent Eclipse DemoCamp event at SAP headquarters in Walldorf, Germany. Developers from various companies demonstrated the latest developments from assorted Eclipse projects and shared their experiences. The Eclipse DemoCamp in Walldorf attracted approximately two hundred attendees, making it the largest Eclipse DemoCamp to date.
Any statements contained in this document that are not historical facts are forward-looking statements as defined in the U.S. Private Securities Litigation Reform Act of 1995. Words such as "anticipate," "believe," "estimate," "expect," "forecast," "intend," "may," "plan," "project," "predict," "should" and "will" and similar expressions as they relate to SAP are intended to identify such forward-looking statements. SAP undertakes no obligation to publicly update or revise any forward-looking statements. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. The factors that could affect SAP's future financial results are discussed more fully in SAP's filings with the U.S. Securities and Exchange Commission ("SEC"), including SAP's most recent Annual Report on Form 20-F filed with the SEC. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their dates.
Copyright © 2009 SAP AG. All rights reserved.
SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serve informational purposes only. National product specifications may vary.
The use of standard technologies developed within the Eclipse community provides customers and partners with a familiar development environment and, as a result, the steep learning curve for resources is eliminated. SAP supports the mission of the Eclipse Foundation to help increase developer adoption of Eclipse technologies in the software industry, as well as the broad support by a large number of software vendors, has increased interoperability between solutions based on the same common Eclipse technologies.
SAP is a founding member of the foundation and has been using Eclipse technology since 2002. As an active contributor to the Eclipse Web Tools Platform Project (WTP) and an original contributor of the Eclipse Memory Analyzer Tool (see "SAP Contributes New Tool to Open Source Eclipse Developer Community"), SAP has been involved in the Eclipse ecosystem since 2004. Through its expanded involvement, SAP will collaborate with other members on building an open development platform comprised of extensible frameworks, tools and runtimes for building, deploying and managing software across the lifecycle. The Eclipse Git Team Provider (EGit) project was co-initiated by SAP to drive the evolution of a modern distributed version control system boosting development productivity with easier Eclipse integration and higher performance at reduced total cost of ownership. Participation in the Eclipse Modeling Project (EMP) will drive the evolution and promotion of model-based development technologies, and the Eclipse Equinox Project will provide a service-oriented OSGi-based modular platform for application development and operations. Additionally, SAP has proposed a new project, codename Pave, within WTP, with initial code donation from SAP that will provide a template-based application framework to simplify development of complex applications.
As part of its increasing commitment to the Eclipse community, SAP hosted the most recent Eclipse DemoCamp event at SAP headquarters in Walldorf, Germany. Developers from various companies demonstrated the latest developments from assorted Eclipse projects and shared their experiences. The Eclipse DemoCamp in Walldorf attracted approximately two hundred attendees, making it the largest Eclipse DemoCamp to date.
Any statements contained in this document that are not historical facts are forward-looking statements as defined in the U.S. Private Securities Litigation Reform Act of 1995. Words such as "anticipate," "believe," "estimate," "expect," "forecast," "intend," "may," "plan," "project," "predict," "should" and "will" and similar expressions as they relate to SAP are intended to identify such forward-looking statements. SAP undertakes no obligation to publicly update or revise any forward-looking statements. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. The factors that could affect SAP's future financial results are discussed more fully in SAP's filings with the U.S. Securities and Exchange Commission ("SEC"), including SAP's most recent Annual Report on Form 20-F filed with the SEC. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their dates.
Copyright © 2009 SAP AG. All rights reserved.
SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serve informational purposes only. National product specifications may vary.
