search

zazuko / xrm

A friendly language for mappings to RDF
MIT License
1 stars 0 forks source link

Housekeeping of vscode plugin buildscript #111

Closed mchlrch closed 2 years ago

mchlrch commented 3 years ago

The vscode plugin build fails at the moment. Maybe needs housekeeping/updates.

It makes sense to first do #109 before investigating and fixing this build.

If possible, it would be good to reduce the complexity and have a Maven build for the plugin.

https://github.com/zazuko/expressive-rdf-mapper-vscode

./gradlew startCode

...

> Task :vscode-extension-self-contained:npmInstall
npm WARN prepublish-on-install As of npm@5, `prepublish` scripts are deprecated.
npm WARN prepublish-on-install Use `prepare` for build steps and `prepublishOnly` for upload-only.
npm WARN prepublish-on-install See the deprecation note in `npm help scripts` for more information.

> expressive-rdf-mapper@1.1.0 prepublish C:\git\expressive-rdf-mapper-vscode\vscode-extension-self-contained
> node ./node_modules/vscode/bin/install && tsc -p ./src

Detected VS Code engine version: ^1.33.0
Error installing vscode.d.ts: Error: Request returned status code: 404
Details: <!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<title>Error</title>
</head>
<body>
<pre>Cannot GET /api/releases/stable</pre>
</body>
</html>

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! expressive-rdf-mapper@1.1.0 prepublish: `node ./node_modules/vscode/bin/install && tsc -p ./src`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the expressive-rdf-mapper@1.1.0 prepublish script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

> Task :vscode-extension-self-contained:npmInstall FAILED
nnamtug commented 2 years ago

see https://github.com/zazuko/expressive-rdf-mapper-vscode/tree/issue111_upgrade_build

Build is up and running. in the current state, the theia integration is lost. Please try to build+run it and give feedback. If error ELIFECYCLE still occurs, please try the following (one of):

mchlrch commented 2 years ago

yes, build+run works again (I did a fresh clone. I didn't do the npm cache clean --force)