Read the rest of this FAQ, which should answer any question you might have about
redistributing a modified version of Aptana Studio or Jaxer.

Aptana wants to make our products available to everyone, and we want to continue to make the source code available and encourage outside contributions.

By adopting a dual license model, Aptana can remain open source and encourage the freedom of development and contribution that has made us who we are. In addition, it makes it easier to use our software in situations where the GPL is not an option.

The dual licensing model sustains both innovation and growth. If a company sells a version of Aptana Studio or Jaxer, or a work based on it, and cannot contribute the code back to the community, we ask that they contact us for a commercial license. On the other hand, developers that want to create better open-source software can continue to do so under the GPL and ensure that everyone benefits from each other's contributions.

You can change any of Aptana Studio's or Jaxer's GPL'd source code and create derivative works as long as everything you add or change is all licensed under the GPLv3 and made publicly available.

Yes, under the GPL. If you need to make modifications, add or remove plugins, etc., or otherwise create a work based on Aptana Studio or Jaxer, and you cannot make those changes available under the GPL, you will need to contact us for a commercial license.

Any code you write and own copyright to, which is not a work based on Aptana Studio or Jaxer code, can be distributed in any manner under any license. However, for example, if you create and distribute a combination of your own code with Aptana Studio or Jaxer, or you otherwise create a work based on an Aptana product, then the whole work must be GPL'd or you must obtain a separate license from Aptana.

No. If you keep these modifications internal to your organization, you do not have to make your changes publicly available. If you wish to redistribute modifications external to your organization, you must either contact Aptana for a commercial license or release it under the GPL.

Please send your question to license@aptana.com and we will be happy to assist you.

Running your software on the Jaxer server does not at all compel you to license your software under the GPL. Jaxer itself is licensed under the Gnu Public License version 3 (the GPL) in order to keep it free to use and distribute and extend, as long as distributed extensions to Jaxer itself are offered back to the community under the GPL. But software programs that run on top of Jaxer are not bound by the Jaxer GPL license. Indeed we place no restrictions on the software you run on top of Jaxer, in terms of licensing or anything else.

While most of Jaxer runs on the server, a small part of Jaxer is a client-side library that by default gets embedded in the pages Jaxer serves to the browser. Alternatively, Jaxer's configuration can be changed so pages it serves reference the client-side Jaxer library through a <script src="..."></script> tag. To alleviate any concerns you may have that such automatic distribution of a small piece of Jaxer might create a derivative work and thereby entangle your software with Jaxer's license, we're in the process of formulating an explicit "classpath" exception to the GPL license for Jaxer: that exception will state that we explicitly grant you an exception to distribute the client-side part of Jaxer and dynamically link it with your own software regardless of the terms of your software's license.

In short, please feel free to develop software for running on Jaxer without being concerned that Jaxer's license will somehow restrict your software's license. Jaxer's license does not affect any software you yourself write or obtain from a third party. Indeed, as long as you are not deriving software from Jaxer and redistributing that Jaxer-derived software, the only effect of the Jaxer license on you is to make sure Jaxer remains free and open to you.