Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Sep 20 14:10
    apupier commented #260
  • Sep 20 13:43
    apupier edited #285
  • Sep 20 13:43
    apupier assigned #297
  • Sep 20 13:41
    apupier commented #298
  • Sep 20 13:41
    apupier labeled #298
  • Sep 20 13:40
    apupier review_requested #298
  • Sep 20 13:40
    apupier review_requested #298
  • Sep 20 13:36
    apupier opened #298
  • Sep 20 13:34
    apupier opened #297
  • Sep 19 07:33
    apupier labeled #296
  • Sep 19 07:32
    apupier opened #296
  • Sep 18 11:37
    djelinek closed #138
  • Sep 18 11:37
    djelinek commented #138
  • Sep 18 11:06
    djelinek synchronize #136
  • Sep 18 06:41
    apupier edited #138
  • Sep 18 06:40

    apupier on master

    Add in changelog the update fro… (compare)

  • Sep 18 06:40
    apupier closed #139
  • Sep 18 06:40
    apupier unlabeled #139
  • Sep 18 06:40
    apupier labeled #139
  • Sep 17 13:23
    apupier commented #140
Aurélien Pupier
@apupier
for information I tried to reuse the code from camel-idea (duplicated fo rnow in common-tooling)
I'm pretty sure that more code can be factorize on this part in the future
Tomáš Sedmík
@tsedmik
@apupier, @lhein I'm thinking about Apache Camel LSP project management and I'm wondering if we plan to work in sprints (fixed release cycles) or "once we have something we will make a release"? It will help me to draft an initial workflow how to manage the whole project on GitHub
Lars Heinemann
@lhein
for now we did not follow sprints or fixed cycles
whenever we felt there are enough new features we cut a release
Tomáš Sedmík
@tsedmik
@lhein ok, that's what I thought and that's IMHO most reasonable way to go for now :-)
Aurélien Pupier
@apupier
@davsclaus Hello Claus. is it possible to include Tomas and Dominik Jelinek in the member of Camel Tooling organization please? (or give me rigth to do it)
Tomas will create a board to better manage the LSP work in github directly and start having some QE applied on it (and soon documentation)
Claus Ibsen
@davsclaus
@apupier yeah sure
@apupier you and @lhein are now also owners so you ought to have admin rights
Aurélien Pupier
@apupier
thanks!
Tomáš Sedmík
@tsedmik
@apupier Hi Aurelien, I've noticed, that you've started playing with project boards :-)
@apupier I believe, that we need to set some guidelines and rules how to work with it
for example:
Tomáš Sedmík
@tsedmik
Hi @apupier, @lhein, could you get me some tips or hints how to test Apache Camel LSP locally - to be able verify resolved issues? What is your workflow in development phase?
Aurélien Pupier
@apupier
I launch a maven build on the language server project to have the fat jar genrated in target folder
then I copy it to the libs folder of LSP eclipse client (the best is to launch a maven build which will copy it automatically but it takes more time. Fo rthe first time it can ensure you to find the correct place)
than launch an Eclispe instance with the LSP eclipse client project (I hink this one yyou know how to do)
to test on VS code, i copy the fat jar to jars folder of vscode client.
to launch it, you need to open the vs code client project in VS Code, then you shoudl have a Debug -> Start Debugging available
image.png
you can even choose to launch the test suite or a vs code instance with Apache Camel LSP
Aurélien Pupier
@apupier
to verify already resolved issues, you can also use the Eclipse LSP update site/marketplace as it is automatically pushed
Tomáš Sedmík
@tsedmik
@apupier great ... thank you ... I've figured out how to do it for Eclipse ... Now, I'll look at VS Code ;-)
Tomáš Sedmík
@tsedmik
@apupier I tried VS Code - import 'camel-lsp-client-vscode' - copy the server jar into 'jars' folder - I launch Camel LSP client Extension on 'Debug' view - the following error occurs:
/usr/share/code/code --debugBrkPluginHost=49562 --debugId=2118c218-d807-4a1d-bc28-13acdf704f4c --extensionDevelopmentPath=/home/tsedmik/devel/git/camel-lsp-client-vscode --debug 
Activating extension 'camel-tooling.vscode-apache-camel' failed: Cannot find module '/home/tsedmik/devel/git/camel-lsp-client-vscode/out/extension'.
extensionHostProcess.js:818
Activating extension `camel-tooling.vscode-apache-camel` failed:  Cannot find module '/home/tsedmik/devel/git/camel-lsp-client-vscode/out/extension'
extensionHostProcess.js:463
Here is the error stack:  Error: Cannot find module '/home/tsedmik/devel/git/camel-lsp-client-vscode/out/extension'
extensionHostProcess.js:463
    at Function.Module._resolveFilename (module.js:543:15)
    at Function.Module._load (module.js:473:25)
    at Function.t._load (/usr/share/code/resources/app/out/vs/workbench/node/extensionHostProcess.js:847:582)
    at Function.t.getExtensionPathIndex.then.o._load (/usr/share/code/resources/app/out/vs/workbench/node/extensionHostProcess.js:795:924)
    at Module.require (module.js:586:17)
    at Module.patchedRequire [as require] (/usr/share/code/resources/app/extensions/git/node_modules/diagnostic-channel/dist/src/patchRequire.js:14:46)
    at require (internal/module.js:11:18)
    at Function.i [as __$__nodeRequire] (/usr/share/code/resources/app/out/vs/loader.js:30:770)
    at /usr/share/code/resources/app/out/vs/workbench/node/extensionHostProcess.js:821:524
    at t._doActivateExtension (/usr/share/code/resources/app/out/vs/workbench/node/extensionHostProcess.js:821:636)
    at t._activateExtension (/usr/share/code/resources/app/out/vs/workbench/node/extensionHostProcess.js:820:511)
    at Object.actualActivateExtension (/usr/share/code/resources/app/out/vs/workbench/node/extensionHostProcess.js:818:395)
    at e._activateExtension (/usr/share/code/resources/app/out/vs/workbench/node/extensionHostProcess.js:463:727)
    at /usr/share/code/resources/app/out/vs/workbench/node/extensionHostProcess.js:463:346
    at Array.map (<anonymous>)
    at e._activateExtensions (/usr/share/code/resources/app/out/vs/workbench/node/extensionHostProcess.js:463:321)
    at e.activateByEvent (/usr/share/code/resources/app/out/vs/workbench/node/extensionHostProcess.js:461:592)
    at /usr/share/code/resources/app/out/vs/workbench/node/extensionHostProcess.js:818:837
    at Object.g [as _notify] (/usr/share/code/resources/app/out/vs/workbench/node/extensionHostProcess.js:79:572)
    at Object.enter (/usr/share/code/resources/app/out/vs/workbench/node/extensionHostProcess.js:82:924)
    at n.Class.derive._oncancel._run (/usr/share/code/resources/app/out/vs/workbench/node/extensionHostProcess.js:84:790)
    at n.Class.derive._oncancel._completed (/usr/share/code/resources/app/out/vs/workbench/node/extensionHostProcess.js:84:231)
    at e.open (/usr/share/code/resources/app/out/vs/workbench/node/extensionHostProcess.js:111:536)
    at /usr/share/code/resources/app/out/vs/workbench/node/extensionHostProcess.js:818:433
    at Object.g [as _notify] (/usr/share/code/resources/app/out/vs/workbench/node/extensionHostProcess.js:79:572)
    at Object.enter (/usr/share/code/resources/app/out/vs/workbench/node/extensionHostProcess.js:82:924)
    at n.Class.derive._oncancel._run (/usr/share/code/resources/app/out/vs/workbench/node/extensionHostProcess.js:84:790)
    at n.Class.derive._oncancel._completed (/usr/share/code/resources/app/out/vs/workbench/node/extensionHostProcess.js:84:231)
    at c (/usr/share/code/resources/app/out/vs/workbench/node/extensionHostProcess.js:87:680)
    at n.Class.derive.join.i.forEach.K.then.o.(anonymous function) (/usr/share/code/resources/app/out/vs/workbench/node/extensionHostProcess.js:87:894)
    at Object.g [as _notify] (/usr/share/code/resources/app/out/vs/workbench/node/extensionHostProcess.js:79:572)
    at Object.enter (/usr/share/code/resources/app/out/vs/workbench/node/extensionHostProcess.js:82:924)
    at n.Class.derive._oncancel._run (/usr/share/code/
any idea how to fix it?
Aurélien Pupier
@apupier
never seen this error but I know that other IDEs than Eclipse are not good for automatic building so I often needs to call npm install
or install required dependices from a right-click menu in VS Code
I don' tknow exactly when it is needed for now
install depdencies is on right-click on package.json file
@tsedmik so usually I invoke this install depdencies, then try to call npm install in the terminal that has been opened and then retry to "debug" the application
Tomáš Sedmík
@tsedmik
@apupier ok, I'll try it. Thank you for the tip ;-)
Tomáš Sedmík
@tsedmik
@apupier "Install dependencies" on "package.json" helps. But I had to manually install "mvn-artifact-download" -> npm install --save mvn-artifact-download
otherwise "Install dependencies" fails with error that "mvn-artifact-download" cannot be installed
Tomáš Sedmík
@tsedmik
@lhein, @apupier to keep all information in upstream, would you mind if I use Git Hub wiki for Define QE role in Apache Camel LSP project - camel-tooling/camel-language-server#146
Aurélien Pupier
@apupier
@tsedmik seems fine
Tomáš Sedmík
@tsedmik
@apupier great ... I'm on it ;-)
Aurélien Pupier
@apupier
New release of the VS code client available https://twitter.com/apupier/status/1069509232804933632
Raja Jeevagan
@RajaJeevagan
@davsclaus Hello, I've a bunch of camel projects with Java DSL but in kotlin files. The projects are kotlin based Spring boot projects. Is there anyway the IntelliJ Idea Camel plugin be used on these projects.
Claus Ibsen
@davsclaus
@RajaJeevagan no the IDEA plugin is for Java and XML only. An earlier version did had some initial support for Kotlin, but I think we have removed that in the newest versions - it was at that time too much to handle for us as we develop this plugin in our spare time
The plugins that @apupier works on is using LSP which is a standard that many other IDEs are adding/has support for, and thus it works in more editors. IDEA dont yet have out of the box suppport for LSP
Raja Jeevagan
@RajaJeevagan
@davsclaus Thanks!!
Ghost
@ghost~5af9f71cd73408ce4f994fd0
Hi,
I'm just getting this message in Console in Eclipse:
[Info] Connected to Language Server...
[Info] Initializing capabilities of the server...
Any Ideas?
Aurélien Pupier
@apupier
Hello, it was normal message to inform on the state of the Language Server.
as it seems that it was causing issues and confusing users more than birning value, it has been removed with latest version
if you upgrade to the very latest version, there should be no message
(I think a version built on the 5 February)
Ghost
@ghost~5af9f71cd73408ce4f994fd0
ok, thanks. I'm gonna check
Aurélien Pupier
@apupier
for reference, the issue related to that is camel-tooling/camel-lsp-client-eclipse#44 (not closed yet because it has not been validated by QA yet.
as I forgot to put it in QA column of our dashboard :s