If you have an active support subscription, purchased prior to May 31, 2019, please use the email address, provided to you in the email confirming the license purchase.
If you have questions, not covered by the documentation, please email us at firstname.lastname@example.org.
If you are a current customer of JxMaps all the support hours remain with you and are valid until your support period comes to an end.
All Commercial licences previously purchased will remain valid. You can continue using them according to the terms of the Product License Agreement.
JxMaps supports Windows XP SP2, 7, 8, Server 2008, Server 2012, macOS 10.8 - 10.12, Ubuntu 10 and higher; Oracle and Apple JDKs 1.6 and higher, 32-bit and 64-bit architectures.
Yes, you can use JxMaps in Java Applet and JWS applications like a standard Java library.
This is possible with the Per Developer License.
You can distribute unlimited number of copies of your product with our library enclosed.
The fully-qualified name for a class is the package name followed by the class name, separated by a period (.). For example: com.mycompany.myproduct.MyClass
This can be any class of your application. The only requirement is that it should be included into your Java application class path.
When we say “project” we have in mind one product of your company, including your future product versions or potential derivative works, based on your product.
The Project License is tied to one project only.
Having purchased the license you received a license archive. The archive will contain a licence.jar file. This license should be used in the development process and included in your application when distributing it to end users. Inside the license.jar you can find the teamdev.licenses file that contains information about your license.
Chromium code is mainly provided under a permissive BSD license, however, some components it includes are supplied under different licenses. We have reviewed the licenses for all components included in JxMaps and referenced them here. There are no requirements to disclose your proprietary code.