Frequently Asked Questions¶
Where can I get the source code?¶
Do you publish changelogs?¶
Yes. Each project have it’s own changelog on GitHub. Go to the GitHub project page using the links in the previous question and click
On the resulting page, a line with links to all commits, branches commits and contributors is show. Clock on the text that say
and all the releases of that project are listed with links to the changelog.
If you want to see what’s coming in the future releases, check out Discuss . Approximately every other week, our product advisory board meets to discuss what to prioritze in the upcoming releases. Reports from these meetings are published on Discuss.
How is Enonic XP Licensed¶
Enonic XP is available under the GPL 3.0 license. This basically means that you are free to use and re-distribute Enonic XP according to the GPL license. The linking exception ensures that you can build custom applications and libraries on top of Enonic XP and license these however you see fit. Any changes made to the Enonic XP core platform however must be licensed as GPL.
We encourage the use of FOSS licensing for 3rd party apps and libraries. Libraries in particular should be licensed with a non-intrusive license such as Apache, BSD or MIT.
This is a major difference from products such as Drupal and Wordpress where your themes, plugins and modules must be licensed as GPL too.
Enonic XP also consists of many 3rd party software components. The complete list can be found in our Notice.txt file
What is $XP_INSTALL?¶
$XP_INSTALL and $XP_HOME are referenced frequently in the documentation and it is important to understand the difference. $XP_INSTALL is the top level directory of the XP installation and it contains the directories bin, home, lib, toolbox and others.
What is $XP_HOME?¶
$XP_HOME, by default, is the location of the $XP_INSTALL/home folder which contains the config, deploy, repo and other directories specific to a single XP instance. The home folder can be copied to multiple locations for developers working on more than one project.
There are two situations where the $XP_HOME environment variable must be set:
- When developers are working on an application and intend to use ./gradlew deploy.
- When a home folder other than $XP_INSTALL/home is to be used.