On 5 August 2013 16:35, Stanislav Ochotnicky <sochotnicky@redhat.com> wrote:

This is most likely caused because you are running mvn-rpmbuild install, instead
of using %mvn_build. maven-local pulls in *some* plugins, but definitely not all
of them.

Thanks, I updated the f20 spec file to the new guidelines and this indeed solved it. I was using the same spec file for f18, f19 and f20.

Though now I have another dependency problem:

DEBUG: [INFO] Reactor Summary:
DEBUG: [INFO]
DEBUG: [INFO] guacamole-common .................................. SUCCESS [2.056s]
DEBUG: [INFO] guacamole-ext ..................................... SUCCESS [0.255s]
DEBUG: [INFO] guacamole-common-js ............................... SUCCESS [0.485s]
DEBUG: [INFO] guacamole ......................................... FAILURE [0.042s]
DEBUG: [INFO] guacamole-client .................................. SKIPPED
DEBUG: [INFO] ------------------------------------------------------------------------
DEBUG: [INFO] BUILD FAILURE
DEBUG: [INFO] ------------------------------------------------------------------------
DEBUG: [INFO] Total time: 3.654s
DEBUG: [INFO] Finished at: Mon Aug 05 16:40:28 CEST 2013
DEBUG: [INFO] Final Memory: 27M/344M
DEBUG: [INFO] ------------------------------------------------------------------------
DEBUG: [ERROR] Failed to execute goal on project guacamole: Could not resolve dependencies for project net.sourceforge.guacamole:guacamole:war:0.8.2: Cannot access guac-dev (http://guac-dev.org/repo) in offline mode and the artifact net.sourceforge.guacamole:guacamole-common-js:zip:0.7.3 has not been downloaded from it before. -> [Help 1]

With the same spec file up to 22nd of July the guacamole-common-js component that is built as part of the project was used; now the same build tries to download guacamole-common-js off the web and not using the one that is built a moment before.

Anything I should look for?

Many thanks,

--Simone