sakai:deploy goal fails if the lib directory doesn't exist
Description
Previously running the sakai:deploy goal on an empty directory created all necessary sub-directories. For instance if the directory "/home/matt/fakedirectory" exists then the command below in the past would work and create all directories (like shared, webapps, etc)
Now it results in an error with the lib directory.
This is the full error, so looks more like some issue with SMP-22
Yeah, it shouldn't need to create the lib directory as these directories were created by the plugin. Thanks!
Juanjo Meroño October 20, 2015 at 10:00 AM
This only fails if you deploy in an empty directory, because if you deploy in a real tomcat directory the lib folder already exists. Anyway if this is fixed the fix for could be modified, at least the lines that create the lib directory will be no longer necessary.
Matthew Jones October 14, 2015 at 2:32 PM
Edited
Running this on 10.x (in kerenl) creates 4 top level directories common, components, lib and shared.
Previously running the sakai:deploy goal on an empty directory created all necessary sub-directories. For instance if the directory "/home/matt/fakedirectory" exists then the command below in the past would work and create all directories (like shared, webapps, etc)
Now it results in an error with the lib directory.
This is the full error, so looks more like some issue with SMP-22