-
Notifications
You must be signed in to change notification settings - Fork 17
ml local deploy modules returns 404 error -- need to update url-rewriter property #208
Comments
I think you ran against master branch. The latter issue with error-format was fixed in develop branch. The first wasn't fixed because we wanted to be able to deploy against both ML 8 and ML 7. You have to put that rewriter line in the env properties, for instance deploy/local.properties. We'll consider making ML 8 the default once we have released the current develop branch into master.. |
Thanks Geert. Yes, I see now that the Just wanted to log this, to help anyone else that might be struggling with ML 8. I've added pull request #209 to update the comments in build.properties. |
Thanks for the PR! |
Address issue #208: update comments in build.properties for ML 8
Address issue marklogic-community#208: update comments in build.properties for ML 8
Can we make this the default now? (I just ran into this issue and ate up some time figuring out what was going on.) |
Isn't it solved in develop branch yet? Latest Roxy will also auto-compensate. Maybe we should upgrade.. |
…rties for ML 8 Update comments in build.properties to indicate url-rewriter change required for ML version 8.
Address issue marklogic-community#208: update comments in build.properties for ML 8
While attempting to install demo-cat locally with MarkLogic 8, I ran into a problem with the
ml local deploy modules
command, which was returning a404 Not Found
error.I found the related Roxy issue #370.
I updated the following setting in my build.properties file.
I then ran
ml local bootstrap
andml local restart
, and was then able to successfully complete theml local deploy modules
, and start up the application.I think the above is isolated to ML8, so may just need an update to the readme instructions.
UPDATE: Strangely, when I tried to re-run
ml local deploy modules
, I began to receive a500: RESTAPI-UNSUPPORTEDPROP
error. I found related Roxy issue #336, and so removed the<error-format>
line from rest-api/config/properties.xml file, and was able to then re-rundeploy modules
without issue.I'm not sure why the first pass was successful, and subsequent runs picked up the
<error-format>
element.The text was updated successfully, but these errors were encountered: