hybris suite problems detail - AGETO/hybris-maven-plugin GitHub Wiki

Hybris suites problems in detail

Hybris has to be built at the target system.
If you want to run the hybris suite on a server you have to compile the whole suite on it. This means you are not able to compile the suite on a dedicated build server and then copy the result to your web server. This is a problem, because if you want to install an upgrade of the hybris suite on your server you have to shutdown all your web services on this server, and then compile the upgrade of the suite which can take some hours and you are not able to sell any products with this server while the compilation is running.
The whole suite has to be compiled if an extension has been updated.
If you are developing custom extensions for the hybris suite you have to recompile the whole hybris suite every time you want to test a change in the source code in your extension. Because compilation can take some hours this means that you need a lot of time while debugging your extension by waiting for the compilation of the hybris suite to finish.
The Suite is developed for the Eclipse IDE.
The Hybris suite has been developed for the Eclipse IDE which makes it hard to be imported into other IDEs like IntelliJ, so if your are used to write your code with other IDEs than Eclipse you may run into problems with the suite.
Hybris is using ANT build system.
The Hybris suite is built with the out dated build system ANT, which is not as well structured and standardized as modern build systems like maven, gradle, etc. So as a developer you need a lot of time if you want know what is going on while the build is running.

⚠️ GitHub.com Fallback ⚠️