ant addoninstall - run once and commit?

[matthewsmith]

Hi all,

When using the ant addoninstall command to install an addon into your storefront extension, do you:

1. Run this command once and commit the changes it makes to version control (along with the addon itself, if needed)

2. Run this command when setting up a new developer environment and as part of every Continuous Integration build.

I had assumed that committing the changes was the normal approach but speaking to some other Hybris practitioners they've been taking the other approach and running ant addoninstall as part of the build process.

[Former Member]

Hi,

I would say it depends on what kind of addon it is. From my experience every project is unique and most of the time addon have to be customized. So I prefer run ant addon once and commit the changes. It 's easy for maintaining the project.

If you are using multiple addons for different project I'll have a git for each of them to add generic features but nothing to specific.

That's a personal opinion, not sure if there is a good / bad answer.

[matthewsmith]

Thanks - no I'm not sure if there is a 'right' answer, I hadn't considered the multiple addons/multiple projects angle though - I'm coming from a one project, one storefront angle!

[Former Member]

As I said I would go for solution 1

[landmesf]

Hi Matthew, we're also using 2nd mentioned method: run ant addoninstall for new developer environments and in every bamboo build - esp. for deployment.

I don't know if this is a best practice. However, this way we can leave the hybris commerce core pure and reuse it as a bitbucket repository for multiple projects. This is handy for CI - i guess that all of it.

[matthewsmith]

I don't understand what you mean about leaving the commerce core 'pure'? Installing an addon onto a custom storefront extension wouldn't affect any standard extensions or the platform extension?