I am using LiveSDK 5.6 to get file and folder info stored in One Drive. I am able to get these info, but Now, I am trying to find file version history. I am not able to find a way to get version history of a file stored in One Drive.
Can anyone suggest me a way to get version history of a file (using Live SDK or REST API ?
Rest API documentation API: https://msdn.microsoft.com/en-us/library/dn659752.aspx
Thanks in advance.
The LiveSDK, unfortunately, won't return version history but will return created_time, updated_time, etc. The new OneDrive API has a new feature for checking changes made to an item and its children (http://onedrive.github.io/items/view_changes.htm).
As Toan-Nguyen says, we can't get version number from One Drive APIs now (July 8 2016).
https://dev.onedrive.com/resources/item.htm
I want to get file version information from API, so I requested from Request page. If you want to get version, please vote.
Related
I have to fetch the list of builds present here : https://openmrs.jfrog.io/openmrs/public/org/openmrs/api/openmrs-api/
I am new to artifactory and its api. I need to know the curl command for fetching all the version numbers mentioned there please? How do I go about it? It's worthwhile to know that the repo doesn't belong to me and hence I do not have the username and password for it(Incase that's needed).
In the artifactory rest API documentation they use localhost for this purpose and do not have such a link. I haven't set this repo up so I do not know how it's done. Basically I am new to this and hence any help would be appreciated.
Thanks
Assuming you would like to get the list of versions available in this folder, there are 2 possible options:
1) Use the folder info REST API method to get a list of all the sub-folders
curl https://openmrs.jfrog.io/openmrs/api/storage/public/org/openmrs/api/openmrs-api/
2) Download and parse the maven-metadata.xml file inside this folder. This file contains information about available versions.
I want to create a custom report. Response format for sonarqube web service API /api/issues/search is JSON or XML. How can I use that response to create a html or CSV file using "unix shell without using command line tools" so that I can use it as a Report. Or is there any other better way to achieve this?
you can generate a html file if you run an analysis in the preview mode http://docs.sonarqube.org/pages/viewpage.action?pageId=6947686
It looks as if the SonarQube team has been working hard to not allow people to do this. They appear to want people to purchase an Enterprise Subscription in order to export reports.
An old version of sonar-runner (now called sonar-scanner) had an option to allow local report output. But that feature is "no more supported".
ERROR: The preview mode, along with the 'sonar.analysis.mode' parameter, is no more supported. You should stop using this parameter.
Looks like version 2.4 of Sonar Runner does what you want. If you can find it. Of course they only have 2.5RC1 available on the site now.
Using the following command should work on version 2.4:
sonar-runner -Dsonar.analysis.mode=preview -Dsonar.issuesReport.html.enable=true
There at least two open-source projects that query the SQ API to generate reports in various formats.
https://github.com/cnescatlab/sonar-cnes-report/tree/dev (Java)
https://github.com/soprasteria/sonar-report (JavaScript/Node)
At the time of writing both are active.
I have a problem with API Manager 1.8.0 around the functionality of deleting an API and recreating it.
Let's say I've created the "file" API version 1.0.0 and after that I've deleted it and recreated it with the same name but version 1.0.1.
When I try accessing the "file/1.0.1" API I get a 404.
I know I could've done the version update for this but that's beside the point ( I believe so).
I've created a new API named "file1" with version 1.0.1 using the same parameters as for the "file" API above and "file1/1.0.1" works as expected.
I'm using an wso2 API Manager 1.8.0 as it comes OOTB no additional database or anything else.
Could you please advise how I could get the "file" API working again?
Thanks
Delete file API from publisher.
Go to /repository/deployment/server/synapse-configs/default and delete the file API.
Then you will be able to create it again
I have a website on which I have published several of my applications.
Right now I have to update it each time one of the applications is updated.
The applications themselves check for updates so the user only visits the website if they don't have a previous version installed.
I would like to make it easier for me by creating a single executable that when downloaded and executed, will check with the database which version is the most recent and then download that one and run that setup.
Now I can make a downloader for each application, but I rather make something more universal with a parameter or argument as the difference.
For the download the 'know' which database to check for the most recent version, I need to pass on the data to the downloader.
My first thought was putting that in a XML file, so I only have to generate different xml files for each application, but then it wouldn't be a single executable anymore.
My second thought was using commandline arguments like: downloader.exe databasename
But how would I do that when the file is downloaded?
Would a link like: "https://my.website.com/downloader.exe databasename" work?
How could I best do this?
rg.
Eric
I am trying out a mashup of Alfresco and ProcessMaker. I intend to use Alfresco's document management capabilities over ProcessMaker.
Here is the scenario:
A user fills up a form in ProcessMaker and a file is uploaded in Alfresco.
I followed the wiki in this link. The problem is that, my result variable is always false. I also checked my input. I am able to access Alfresco via the address I provided, but it still does not work. I also ensured that the file exists in my directory.
Is there a way I can check (probably from logs or console) the error being returned by Alfresco or ProcessMaker so I can continue?
Alfresco is installed in a Japanese version of Windows 7.
Alfresco version is 4.2.c.
Process Maker version is 2.0.45.
I have no experience with ProcessMaker, but here's a couple of things you can try to investigate your issue:
inspect the network traffic between ProcessMaker and Alfresco (e.g. with Wireshark) to see if there's any hint available in the HTTP responses from Alfresco
enable DEBUG logs on Alfresco side
as far as I can see, ProcessMaker users Alfresco CMIS REST APIs to implement its triggers. Have a look at class.pmAlfrescoFunctions.php in ProcessMaker and try the calls yourself with some REST client (e.g. curl, Chrome REST console, htty)
This should give you an idea of what's going wrong in your case.
UPDATE
After reading that the Japanese language pack changed a folder name from "Sites" to "/サイト", and double checking the Alfresco triggers code, it's indeed the case that localized versions of Alfresco are not supported OOTB by ProcessMaker, which hardcodes "Sites" in its CMIS queries.
While the workaround provided by #nmenego would be enough in most cases, I opened a bug to ProcessMaker to let them know of the limitation.
I discovered that the problem was in the encoding used by my installed Alfresco. Instead of the default folder /Sites, the default directory was /サイト (sites in Japanese). Apparently, upon installation, the names of the default folders are translated to Japanese.
What I did was I added a folder named /Sites, and it all works now.
Of course, the points pointed out by skuro are all valid as well.
We just confirmed that this is a bug in the ProcessMaker connector triggers for Alfresco, thank you for reporting it.
I've just opened ticket 11003 in ProcessMaker's Main Support Portal for the developers to work on fixing it.
Please register for free in ProcessMaker's Main Support Portal in order to follow up on the resolution of this bug.
Best regards,
Arturo A. Robles
Customer & Partner Support Manager
Colosa Inc. - ProcessMaker