Ant all VS Ant clean all commands in SAP Commerce [Hybris]

By Ramesh V

In this article, I will explain the difference between most commonly used Ant build commands like ant all & ant clean all.

SAP Hybris uses Apache Ant build framework to build the extensions or modules in the Hybris framework. 

There are several ant targets available to build the hybris framework like ant all, ant clean and ant clean all.

We can find list of available ant targets by using ant -p command as shown below:

Note: before running any ant command we must set ant environment from platform folder.
          C:\Trainings\CX2211\hybris\bin\platform>setantenv.bat


Ant clean all:
When we run the ant clean all command from the platform folder, it does the following things:
  • First it will check whether all folders like bin, config, data, log, roles, temp folders are available inside hybris folder or not. If the folder structure is not available then it creates else it won't create any folder structure. 
  • It deletes all existing generated models and .class files and then start the build from scratch.
Ant all:
  • ant all assumes the folder structure is already available in hybris folder and it will just perform the build for the changes we made in the files like items.xml and .java.
In general ant all is faster and takes less time than ant clean all. And most of the cases ant all is sufficient to serve the build purpose.

ant clean all can be used when we setup hybris for the first time / sometimes if our changes are not reflecting even after using ant all command / to remove unwanted files from the code base.


Note: In hybris ant all is the default ant target.




Happy Learning!!!😊😊😊



SAP CX Senior Consultant[Hybris]

Comments

Post a Comment

Popular posts from this blog

Type System in SAP Commerce [Hybris]

By Ramesh V
In this article, I have explained in details about what is a Type System in SAP Commerce [Hybris] and how the data can be organized in the Hybris system. Type System in SAP Commerce is a data modeling framework . It defines the structure and organization of data within the platform. In SAP Commerce data can be organized in the form of types , for example product information, customer information, address information, cart information and order information etc. A type is a template for objects and every object stored in a platform is a type instance. Types can be defined in an items.xml file using following aspects: the deployment : It defines the database table where objects stored. attributes : Manage and store data for the object. the java class of the object. In SAP Commerce, Type is a blueprint of an Item and Item is an instance of a Type . Types can inherit from other types, allowing for a hierarchical organization of data. Attributes define the properties of a type. They can ...
Read more

Differences between Extension and AddOn in SAP Hybris

By Ramesh V
In this article, I have explained differences between Extension and AddOn in details in SAP Commerce [Hybris] and also described when to use Extensions and when to use AddOn's. An Extension is a self-contained module that adds or modifies functionality in SAP Commerce.   An Extension generally represents a larger functionality and it contains business logic, type definitions, back-office configurations and other configuration files like xml, properties and etc, whereas AddOns are used to extend the functionality of SAP Commerce Accelerator[storefront] without modifying the core code base. AddOns are plugin kind of extension, you can easily remove your AddOns without refactoring the code of your Accelerator extension. Extension can work independently or extend the another extension whereas AddOn always depends on an existing extension (e.g. acceleratorstorefront). Extensions are used for business logic whereas AddOns are mostly used for Frontend/UI customization.     ...
Read more

items.xml in SAP Commerce [Hybris]

By Ramesh V
The items.xml file specifies types of an extension for defining the data model . By editing the items.xml file, you can define new types or extend existing types. In addition, you can define, override, and extend attributes of the types. Location of the items.xml file: The items.xml is located in the resources directory of an extension. The items.xml files are prefixed with the name of their respective extension in the form of extension name-items.xml. For example: For the core extension, the file will be core-items.xml . For the catalog extension, the file will be catalog-items.xml . Basic structure of the items.xml file: The items.xml defines the types for an extension in XML format and the basic structure is as follows: <items   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"               xsi:noNamespaceSchemaLocation="items.xsd">           ...
Read more