[FOLIO-292] mod-circulation: BUILD FAILURE (as of 2016-09-02 00:34 WEST) Created: 01/Sep/16  Updated: 12/Nov/18  Resolved: 18/Sep/18

Status: Closed
Project: FOLIO
Components: None
Affects versions: None
Fix versions: None

Type: Bug Priority: P3
Reporter: Filipe Bento Assignee: shale99
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Sprint:

 Description   

[ERROR] Failed to execute goal on project circulation: Could not resolve dependencies for project folio:circulation:jar:0.0.1-SNAPSHOT: The following artifacts could not be resolved: sling:domain-models-api-interfaces:jar:0.0.1-SNAPSHOT, sling:domain-models-runtime:jar:0.0.1-SNAPSHOT: Could not find artifact sling:domain-models-api-interfaces:jar:0.0.1-SNAPSHOT -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
The command '/bin/sh -c /bin/bash -c 'git clone https://github.com/folio-org/mod-circulation.git ./mod-circulation && cd ./mod-circulation && mvn clean install'' returned a non-zero code: 1

****
... probably because of:
https://github.com/folio-org/mod-circulation/search?utf8=%E2%9C%93&q=sling



 Comments   
Comment by Filipe Bento [ 01/Sep/16 ]

raml-module-builder: Ok (before)

Comment by Filipe Bento [ 01/Sep/16 ]

Same with mod-configuration – new ticket (here)?
(...)
[WARNING] The POM for sling:domain-models-api-interfaces:jar:0.0.1-SNAPSHOT is missing, no dependency information available
[WARNING] The POM for sling:domain-models-api-aspects:jar:0.0.1-SNAPSHOT is missing, no dependency information available
[WARNING] The POM for sling:domain-models-runtime:jar:0.0.1-SNAPSHOT is missing, no dependency information available
Downloading: https://repo.maven.apache.org/maven2/junit/junit/4.12/junit-4.12.jar
Downloading: https://repo.maven.apache.org/maven2/org/hamcrest/hamcrest-core/1.3/hamcrest-core-1.3.jar
Downloaded: https://repo.maven.apache.org/maven2/junit/junit/4.12/junit-4.12.jar (308 KB at 5125.8 KB/sec)
Downloaded: https://repo.maven.apache.org/maven2/org/hamcrest/hamcrest-core/1.3/hamcrest-core-1.3.jar (44 KB at 610.7 KB/sec)
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 2.047 s
[INFO] Finished at: 2016-09-01T23:40:23+00:00
[INFO] Final Memory: 9M/143M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project configuration: Could not resolve dependencies for project com.folio:configuration:jar:0.0.1-SNAPSHOT: The following artifacts could not be resolved: sling:domain-models-api-interfaces:jar:0.0.1-SNAPSHOT, sling:domain-models-api-aspects:jar:0.0.1-SNAPSHOT, sling:domain-models-runtime:jar:0.0.1-SNAPSHOT: Could not find artifact sling:domain-models-api-interfaces:jar:0.0.1-SNAPSHOT -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
The command '/bin/sh -c /bin/bash -c 'git clone https://github.com/folio-org/mod-configuration.git ./mod-configuration && cd ./mod-configuration && mvn clean install'' returned a non-zero code: 1

Comment by Filipe Bento [ 02/Sep/16 ]

Ok, same thing with all of raml based... (tried them all)

Comment by shale99 [ 04/Sep/16 ]

must mvn install the raml-module-builder in order to build any module built using it - that includes mod-configuration, mod-acq, mod-acq-postgres, and mod-circulation - should be indicated in the read me of each project - if this was done (mvn installing the raml builder) please let me know

Comment by Filipe Bento [ 04/Sep/16 ]

We are good now – found that running them in chain, mvn installing the raml builder has to be run, before all of them, even if it was already ran; e.g.;

Update (see bellow)

cd /usr/src/app && \
git clone https://github.com/folio-org/raml-module-builder.git ./raml-module-builder
cd ./raml-module-builder && \
mvn clean install

cd /usr/src/app && \
git clone https://github.com/folio-org/mod-circulation.git ./mod-circulation && \
cd ./mod-circulation && \
mvn clean install

cd /usr/src/app && \
git clone https://github.com/folio-org/mod-configuration.git ./mod-configuration && \
cd ./mod-configuration && \
mvn clean install

cd /usr/src/app && \
git clone https://github.com/folio-org/mod-acquisitions.git ./mod-acquisitions && \
cd ./mod-acquisitions && \
mvn clean install

Comment by shale99 [ 04/Sep/16 ]

will take a look at that - it shouldnt be the case - once you run the module-builder and the jars are in your local repo - that should be enough and all other modules depending on those jars should pass - will take a look

Comment by Filipe Bento [ 06/Sep/16 ]

Update on this: yes, it's only necessary to have been ran once for that session / container, "mvn clean install" of raml-module-builder before "mvn clean install" of its based modules – will update example above.

If this container is used for the commits of a new image, then "mvn clean install" of raml-module-builder needs to be executed before deploying new modules, that haven't been compiled in the old container. That was part of my scenario, hence those errors and build fails.

Thanks,
Filipe

Comment by Jakub Skoczen [ 06/Sep/16 ]

Guys, I think those steps will be largely avoided when the artifacts are uploaded to a shared Maven repo. I have created a Jira issue for that effect.

Generated at Thu Feb 08 23:04:41 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.