cancel
Showing results for 
Search instead for 
Did you mean: 

hybris 5.2.0.2 Production Deployment fails

Former Member
0 Kudos

I am configuring a new CI environment and I noticed an odd behavior when deploying the hybris platform. It always fails to run "ant clean all" on my target environment right after extracting the hybrisServer-*.zip files.

While the below WIKI links explain the process in detail of how to deploy to production, I decided to download the hybris commerce suite 5.2.0.2 from the wiki and I followed the steps accordingly, only to face the following error (which is surprisingly the same I have on my CI). Does anybody has any clue on why these steps doesn't work? Thanks!

  • https://wiki.hybris.com/display/release5/Create+Deployment+ZIP+Files

  • https://wiki.hybris.com/display/release5/Install+Deployment+ZIP+Files

    Buildfile: /Users/rgarrido/Temp/unzipped/hybris/bin/platform/build.xml [echo] /Users/rgarrido/Temp/unzipped/hybris/bin/platform/tomcat/bin [mkdir] Created dir: /Users/rgarrido/Temp/unzipped/hybris/log [mkdir] Created dir: /Users/rgarrido/Temp/unzipped/hybris/data [mkdir] Created dir: /Users/rgarrido/Temp/unzipped/hybris/temp/hybris [echo] No platform version file can be found!! [echo] cleabrary folder /Users/rgarrido/Temp/unzipped/hybris/bin/platform/lib/dbdriver/ [artifact:mvn] [INFO] Scanning for projects... [artifact:mvn] [INFO] Searching repository for plugin with prefix: 'dependency'. [artifact:mvn] [INFO] ------------------------------------------------------------------------ [artifact:mvn] [INFO] Building Maven Default Project [artifact:mvn] [INFO] task-segment: [dependency:copy-dependencies] [artifact:mvn] [INFO] ------------------------------------------------------------------------ [artifact:mvn] [INFO] ------------------------------------------------------------------------ [artifact:mvn] [ERROR] BUILD ERROR [artifact:mvn] [INFO] ------------------------------------------------------------------------ [artifact:mvn] [INFO] Cannot execute mojo: copy-dependencies. It requires a project with an existing pom.xml, but the build is not using one. [artifact:mvn] [INFO] ------------------------------------------------------------------------ [artifact:mvn] [INFO] For more information, run Maven with the -e switch [artifact:mvn] [INFO] ------------------------------------------------------------------------ [artifact:mvn] [INFO] Total time: < 1 second [artifact:mvn] [INFO] Finished at: Mon Sep 15 17:41:00 EDT 2014 [artifact:mvn] [INFO] Final Memory: 6M/245M [artifact:mvn] [INFO] ------------------------------------------------------------------------ BUILD FAILED /Users/rgarrido/Temp/unzipped/hybris/bin/platform/build.xml:20: The following error occurred while executing this line: /Users/rgarrido/Temp/unzipped/hybris/bin/platform/resources/ant/antmacros.xml:77: The following error occurred while executing this line: /Users/rgarrido/Temp/unzipped/hybris/bin/platform/resources/ant/mavenTasks.xml:309: Java

Accepted Solutions (1)

Accepted Solutions (1)

former_member602476
Active Participant
0 Kudos

Have you tried setting this in your local.properties? maven.update.dbdrivers=false

Former Member
0 Kudos

Just tried and it kinda worked. Is this property documented somewhere? I had to copy the hsqldb driver to the hybris/bin/platform/lib/dbdriver folder. I guess if maven cannot be used for the base dependencies I'll have to add yet another step on my CI to resolve these kind of things... Not ideal at all...

Former Member
0 Kudos

Any chance of making either the pom.xml files available on the deployment artifacts or making the deployment artifacts works without having to run "ant clean all"? I.e. Is the "ant clean all" targets only used to regenerate the platformhome.properties or is there any other stuff that needs to be refreshed with it? I have some Gulp tasks running as a macro on the buildcallback.xml that is also annoying to set values to skip this execution. Having to run a compilation after packing for production deployment is unsettling.

former_member602476
Active Participant
0 Kudos

You will need to call ant after deployment of zip files. There are additional things that happens when calling ant so as documentation suggests you need to call after zip file deployment: precompiles jsp, copies the tomcat configuration of the embedded server What I have seen work well in deployments is setting up a defined location for the db driver and configure the deployment script to fetch it. Other workarounds are discussed here but I think you should avoid ant customize if you can.

Former Member
0 Kudos

I am facing same issue on for Hybris 5.4 deployment also tried adding maven.update.dbdrivers=false in local.properties but it didn't work. Can you please explain what other steps you performed to make it work.

Former Member
0 Kudos

Could you please explain what changes need to be done in script to make it work. I am facing this issue on Hybris 5.4. Please recommend.

Answers (0)