Add API-X to vagrant install; Resolves https://github.com/Islandora-C…

[ruebot]

…LAW/CLAW/issues/504

See: Islandora/documentation#504

How to test:

• clone repo, and checkout issue-504 branch
• vagrant up
• You should have no errors in the build, and see something along the lines of:

==> default: Installing API-X
==> default: Installing API-X
==> default: 337 [sshd-SshClient[7382f612]-nio2-thread-2] WARN org.apache.sshd.client.keyverifier.AcceptAllServerKeyVerifier - Server at /0.0.0.0:8101 presented unverified RSA key: 6a:cc:33:3d:76:08:39:0a:34:1c:00:20:c2:d1:5a:1d
==> default: Adding feature url mvn:org.fcrepo.apix/fcrepo-api-x-karaf/0.1.0/xml/features
==> default: 
==> default: 
==> default: Running provisioner: shell...
    default: Running: /tmp/vagrant-shell20170126-11798-3ueq4q.sh

@dannylamb @whikloj can you test?

[dannylamb]

@ruebot I think we need to update fcrepo-camel. Which will require updating camel to 2.18.x. This will also force us to upgrade the amherst services we have running as well.

That's an oversight on my part.

[dannylamb]

@ruebot Are you ok with handling that explosion of scope? We can address all those individually if you don't have the time right now.

[ruebot]

@dannylamb no worries. I can make it happen!

[ruebot]

@dannylamb I haven't touched the Camel side of things in the build in a while. Am I missing something, I don't see where we actually install Camel. And, it looks like the CAMEL_VERSION variable actually does nothing now. I'm not seeing anything obvious camel-wise in scripts/karaf.sh, scripts/fcrepo-camel-toolbox.sh, or scripts/islandora-karaf-components.sh.

[dannylamb]

@ruebot https://github.com/Islandora-CLAW/claw_vagrant/blob/master/configs/karaf/fcrepo_camel_toolbox.script#L1

It's a transitive dependency of fcrepo-camel-toolbox. Try bumping the version to 4.7.0.

You can update Amherst stuff here: https://github.com/Islandora-CLAW/claw_vagrant/blob/master/configs/karaf/islandora_id_mapping_service.script#L1

[ruebot]

@dannylamb ready for even more scope creep? Looks like we'll need to update Alpaca to make this happen. I believe we need to align it with the versions listed in the fcrepo-camel-toolbox 4.7.0 release notes. This is what I think I need to update in order to proceed:

• fcrepoCamelToolboxVersion
• activemqVersion
• camelVersionRange

@acoburn that sound about right, or am I missing anything?

@dannylamb ...also, let me know if you want me to create a separate issue for the above, or just continue the work on Alpaca with this issue number.

[dannylamb]

@ruebot That sounds like a good course of action. Carry on. Just be sure to link both pulls in the issue.

[ruebot]

@dannylamb @whikloj ready for review at you convenience.

...I updated my initial comment too with instructions.

[dannylamb]

@ruebot changes are looking good. I'll spin up a copy as soon as I can and test.

[dannylamb]

Something came up when working on Islandora/Alpaca#28. The vagrant environment needs to be able to resolve Drupal urls, which we can't do at the moment because of our port forwarding strategy. Can you please run apache on port 8000 so that localhost:8000 resolves on both guest and host machine?

[dannylamb]

If we install Alpaca first, we don't need these feature declarations. Alpaca's features.xml will take care of it for us and you can delete these three lines.

[dannylamb]

This has been replaced with fcrepo-service-activemq. If this script gets run after alpaca.sh, we'll be fine to delete this.

[dannylamb]

vagrant up

[DiegoPino]

@ruebot are you giving your token away here?