[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] **** |
| 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)? |
| 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 && \ cd /usr/src/app && \ cd /usr/src/app && \ cd /usr/src/app && \ |
| 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, |
| 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. |