-
Notifications
You must be signed in to change notification settings - Fork 47
Build issues on vagrant #206
Comments
I've not seen this before, but it looks to me like it's a Vagrant-specific On Sat, Mar 19, 2016 at 7:22 PM, Nick Ruest notifications@github.com
|
@jrwiebe yep. I've been down a bunch paths with this 😄 I've tried to do the build with the standard vagrant user, here, and then as root here. I'm getting that same error That jar is on the filesystem too, so I'm not sure what's going on. If maven can't find it, read it, or it's just not in it's path? But, sudo mvn build works fine. shrugs |
...nothing really jumped out in the |
Resolved it with archivesunleashed/docker-aut@a0934c8 Something is up with vagrant finding all those artifacts. It finds others in |
I'm setting up a vagrant build for the workshops @ianmilligan1 and I'll be running at IIPC and Congress, and running into an issue building warcbase.
If I try and build it as the vagrant user, or root, I get the following:
If I
vagrant ssh
into the machine after the build, and build normally withmvn clean package appassembler:assemble -DskipTests
the build fails as well. But, if I run it with sudo (sudo mvn clean package appassembler:assemble -DskipTests
) it builds fine.I setup TravisCI with no sudo as a sanity check, and it built fine. See also #205.
Have you run into this before?
The text was updated successfully, but these errors were encountered: